> 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/dotcommonitor.md).
# Dotcom-Monitor Integration
Connect Dotcom-Monitor monitor events to ilert with an inbound webhook and a custom Dotcom-Monitor JSON alert template.
[Dotcom-Monitor](https://www.dotcom-monitor.com/) is a web performance and availability monitoring platform. By integrating Dotcom-Monitor with ilert, you can route monitor failures to on-call responders in ilert and centralize escalation and incident response.
## In ilert: Create a Dotcom-Monitor alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Dotcom-Monitor**, 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, copy the generated **Dotcom-Monitor URL**. You will use this URL in Dotcom-Monitor.
## In Dotcom-Monitor: Create a custom alert template
1. In the Dotcom-Monitor dashboard, click **Manage** in the left navigation.
2. Click **Custom Alert Templates**.
3. Click **+ New Template**.
4. Enter a template name (for example, **ilert template**) and set the format to **Json**.
5. Paste the following template body:
```json
{
"monitor": {
"MonitorName": "@Model.RootResponse.Monitor.Name",
"MonitoringTime": "@Model.Monitor_DateTime"
},
"device": @{
var device = Model.RootResponse.Device;
}
{
"PlatformType": "@device.PlatformType",
"DeviceName": "@device.Name",
"Tags": [
@if (device.Tags != null)
{
foreach (var tag in device.Tags)
{
{
"Name": "@tag.Name",
"Color": "@tag.Color"
}
@if(tag != device.Tags.Last()){ , }
}
}
],
"DeviceReportingUrl": "@Model.OnlineReportLink?CUID=@Model.OnlineReportCUID"
},
"errorDetails": [@foreach (var sessionResponse in Model.SessionResponses)
{
foreach (var response in sessionResponse.Children)
{
{
"TaskType": "@response.Task.TaskType_Name",
"DetailsUrl": "@Model.DMUserLink/client/response-details/hit?id=@response.ID&StartTime=@response.StartTimeJson&rootId=@Model.RootResponse.ID&cuid=@Model.OnlineReportCUID",
"ViewTaskUrl": "@Model.DMUserLink/v2/EditLegacyTask/@response.Device.ID/@response.Task.ID",
"TaskName": "@response.Name",
"Target": "@response.Target",
"Errors": [
@if (response.AllErrors != null)
{
foreach (var error in response.AllErrors)
{
{
"ErrorType": "@error.ErrorType",
"ErrorCode": "@error.ErrorCode",
"Reason": " @error.Reason"
}
@if(error != response.AllErrors.Last()){ , }
}
}
]
}
}
}],
"monitoringResults": [@foreach (var response in Model.LastXResponses)
{
{
"MonitorName": "@response.Monitor.Name",
"Status": "@(response.IsFail ? "Error" : "Ok")",
"Start": "@response.Start",
"DetailsUrl": "@Model.WaterFallLink?id=@response.ID&StartTime=@response.StartTimeJson"
}
@if(response != Model.LastXResponses.Last()){ , }
}],
"firstError": {
"DownStateResponseMonitorName": "@Model.DownStateResponse.Monitor.Name",
"StartMonitorDowntime": "@Model.StartMonitorDowntime"
}
}
```
6. Click **Validate**, then click **Create Template**.
## In Dotcom-Monitor: Create a delivery address group
1. In Dotcom-Monitor, go to **Manage** -> **Delivery Address Groups**.
2. Click **+ New Group**.
3. Enter a group name (for example, **ilert group**) and optional description.
4. Click **New Address**.
5. Select **Webhook** as the delivery address type.
6. In **Webhook URL**, paste the Dotcom-Monitor URL you copied from ilert.
7. Set **Request Type** to **POST**.
8. Expand **Post Data** and configure:
* **Data Type:** Raw
* **Content Type:** JSON
* **Body:** select the previously created **ilert template**
9. Click **Done**, then click **Create Group**.
## In Dotcom-Monitor: Assign the delivery group to a monitor
1. Open the monitor (device) you want to alert on.
2. Go to **Alerts** settings for that monitor.
3. In **Delivery Address Groups**, click **Select Groups**.
4. Select the previously created group (for example, **ilert group**).
5. Keep escalation behavior as needed (for example, **Immediate**) and enable/disable **Resend Uptime Alert** based on your notification preference.
6. Click **Save Changes** or **Save & Close**.
## FAQ
#### **Will alerts in ilert be resolved automatically?**
Yes. When Dotcom-Monitor sends a recovery event for the same monitor, ilert resolves the corresponding alert 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 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/dotcommonitor.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.
