nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Auto Close Dynatrace alert

Donny Gison

We are using Dynatrace API to send Alerts to OpsGenie. Alerting works, but seems we are unable to auto close when DT alert is resolved. Any recommendations how to enable, auto closing based on DT resolution alert?

Does it conflict with Schedule's acknowledgement?

Accepted answers

Mubeen Mohammed

Hello @Donny Gison

This is Mubeen. I will be happy to help you.

As I understand you want to automatically close the alert when it's resolved in Dynatrace.

You can achieve this by using the Dynatrace "Advanced" integration settings. Please note advanced settings for integrations are available only on the Standard and Enterprise plans.

From the Advanced Integration settings, you can set a "Close Alert" action which will close an existing Opsgenie alert based on its alias. The functionality to close an alert is reliant upon the “Alias” field of the alert. Here is the documentation to help understand the "Advanced Integration Settings"

Regards,

Mohammed Mubeen
Support Engineer, Atlassian

All comments

Mubeen Mohammed

Hello @Donny Gison

This is Mubeen. I will be happy to help you.

Mohammed Mubeen
Support Engineer, Atlassian

Donny Gison

@Mubeen Mohammed

Seems to be set-up but not working? Thanks.

Screen Shot 2022-03-13 at 1.13.21 AM.png

Mubeen Mohammed

Hello @Donny Gison
Hope your day is great,
As I can see from the screenshot shared you have just set the initial close alert rule.

So as mentioned in my previous response, you can set a "Close Alert" action which will close an existing Opsgenie open alert based on its "alias" value.

[The alias is the unique identifier for "open" alerts. There can only be one "open" alert with the same alias in Opsgenie.]

So for the Close Alert rule to work, the below conditions are required to match, and the setup will be as follows.

1. You will initially configure a "Create alert" action. A "Create Alert" action will create a new Opsgenie alert if the condition set of its filter matches the data. You need to make sure to set a custom "Alias" value for this "Create alert" action.

Create Alert.png
2. A "Close Alert" action will close an existing Opsgenie alert based on its "Alias" which means, for the "Close alert" action to work you need to have an Open alert with the same Alias field value configured in both "Create alert" and Close alert" action.

3. The actions are evaluated in order, each time the alert payload reaches Opsgenie it will be first evaluating the first action configured under your account.

Ex: You have created "Create alert -1", "Create alert -2", "Close alert -1" and "Close alert -2" actions under your integration settings.

Alert triggered from Dynatrace,
- It first checks the "Create alert -1" action if it matches alert will be created
- if not then It will go to the next action "Create alert -2" if this alert action is matching then based on its rules alert will be created. If there is already an alert open with the same information It will get de-duplicated.

- If not it will then route to "Close alert -1" at this point if this action matches then Opsgenie will check if there is any open alert with the "Alias" matching, and It will close that alert accordingly and It will not check any further with the last action "Close alert -2"

For any action set up for integration, an Alias value must be defined and matched exactly in order for the action to be executed.

Hope this information is helpful, please let us know if you have any further questions. I will be happy to assist.

Regards,

Mohammed Mubeen
Support Engineer, Atlassian

Donny Gison

Hi @Mubeen Mohammed ,

That's helpful. Made me understand Actions more. May I please seek further feedback.

In your example the Alias to match is hard coded. What if it changes like DT problem number.

DT Alert Creation Message -

[PROD] SmartQ UW: OPEN Problem P-220343162

DT Alert Closure Message -

[PROD] SmartQ UW: RESOLVED Problem P-220343162

May Alias values is likely not right

Screenshot 2022-03-15 174147.png

Mubeen Mohammed

Hello @Donny Gison
Thank you for the confirmation and I am glad it is working as expected for you now.

Regards,

Mohammed Mubeen
Support Engineer, Atlassian

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

opsgenie