docs: adjust queries in Grafana dashboard #9584
Merged
Conversation
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
Contributor
Author
|
I'm not sure why CI failed. I don't think that it's related to the proposed changes. |
monkeyDluffy6017
approved these changes
Jun 7, 2023
leslie-tsang
approved these changes
Jun 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Change Prometehus queries of the latency graphs to consider selected
$routeand to use dynamic rate interval ($__rate_interval).These changes lead to a better user experience with the provided Grafana dashboard. The main focus is to allow users to see latency metrics for a particular route.
The changes don't affect existing users in any way, the default view stays the same. The required version of Grafana stays the same.
These are the altered panels:
Checklist
I have added tests corresponding to this changeI have updated the documentation to reflect this change