Problems: Query problems with particular severity

[darrynv]

Feature request

If it relates to metric data visualization would be great to get

1. When setting the query mode to "Triggers", it would be great to be able to set specific Severity parameters e.g. Instead of >= Warning you could set = Warning.

Currently, if you want to display the count of Average vs Warning Triggers, this is skewed by the fact that Warning would display Average + Warning count e.g.

Problem
Triggers

Current Setting
Setting

I realize this could be a restraint on the API end, but perhaps setting a "severity" filter may work?

[k0deine]

Actually this doesn't have to be a limitation of the API.
You can easily set a filter on the priority field with an array or single value of for example 3 which equals average priority triggers.
I have the same issue that when defining multiple single graphs with the trigger list as datasource you cannot limit it to a specific severity. So each graph with a lower severity also contains the count of higher severity triggers. Which is kinda weird for dashboards trying to show the amount of triggers active for each severity.

You can visualize it with a trigger table, but a singlestat just looks a lot better.