You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have many instances of Prometheus as a data source, pulling in integer values for items like an event ID or userid.
These IDs map to human-readable names in a SQL data source (which we also have configured in grafana)
While we can use grafana variables to, for example, provide a dropdown to modify the graph query by friendly name (if, for example, we wanted to filter on an ID, the legend does not appear to be alterable when we aren't filtering, so we end up with integers in the legend instead of the __text value of the variable names.
It would be wondrous if we could use a variable for the legend in such a way that the __text value from the variable, rather than the raw value, appeared in the legend.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! It looks like this has already been reported by another user. We’ve closed this in favor of the existing one. Please consider adding any details you think is missing to that issue.
To avoid having your issue closed in the future, please read our CONTRIBUTING guidelines.
We have many instances of Prometheus as a data source, pulling in integer values for items like an event ID or userid.
These IDs map to human-readable names in a SQL data source (which we also have configured in grafana)
While we can use grafana variables to, for example, provide a dropdown to modify the graph query by friendly name (if, for example, we wanted to filter on an ID, the legend does not appear to be alterable when we aren't filtering, so we end up with integers in the legend instead of the __text value of the variable names.
It would be wondrous if we could use a variable for the legend in such a way that the __text value from the variable, rather than the raw value, appeared in the legend.
Thanks!
The text was updated successfully, but these errors were encountered: