> 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/uptrends.md). # ITRS Uptrends Integration Create alerts in ilert from ITRS Uptrends monitoring alerts — with ilert's ITRS Uptrends inbound integration. [ITRS Uptrends](https://www.uptrends.com/) monitors websites, APIs, transactions, and servers from checkpoints around the world. When a monitor fails, Uptrends sends an alert through the integrations attached to the monitor's alert definition. With this integration, Uptrends error alerts create alerts in ilert, and the matching OK alerts resolve them. ## In ilert: Create an ITRS Uptrends alert source 1. Go to **Alerting** → **Alert sources** and click **Create new alert source**. 2. Search for **ITRS Uptrends**, 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**.
The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below.

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 generates a webhook URL for your alert source. Copy it — you will need it in the next section.
The Settings tab of an ITRS Uptrends alert source in ilert, showing the integration type, the masked integration key, and the ITRS Uptrends URL.
## In Uptrends: Create a custom integration 1. On the left menu bar, navigate to **Alerting -> Integrations -> Add Integration**.
2. Now scroll down to the "Custom integrations" tab, select **Uptrends integration** and press **Choose**.
3. Enter an **Integration name** and the in ilert previously created alert source url into the **ApiUrl Value** field.
4. Now on the left menu bar, navigate to **Alerting -> Alert definitions**.
5. Select any Alert for which you want to receive a notification. 6. Select any **Escalation Level** for which you want to receive a notification, select the **Custom integration** you created earlier and press **Save**.
## FAQ **Will alerts in ilert be resolved automatically?** Yes, as soon as the Alert transitions to the status "OK" , corresponding alerts in ilert will be resolved automatically. --- # 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/uptrends.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.