> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/dynatrace.md).
# Dynatrace Integration
The ilert Dynatrace integration helps you to easily connect ilert with Dynatrace.
With the ilert Dynatrace integration, you can add alerts in ilert based on problems from Dynatrace. ilert is now available as a native app in the Dynatrace Hub, so you can install it directly in Dynatrace and forward problems to ilert through a workflow — no custom HTTP request template required.
## In ilert: Create a Dynatrace alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Dynatrace**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In Dynatrace: Install and configure the ilert app
1. In Dynatrace, click on **Hub**, search for the **ilert** app and click **Install**.
2. Go to **Settings**.
3. Open **Apps** --> **ilert connections**.
4. Click **Add item**, choose a name and paste the **webhook URL** generated in the previous ilert step. Click **Save**.
5. Go to **Workflows**.
6. Add a **Problem trigger**.
7. Edit the relevant trigger settings to match the problems you want to forward to ilert.
8. Click **Add action**.
9. Under the **ilert** app, choose the **Send event in ilert** action.
10. Configure the action settings (select the ilert connection you created), then **Save** and **Deploy** the workflow.
The integration is now set up. Dynatrace problems that match your workflow trigger will create alerts in ilert.
## FAQ
**Will alerts in ilert be resolved automatically?**
Yes, as soon as the recovery conditions of application, server or database are met, the alert in ilert will be resolved automatically.
**Can I setup Dynatrace with multiple alert sources from ilert?**
Yes, you can create arbitrary mappings between your problems in Dynatrace and alert sources in ilert. Simply add an additional ilert connection with the webhook URL of the other alert source, and point a workflow action to it.
**Can I customize the alert messages?**
Yes, you can customize the events sent to ilert by adjusting the settings of the **Send event in ilert** action in your Dynatrace workflow.
## Legacy: HTTP Request Template (Problem Notifications)
{% hint style="info" %}
This method is kept for existing setups. For new integrations we recommend using the native ilert app from the Dynatrace Hub described above.
{% endhint %}
1. Go to **Settings** --> **Integration** --> **Problem Notifications** and click on **Set up notifications** to add a new template
2. Select **Custom integration**
3. In the **Name** section, enter a name (e.g. "ilert Notification")
4. In the **Webhook URL** section, set the **Webhook URL** to the one generated in ilert
5. In the **Additional HTTP Headers** section, add the following headers `Accept`: `application/json` and `Content-Type`: `application/json`
6. In the *Custom payload* section, set the MIME type to `application/json` and copy and paste the following JSON payload:
```
{
"State": "{State}",
"ProblemID": "{ProblemID}",
"ProblemTitle": "{ProblemTitle}",
"ProblemURL": "{ProblemURL}",
"ProblemDetailsText": "{ProblemDetailsText}"
}
```
7. Click the **Send test notification** button and you should receive a **Custom integration test successful** dialog message
8. Click **Save**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ilert.com/integrations/inbound-integrations/dynatrace.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
