Description
I think it would be nice if it were possible to add a label like disable_resolve or something along those lines to an alert so that it will not auto-resolve even if passed to a pagerduty receiver with that feature enabled. It would be pretty simple to document and appears to be a feature a couple people need.
The mild inconvenience we encounter is duplicating our receiver config for every team's receiver to have an auto-resolve and not auto-resolve pagerduty receiver.
There is a similar request with some discussion here: #4033
I don't think the send_resolved field needs to be templateable, I think it makes sense as static per receiver to reduce complexity. And I'm not sure every integration needs this feature so it would be nice to scope it to the pagerduty integration.
There is some discussion in the above thread about the strength of alertmanager being around grouping. I would argue that while that is true, alerts are mostly grouped on traits of how the alerting service functions (the teams supporting it, the related pieces of infrastructure, other things that are technically connected to it) and breaking that grouping into two to change how the alert behaves with an external integration seems unnecessary. As opposed to routing by destination (different receivers for different teams, etc,.) makes sense to me to control at the routing step.
I'm not very familiar with the codebase so I don't know if this is a technically complex request, if it is totally feature breaking to implement this for just the pagerduty integration I apologize. This is also pretty small fries.