-
Notifications
You must be signed in to change notification settings - Fork 3
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
[FEATURE] Query Insights Dashboards #5
Labels
Comments
This was referenced Jul 11, 2024
This was referenced Sep 4, 2024
Closing this issue since PRs for all MVP pages are already merged. |
Reopen it for releasing in 2.19 |
ansjcy
changed the title
[FEATURE] Query Insights Dashboards - MVP
[FEATURE] Query Insights Dashboards
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
In the recent releases, we have built the backend framework and APIs for query insights, including the capability to identify the top N queries based on various metrics. However, users currently lack a dashboard tool to visualize and analyze this data. They can only query the top N queries via an API and must manually aggregate and interpret historical data on their own for visualization purposes. This process is cumbersome and limits the ability to quickly diagnose and resolve performance issues.
What solution would you like?
Mock screens
Screen 1: Top N queries overview page. Users will be able to see the top queries
Screen 2: Query details screen. Users can click on the time stamp to drill down and view the details of the query.
Screen 3: Configuration tab displays the default configuration settings. Users with appropriate edit access can modify the configuration settings.
Screen 3a. While an edit is being made, the bottom bar is displayed with actions to save/cancel, along with the status of number of unsaved changes.
Screen 3b. Updated configuration is saved once user clicks “Save“.
What alternatives have you considered?
N/A
Do you have any additional context?
opensearch-project/OpenSearch#11522
The text was updated successfully, but these errors were encountered: