-
Notifications
You must be signed in to change notification settings - Fork 44
Allow a user to be able to add additional labels to a silence via alertmanager ui #69
Comments
I'm not sure how is a more fine grained silence reducing the number of silences needed, it should require you to provide more silences in the end? Isn't it the other way around? If you want to silence the whole alert group you just need to un-check instance/node specific labels in the silence form, right? Update: I think I get it - when there are 2 instances of an |
This commit turns label checkboxes into multiselect dropdowns that are populated from all labels in current alert group. There is also a cocollapsible preview box that allows user to inspect raw silence JSON object we will send to the Alertmanager API. Fixes #69
See if #70 solves your request |
This commit turns label checkboxes into multiselect dropdowns that are populated from all labels of all instances of current alert (matched by alertname label). There is also a cocollapsible preview box that allows user to inspect raw silence JSON object we will send to the Alertmanager API. Fixes #69
This commit turns label checkboxes into multiselect dropdowns that are populated from all labels of all instances of current alert (matched by alertname label). There is also a cocollapsible preview box that allows user to inspect raw silence JSON object we will send to the Alertmanager API. Fixes #69
It would be good to be able to specify labels that are not part of a currently firing alert so that we can reduce the number of silences that are needed.
For exampe I would like to do the following:
{ "node": "foo", "instance": "foo" }
on an alert where only instance is firing
The text was updated successfully, but these errors were encountered: