Admins search requests management UI in Kibana

[AlonaNadler]

Currently, admins don't have visibility in Kibana on the requests that are running, they only have visibility to the Elasticsearch requests.

That makes it difficult in several cases:

• Admins need to understand the query from the ES request which can be challenging
• Admins can't tell which query is tied to which object,
• In case a heavy query slows down the cluster they can't tell where in Kibana was it issued from or which object? (example: someone created a pie chart with 1000 slices and users keeps running it, admins have a difficult time to track the issue)

The workaround often used is to look at either the tasks in Elasticsearch or using audit logs. The limitation in these methods is that they can't tell which Kibana object/application the request is coming from.

The ongoing work on query cancellation in Kibana gets us closer to provide search requests management UI in Kibana

Suggestions: a management UI that shows all the running queries and allow admins to terminate a request done by a user

Goals:

• allow admins to view what is running in Kibana in an easy way
• provide a way to terminate the long-running search for a user in case it consumes too much of the cluster or the query is not efficient ( e.g running a search on the last 5 years)
• identify visualizations that are creating heavy queries
• Identify methods users use that create load on the ES side

To illustrate this idea

cc: @lukasolson @elastic/kibana-app-arch

[elasticmachine]

Pinging @elastic/es-ui

[cjcenizal]

Related to the Tasks UI issue (#42621).

[mdefazio]

I believe this screen is related to this issue:

Current Prototype: https://www.figma.com/proto/FD2M7MUpLScJKOyYjfbmev/Kibana-Query-Management?node-id=256%3A1552&viewport=1504%2C-203%2C0.8277243375778198&scaling=scale-down

See https://github.com/elastic/kibana-team/issues/135

[jzzfs]

I took the liberty of implementing this, albeit outside of Kibana. Here's the web app and here's the repo.

Already mentioned in kibana#42621

[vadimkibana]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.