This repository was archived by the owner on Apr 2, 2024. It is now read-only.
Aggregate metrics at global level to avoid legend pollution in dashboards #1800
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
782ad9e to
bdba054
Compare
…ards Signed-off-by: Arunprasad Rajkumar <[email protected]>
bdba054 to
3e6f080
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Signed-off-by: Arunprasad Rajkumar [email protected]
Description
Currently we don't aggregate most of the dashboard queries which leads to legend pollution if we deploy Promscale multiple times.
Before
After
Merge requirements
Please take into account the following non-code changes that you may need to make with your PR: