> 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/serverguard24.md).
# ServerGuard24 Integration
Connecting ServerGuard24 with ilert enables real-time alerts and streamlined incident management, allowing teams to respond swiftly to server issues and minimize downtime
[ServerGuard24](https://www.serverguard24.com/index.html) is a comprehensive server monitoring service that ensures the availability and performance of your IT systems. It offers a range of monitoring solutions, including website monitoring, mail server monitoring, database server monitoring, and security monitoring. This guide helps to connect ServerGuard24 with ilert.
## In ilert: Create a ServerGuard24 alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **ServerGuard24**, 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 ServerGuard24: Create a Webhook
1. On the Dashboard, click on **Settings**.
2. Now, on the sidebar, navigate to **Integrations** and click on the **+ New Integration** button.
3. Change the **Type** to 'Custom'.
4. Change the **Request Type** to 'POST Data'
5. Now, enter a **Description** and the previously generated alert source URL in the **URL** field.
6. Enter the following template into the **Data Template** field:
```json
{
"id": "{ID}",
"status": "{STATUS}",
"status2": "{STATUS2}",
"output": "{OUTPUT}",
"remark": "{REMARK}",
"shortlink": "{SHORTLINK}",
"downmsg": "{DOWNMSG}",
"timestamp": "{TIMESTAMP}",
"datetime_gmt": "{DATETIME_GMT}",
"datetime_loc": "{DATETIME_LOC}",
"datetime_frm": "{DATETIME_FRM}",
"datetime_iso": "{DATETIME_ISO}",
"check": "{CHECK}",
"server": "{SERVER}",
"address": "{ADDRESS}",
"debugoutput": "{DEBUGOUTPUT}"
}
```
7. Click on **Save** to finish the setup.
## FAQ
**Will alerts in ilert be resolved automatically?**
Yes, as soon as the status of a ServerGuard24 check is 'OK' again, the 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/serverguard24.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
