> 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/alerting/heartbeat-monitoring.md).

# Heartbeat Monitoring

ilert's heartbeat alert sources allow you to monitor services, devices, or workflows very easily — depending only on an HTTPS outbound connection.

Simply log in to your account, click on the **Alert sources** navigation menu, and choose **Create new alert source**.

![](/files/-MJ3ujdjc3HJNtWBrqnA)

Choose **Heartbeat** as the alert source type and configure the settings to your liking, just like any other alert source you might have already created.

With heartbeat alert sources, you may additionally choose an **interval** in which a ping (HTTP request) of your service, device, or workflow is expected. If the ping is not received by ilert in the configured interval, an alert will be created.

![](/files/-MJ3vE9VBYbQokz7bbJf)

After your alert source has been created, you will be taken to its details view, where the API key will be shown. You can use this API key to call ping requests for your heartbeat alert source.

![](/files/-MJ3vqXdq9SsdMmX8u69)

Using the **URL** (including the API key) you can simply try out heartbeats (pings), e.g. with curl on the command line:

```
curl https://api.ilert.com/api/v1/heartbeats/${YOUR-APIKEY}
```

You can find more examples on how to implement heartbeats here:

{% content-ref url="/pages/-MJ3xwrMP9m9qyteB53i" %}
[Prometheus Heartbeat Example](/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/heartbeat-monitoring/prometheus-heartbeat-example.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MJ3wu5-5cROcxAzcSAH" %}
[CLI Heartbeat Examples](/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/heartbeat-monitoring/cli-heartbeat-examples.md)
{% endcontent-ref %}


---

# 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/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/heartbeat-monitoring.md?ask=<question>&goal=<endgoal>
```

`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.