steve-exley
steve-exley
Thank you for this issue. It is not something we can solve directly. We have opened an internal ticket to request this change.
That's a good suggestion. We're not actively working on the Azure connection options - there are a few. But we'll add this to our future capabilities roadmap.
I too have what I think may be the same issue. Prometheus continues to report the alert in active state to AlertManager, however AlertManager reports the alert as closed and...
Further investigations on this show that the issue for us was introduced in [Prometheus 2.4, #4550](https://github.com/prometheus/prometheus/pull/4550) Prometheus now sends the `endsAt` field to the Alertmanager with a very short timeout...
We still had some of these issues on 0.16.1, the underlying cause is that the `endsAt` time period generated by Prometheus does not leave much margin for error and AlertManager...