Be able to silence based on generatorURL

[brian-brazil]

The primary purpose of generatorURL is to be able to silence on it, this is important when you've a broken/inaccessible Prometheus server that continues to send incorrect alerts. This should be an additional option for silences, potentially hidden in an advanced section.

[matthiasr]

+1 I needed exactly this the other day.

[juliusv]

Not objecting to being able to silence on it, but to the statement that that is the primary purpose of the generatorURL :) My intent when sending this field to the Alertmanager was to have a nice link back from alerts/notifications to the Prometheus server graphing interface, so that one can easily play with the alerting expression.

[brian-brazil]

The silence is the primary purpose, and quite some time was spent arguing that it should be a separate field rather than a label or annotation due to the required semantics of the silence and de-duplication.

Technically it should be two fields however with that and the link being combined into one it's much less likely that other am client implementations would skip over it not realising why it's so important.

[Kellel]

Since generatorURL is outside of labels (which is what are used for matching currently) do we want to expand this feature request to be able to silence based on any part of a alert?

I can see that receivers might be useful to silence against, maybe fingerprint(?), but to be honest i'm struggling to come up with a silence usecase for any of the other fields.

Also in my experience I haven't ever hit something that would make silencing by generatorURL useful. Usually I will have labels that convey enough of the same information that it's not needed.

[brian-brazil]

I don't see a need to silence on anything else.

Usually I will have labels that convey enough of the same information that it's not needed.

The whole point is for cases where labels aren't sufficient, such as a HA pair which are producing identical alert labels but one of them is dodgy.

[sunilvasnata]

I have similar requirement, want to inhibit notification from second replica of Prometheus. Any update on this issue ??