[🐛 Bug]: Site24x7 - resolved state not reflected in Keep

[syphernl]

Describe the bug
We use the Site24x7 provider. It pulls in alerts, but it appears that it doesn't (properly) handle setting these to resolved.

To Reproduce
Steps to reproduce the behavior:

1. Trigger an alert in Site24x7
2. See it ends up in the feed as "Firing"
3. Resolve the alert in Site24x7
4. See that the event still is "firing" and not "resolved"

Expected behavior
The event should go to "resolved", not remain on "firing"

Screenshots

Additional context

[dosubot]

I found a similar issue that was previously reported and closed: [🐛 Bug]: Incident is not closing automatically. This issue was resolved by a pull request that added incident resolution logic for enriched alerts. You can view the closed issue here.

To ensure alerts from Site24x7 are marked as resolved in Keep, make sure that the configuration in otel-shared/alertmanager.yml includes the send_resolved: true setting under the webhook_configs for the receiver named "keep" ^[1].

Additionally, the current logic in Keep for handling resolved alerts from Site24x7 involves transitioning the alert's status to "RESOLVED" if it is determined that the alert no longer exists. The lastReceived timestamp is updated, and the alert is added to the list of alerts to notify. If all alerts associated with an incident are resolved, the incident status is updated to "RESOLVED" ^[2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[shahargl]

Will look at it!

[shahargl]

hey @syphernl - I couldn't "resolve" alert in 24x7 - can you show how you do that?

[shahargl]

I think I found something

[syphernl]

Ah, nice!