topic Problems sent to Opsgenie seems to not autoclose in Alerting

Problems sent to Opsgenie seems to not autoclose

AymericM — Thu, 01 Dec 2022 14:56:37 GMT

In the documentation it is stated :

Opsgenie incidents are automatically created when problems are detected and closed when problems are resolved.

But from our experience only the creation part is working, when the problem is marked as resolved in Dynatrace console it remains open in OpsGenie.

I don't see any setting in the configuration of the problem notification to activate or deactivate the sending of the close event.

Is it still working ?

Re: Problems sent to Opsgenie seems to not autoclose

Thps44 — Thu, 24 Mar 2022 16:34:58 GMT

I am having this exact same problem just started in our system recently as well. I've combed through all the setting and even updated the OpsGenie integration to V2 but still alerts are not auto closing. Hopefully a resolution can be found, I will keep looking on my end.

Re: Problems sent to Opsgenie seems to not autoclose

hakanozanlagan — Tue, 29 Mar 2022 14:49:45 GMT

we having this exact same problem too. it was working a few days ago. We didn't change any configuration. I think this problem occured after server last update.

Re: Problems sent to Opsgenie seems to not autoclose

AymericM — Tue, 29 Mar 2022 14:59:01 GMT

I sent a ticket to Dynatrace support. The answer is that Atlassian depracated the V1 of Opsgenie integration with Dynatrace and is pushing the use of their new integration using a webhook in a Custom Integration.

The advice of Dynatrace support was to follow Opsegnie documentation :

https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-dynatrace-webhook-v2/

And to make sure to :

- check the box "Call webhook if problem is closed"

- add "PID":"{PID}" in the json.

We tried it and it works.

Re: Problems sent to Opsgenie seems to not autoclose

Thps44 — Tue, 29 Mar 2022 16:01:47 GMT

When I add "PID":"{PID}" to the json it strips responders/owners from the alert so it goes to Opgenie but doesn't trigger actual alerts, when I removed the "PID":"{PID}" I get the alert notifications. Did you also see this behavior?

Re: Problems sent to Opsgenie seems to not autoclose

AymericM — Tue, 29 Mar 2022 16:57:29 GMT

I don't think we have this problem.

You're using the Custom Integration ?

If yes do you add the PID after the default JSON ?
If yes do you add a comma after the ProblemTitle line so the JSO remain valid ?

{
"State":"{State}",
"ProblemID":"{ProblemID}",
"ProblemTitle":"{ProblemTitle}",
"PID":"{PID}"
}

Re: Problems sent to Opsgenie seems to not autoclose

Thps44 — Tue, 29 Mar 2022 17:16:32 GMT

Yes, using custom integration and my JSON is identical, I deleted and recreated the integration and I get the notifications in OpsGenie but it is not assigning an owner or responder even thought the team is added to the integration I am not sure what is occurring. I tried tying it to the escalation process and the team both act the same and are not triggering an alert.

Re: Problems sent to Opsgenie seems to not autoclose

Thps44 — Tue, 29 Mar 2022 17:20:19 GMT

I think I just figured it out, even though the webhook integration is setup the alerts are coming in via the Default API which was not assigned to a team.

Re: Problems sent to Opsgenie seems to not autoclose

hakanozanlagan — Wed, 30 Mar 2022 12:08:47 GMT

how did you set priority? ProblemSeverity propery is not working.

{ProblemSeverity}: Severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, or CUSTOM_ALERT.

Re: Problems sent to Opsgenie seems to not autoclose

Keef_10 — Thu, 21 Apr 2022 09:20:31 GMT

The close alert still does not work for me.

Have you got anymore tips/tricks to try?