Feature request: auto-complete fields when silencing alerts

[aned]

It seems it would makes sense to auto-complete fields in the Alertmanager when silencing.
People can put some random/mistyped values and expect it to work.
It becomes more obvious when you're scheduling a pro-active maintenance in the future and no alerts are currently firing so the preview won't necessarily help in this case.

[simonpasquier]

From which source would AlertManager build the list of all potential labels? If it is from the current alerts it won't help much for the pro-active maintenance use case.

[aned]

The source would have to be all possible alerts configured in prometheus.

[mxinden]

As of today Alertmanager is not aware of the Prometheus instances sending alerts to Alertmanager. How would Alertmanager be able to retrieve that data?

…

On Fri, 31 Aug 2018, 18:39 aned, ***@***.***> wrote: The source would have to be all possible alerts configured in prometheus. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1536 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGuKs3AHLwyTmh8kN3qUwtbvt0uS2TsPks5uWWa4gaJpZM4WUSt9> .

[simonpasquier]

all possible alerts configured in prometheus.

Even if AlertManager were to retrieve the alert definitions from Prometheus (which is unlikely to happen as only Prometheus talks to AM for now), the labels aren't fixed: they can come from the alert query or be templated. I'd say that it would be better managed by an external tool leveraging both the Prometheus and AlertManager APIs.