-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Management] List / Terminate Running Tasks #18829
Comments
This seems more like a management task to me. The tasks API does not report the entire query (at least not currently), and monitoring -- under best practices with a separate, dedicated monitoring cluster -- implies that there's nothing that you can do with the knowledge beyond trying to not repeat it. However, if Management provides a Task listing, then a user could pick and choose between tasks live when it's most relevant. Longer term, I think that query performance makes perfect sense (either in combination with APM or by reading from the slowlog with Filebeat), but the most immediate need is a list / button in Management in my opinion. |
Following a meeting with the Elastic product team, support frequently need to help users and figure which query slow the cluster or slow specific dashboard, |
Pinging @elastic/kibana-stack-management (Team:Stack Management) |
Relates to #44193 |
nice to see at least @cjcenizal is still thinking of this. |
Still a common ask in the field |
+1 on this |
It was mentioned by a user, occasionally users run very heavy queries without being aware e.g. run a query for all data for the last 7 days, they want a way for the administrator to be able to terminate it.
Currently, there is no way to terminate the query. ES added an ID to all task which allows you to terminate specific task elastic/elasticsearch#27764
Initially, I raised that request with the Discover team but it makes much more sense to have that as an admin tool to allow the administrator to kill heavy queries.
This includes a page with a list of running tasks which then the admin can decide to terminate.
@elastic/kibana-monitoring
The text was updated successfully, but these errors were encountered: