topic Re: Dynatrace Custom integration for Problem notification in Automations

Dynatrace Custom integration for Problem notification

Shal — Thu, 18 Sep 2025 06:36:16 GMT

Hi Team ,

We are planning to send Dynatrace alerts to create workitem in Azure devops automatically.

For this

- We need to configure or add webhook URL in Dynatrace (custom integration problem notification) to send the alert with payload and this should trigger Azure service to create workitem in Devops.

Can we use Azure REST API itself instead of webhook here ?

Can someone suggest any option without webhook and use only Azure REST API?

Thanks,

Shalini.

Re: Dynatrace Custom integration for Problem notification

dania — Wed, 17 Sep 2025 14:49:06 GMT

Hi, at the moment there’s no such integration available. However, to use the Azure REST API, you can send requests through workflows and leverage either JavaScript or the WebRequest action to do so.

Re: Dynatrace Custom integration for Problem notification

Shal — Thu, 18 Sep 2025 08:31:39 GMT

I am looking for integrating Dynatrace alert - which means only when conditions in alerting profile matches I need to send the information to Azure to create workitem and it should close once alert is closed.

Do we have such option in workflow notebooks?

Re: Dynatrace Custom integration for Problem notification

dania — Fri, 19 Sep 2025 17:21:44 GMT

To emulate the behavior of an alerting profile using a workflow, you can follow these steps:

Create a new workflow with a Davis problem trigger.
Add a task to execute a DQL query.
Use the DQL query to check the status of the problem.
In the task options, enable "Wait before execution" to configure a delay.
Add a condition so the workflow only continues if the problem is still open.
Finally, add the notification task.

One important note: currently, it's not possible to set a delay directly on the problem trigger itself meaning the workflow can't be configured to run only if the problem has been open for a specific amount of time. However, the approach above is a viable workaround to achieve similar behavior.