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
I'd love grafana to eventually solve an issue that I come across pretty much always when building dashboards:
In a graph, I have multiple timeseries that belong to different 'groups' of things. For example take a request rate graph split out by status code. Currently grafana would just pick random(?) colors from the palette for each status code.
Yet, we know that different ranges mean different things: 200-299 = okish, 400-499 = something missing, 500-599 = something broken. It would be great if I could somehow define these groups and have grafana be smarter about how to color them.
One way to solve this would be to add support for custom color palettes and allow changing this via the series override, which would allow me to say for the regexp ^2..$ use palette "greens".
There are probably other ways and I don't care much about the specific implementation, but I think there should be something in grafana to help with this.
The text was updated successfully, but these errors were encountered:
I'd love grafana to eventually solve an issue that I come across pretty much always when building dashboards:
In a graph, I have multiple timeseries that belong to different 'groups' of things. For example take a request rate graph split out by status code. Currently grafana would just pick random(?) colors from the palette for each status code.
Yet, we know that different ranges mean different things: 200-299 = okish, 400-499 = something missing, 500-599 = something broken. It would be great if I could somehow define these groups and have grafana be smarter about how to color them.
One way to solve this would be to add support for custom color palettes and allow changing this via the series override, which would allow me to say for the regexp
^2..$
use palette "greens".There are probably other ways and I don't care much about the specific implementation, but I think there should be something in grafana to help with this.
The text was updated successfully, but these errors were encountered: