-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alert filtering by labels doesn't work #21
Comments
It probably helps if you post an screenshot of how exactly your are querying the alertmanager (metrics section of the configuration). |
Looks about right for me, are you 100% sure the context label is present in the alert? Can you put it in the legend to check? |
Not sure what you mean. This one https://user-images.githubusercontent.com/4995222/38625039-e3c96562-3da9-11e8-8315-5e3e209b6d60.png is a screenshot of alertmanager which shows that I have the context labels, for example context="PSP-T". Unfortunately the second screenshot https://user-images.githubusercontent.com/4995222/38673880-deb64154-3e52-11e8-9cb6-cf8b254705fd.png is an other example which uses context="IT". Sorry, but I didn't have an other one at this moment. |
I am also having the same issue. I can display all my current alerts on the table. |
Could you open the "query inspector" and check if your label is set under |
yep, its under that, but it just doesn't seem to do anything... |
Same problem here. |
@Santec Which version of Grafana and of the datasource are you using? Could you share the request created by the datasource and sent to the alertmanager (value of |
Meanwhile it' Grafana 5.3.4 and 0.0.7 in my case. And it still does not filter. |
Since I'm using 6.2.x and the current version of this plugin (which is still the same), it works for me. |
I have some labels as you can see here:
When I try a filter expression like
context="PSP-T"
still all alarms are visisble in Grafana. Also a filter likeinstance="IP-ADDRESS"
which should only hit one single alarm is not working.I always get all alarms.
The text was updated successfully, but these errors were encountered: