Allow templated legend via attribute keys and values from query results #57
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.
What does this PR do?
Adds a legend formatter so folks can add custom labels that are derived from the data source.
How does this impact users?
If a user doesn't use a query name, than there is no change.
If a user adds a query name with a label name reference from the query results, like
{{service}}
, then the legend for the that value is interpolated with the label value.What needed to change in the code and why?
A few changes were made to the Time Series Value fields:
createFieldName
function.TIME_SERIES_VALUE_FIELD
which has logic to remove the name if there is nodisplayNameFromDS
set and use default label formatting.{{var1}}
which is similar to the Prometheus / Loki datasource<undefined>
How did you test this?
New unit tests and manually.