> 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/livewatch.md).

# Livewatch Integration

Learn how to connect Livewatch to ilert using a webhook integration for automated incident escalation.

[Livewatch](https://www.livewatch.de/) is a monitoring platform designed to detect downtime, performance degradation, and connectivity issues in real time. It helps businesses stay ahead of service interruptions by sending alerts whenever a monitored service goes offline or recovers. Integrating Livewatch with ilert via webhooks enables you to automatically escalate alerts to your on-call team, trigger incident workflows, and ensure faster resolution times. This integration centralizes alerts, reduces missed notifications, and improves overall service reliability.

## In ilert: Create a Livewatch alert source

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Livewatch**, 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**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="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."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
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.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-d04fbd95cfe00bc3b7a5a692dc720281c4dd5b82%2Falert-source-livewatch.png?alt=media" alt="The Settings tab of a Livewatch alert source in ilert, showing the integration type, the masked integration key, and the Livewatch URL."><figcaption></figcaption></figure>

## In Livewatch: Creating a webhook integration

1. On the sidebar, navigate to **Contacts**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FrDLbmrKDzPa2wyxY3Ox5%2F1.png?alt=media&amp;token=598ff243-fd40-4a8b-a662-5514ca46a420" alt=""><figcaption></figcaption></figure>

2. Click **Create new contact**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FyW7y5LgUxkQ9Iw3cyJe3%2F2.png?alt=media&amp;token=9ae025a3-8bb0-495c-a881-57d66cff11ca" alt=""><figcaption></figcaption></figure>

3. Select **ilert** from the dropdown menu.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FtxZCylzDLiqJRpIsAOyV%2Fnew-1.png?alt=media&amp;token=39019abd-4c16-4fee-96dc-60d32854708b" alt=""><figcaption></figcaption></figure>

4. Paste the **previously generated integration URL** from ilert into the **ilert Url (Livewatch-URL)** field.
5. Enter a **Contact name**.
6. Save the contact to finish the setup.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FpovNOVYofXhnR1rYXbnW%2Fnew-2.png?alt=media&amp;token=1da028de-44dd-46f2-991f-c5e65b162f6a" alt=""><figcaption></figcaption></figure>

## FAQ

#### **Will alerts in ilert be resolved automatically?**

Yes, as soon as a Livewatch sends an alert event with field `state` value set to `1`, corresponding alert in ilert will be resolved.


---

# 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/livewatch.md?ask=<question>&goal=<user_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.
