I’ve just run into a possible issue caused by a combination of Alerts page defaults (or at least my saved Alerts page filters) and alert de-duplication.
Namely, we had an alert fire on December 31st (which no one paid any attention to, partly because we’re still ramping up our usage of Opsgenie) and again earlier today. I noticed the alert had fired today because our Alertmanager routing (we use Prometheus) also sends emails whenever an alert fires. So I went to Opsgenie but couldn’t see any trace of the alert. I figured out a while later this was because the default time range filter on the Alerts page is “created during last week” (at least that’s how it is for me, I might have touched that in the past) and the alert was created more than 7 days ago, so there was nothing for me to see there.
Would it be possible for the default time range on the Alerts page to be “all time”? And I don’t mean just for me, but for all users (at least within my company). It doesn’t look like it would put too much load on Opsgenie, as only the first couple screens’ worth of alerts are loaded (with the rest loaded when scrolling to the bottom).
Ideally the default time range could be set globally by an admin and user changes to the time range would not be persisted at all, so users would not be able to shoot themselves in the foot (persisting time ranges or not could also be an option to be selected by the admin).
Failing that (and considering that such a change could not be made within days anyway) do you have any suggestion for how to work around this issue? All I could come up with was to edit all escalations and add some extra notification after 7 days. But that’s both too specific (user could set their default time range to last day instead of last week) and not visible enough (the 7 day notification may slip through the cracks and it’s a one time thing).