> 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/~/changes/vPSzQFfkdJCVWGT5AL1m/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.
## In ilert: Create a Dynatrace alert source
1. Go to **Alert sources** --> **Alert sources** and click on **Create new alert source**
2. Search for **Dynatrace** in the search field, click on the Dynatrace tile and click on **Next**.
3. Give your alert source a name, optionally assign teams and click **Next**.
4. Select an **escalation policy** by creating a new one or assigning an existing one.
5. Select you [Alert grouping](/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/alert-sources.md#alert-grouping) preference and click **Continue setup**. You may click **Do not group alerts** for now and change it later.
6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on **Finish setup** for now.
7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.
## In Dynatrace: Create a HTTP Request Template
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**
## 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 applications in Dynatrace and alert sources in ilert. Simply create additional actions in Dynatrace using the same HTTP Request Template with a different `ilertApiKey`.
**Can I customize the alert messages?**
Yes, you can customize the events sent to ilert by changing the JSON payload in the **Payload** section of the **HTTP Request Template**.
---
# 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/~/changes/vPSzQFfkdJCVWGT5AL1m/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.
