Allow mapping values in Prometheus table panel #112
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
It is now possible to use the value mapping from the sparkline panel in the table panel for the Prometheus plugin. To use this feature we added a new option for the specified columns named "mapping". If a user specifies such mappings the corresponding value will be shown in the table instead of the returned value from the PromQL query. We also using the "dashboard" as query key instead of the "dashboard.title". Last but not least it is now possible to filter the variable values in a dashboard.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It is now possible to use the value mapping from the sparkline panel in
the table panel for the Prometheus plugin. To use this feature we added
a new option for the specified columns named "mapping". If a user
specifies such mappings the corresponding value will be shown in the
table instead of the returned value from the PromQL query.
We also using the "dashboard" as query key instead of the
"dashboard.title".
Last but not least it is now possible to filter the variable values in a
dashboard.