-
Notifications
You must be signed in to change notification settings - Fork 919
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
Search Profiler visualization #571
Comments
This is really useful tools when you troubleshooting the bad query or analyze the performance. |
In general, I think a general profiler would be useful and something we should add to the Dashboard experience. @Hronom do you any thoughts on what information is most important to capture in a initial profiler? |
@ahopp as for me I'm targeting visual experience, since reading tree of json text not always easy for human, I would say check this screenshots, important for me is So if first version just can have name of item in tree and time how long it take, would be great! |
This could potentially be an interesting task we can plan on as part of the query insight vision :) While a lot of micro visibility data can be auto collected and displayed to the user by default with the query insight framework (opensearch-project/OpenSearch#11429) and dashboard (#5571), we cannot collect all of them since I imaging there would be a big performance impact. If the user wants to see the detailed time/resource consumption and some detailed profile data for one specific search query, this profiler dashboard would be very handy. |
Is your feature request related to a problem? Please describe.
Hard to read JSON output of profile API.
Describe the solution you'd like
Add some visualizer like this https://www.elastic.co/guide/en/kibana/current/xpack-profiler.html
The text was updated successfully, but these errors were encountered: