[Search] Search Sessions Monitoring Task

[lizozom]

Summary

Contains #85253 (will be rebased on top)

This PR implements the Search Sessions monitoring task, as specified in the Search Sessions (formerly known as Background Sessions RFC).

The Search Session service is responsible for tracking sessions in memory and storing them, if the user chooses to do so, but after sessions are saved, the responsibility for tracking them is passed down to the monitoring task.

This task is responsible for checking up on in_progress search sessions, fetching the status of each search request and updating the search session's status (so it's correctly reflected in the Management UI for example).

Once available, this task would probably also be integrated with the push notification service, to provide more immediate completion notifications to the user.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[Dosant]

Code lgtm, tested following things:

1. Search discover, get results, then save session. Checked in devtools that search and session are in completed state 👍
2. My other test didn't go well, once it passed and other time it failed 😢:

I took a sample dashboard and added a single slow viz with 60s shard delay agg. I expected to see in dev tools session completed in around 60s and it was the case once.
But other time long search went to error state with following error:

server    log   [18:11:10.937] [debug][dataEnhanced][data_enhanced][plugins] Found 1 running sessions
server    log   [18:11:10.938] [error][dataEnhanced][data_enhanced][plugins] ResponseError: resource_not_found_exception
    at onBody (/Users/antondosov/Dev/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:333:23)
    at IncomingMessage.onEnd (/Users/antondosov/Dev/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:260:11)
    at IncomingMessage.emit (events.js:327:22)
    at endReadableNT (internal/streams/readable.js:1327:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  meta: {
    body: { error: [Object], status: 404 },
    statusCode: 404,
    headers: {
      'content-type': 'application/json;charset=utf-8',
      'content-length': '285'
    },
    meta: {
      context: null,
      request: [Object],
      name: 'elasticsearch-js',
      connection: [Object],
      attempts: 0,
      aborted: false
    }
  }
}

Session also errored out as the result.
Not sure what went wrong. Maybe there is a race condition somewhere?

[lukasolson]

Tested & functionality seems to be working as expected.

[LeeDr]

This seems like additional features targeted after 7.11.0 FF? 28 files changed (I didn't look but I'm sure some are tests) seems like a change we wouldn't put in after feature freeze.

[lizozom]

@Dosant what you saw is the fact that the extend api changes are still not merged.
So the session got expired while executing :)
Nice test!

[Dosant]

Didn't re-test since the last review considering #85253 (comment) is expected

[gmmorris]

Other than a couple of naming/typing notes, the Alerting & TaskManager changes look good to me 👍

Thanks for doing this 🙏

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 52a4ba1

Metrics [docs]

✅ unchanged

History

• 💚 Build #97856 succeeded 8415b05
• 💔 Build #97710 failed 9b26ff5
• 💔 Build #97612 failed 762bcc7
• 💔 Build #97542 failed c71139d
• 💔 Build #97539 failed 70dd89a

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream