-
Notifications
You must be signed in to change notification settings - Fork 155
Ability to view active profiles and add missing query inspect information #3425
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
Merged
florent-leborgne
merged 3 commits into
elastic:main
from
florent-leborgne:view-profiles-discover
Oct 10, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
The request **Inspector** is available in **Discover** and for all **Dashboards** visualization panels that are built based on a query. The available information can differ based on the request. | ||
|
||
1. Open the **Inspector**: | ||
- If you're in **Discover**, select **Inspect** from the application's toolbar. | ||
- If you're in **Dashboards**, open the panel menu and select **Inspect**. | ||
1. Open the **View** dropdown, then select **Requests**. | ||
1. Several tabs with different information can appear, depending on nature of the request: | ||
:::{tip} | ||
Some visualizations rely on several requests. From the dropdown, select the request you want to inspect. | ||
::: | ||
* **Statistics**: Provides general information and statistics about the request. For example, you can check if the number of hits and query time match your expectations. If not, this may indicate an issue with the request used to build the visualization. | ||
* **Clusters and shards**: Lists the {{es}} clusters and shards per cluster queried to fetch the data and shows the status of the request on each of them. With the information in this tab, you can check if the request is properly executed, especially in case of cross-cluster search. | ||
|
||
:::{note} | ||
This tab is not available for {{esql}} queries and Vega visualizations. | ||
::: | ||
|
||
* **Request**: Provides a full view of the visualization's request, which you can copy or **Open in Console** to refine, if needed. | ||
* **Response**: Provides a full view of the response returned by the request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I overlooked this one in the checklist you shared. While it's probably useful for some users, this was mainly added as a troubleshooting tool for profile issues in prod deployments. I don't personally have an issue with public docs for it, but we should check with @ninoslavmiskovic first to see what he thinks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is fine, since we have a section that explains we are rendering something for the user that is contextual, to also show how they can check it. There is no harm in that. I doubt it will be used much, but no harm in documentation it. ++ LGTM