> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/development-cycle/dashboards/alerts/how-to-create-an-alert.md).

# How to create an alert

You can create an alert to a single pipeline, multiple pipelines at once or all the pipelines in a realm. Once the alert is configured, all pipelines can generate a notification as long as they reach the threshold for the selected and configured metric.

To create an alert, you must select which behavior the pipelines should be associated with. Each time the pipelines show this behavior, an alert will be triggered in the system and you will receive a notification through your selected channels.

{% hint style="info" %}
To learn how to create alerts for VPN, visit the [documentation.](/documentation/developer-guide/development-cycle/dashboards/vpn-connections-monitoring/alerts-vpn-metrics.md)
{% endhint %}

Follow these steps to create an alert:

1. On the Platform home page, click **Monitor**.
2. At the menu at the top of the page, click on **Alerts configuration**.
   * You can also click  **Settings** on the top-right corner of the home page and then click **Alerts** in the menu on the left.
3. Click **Create**.
4. Choose an **Alert name**.
   * It’s not possible to add special characters like "\_" to the alert name. The only exception is “-”, which can be used as a substitute for a blank space.
5. Select one or more pipelines to assign alerts.
   * If you want to assign all pipelines in one realm, activate the **All pipelines** flag.
6. Configure the threshold selecting the metrics and conditions needed to trigger the alert.
7. Configure the **channels** you want to use to receive notifications.
   * Email addresses
   * Telegram chat ID
   * Webhook URL
   * Slack URL
8. Click **Save** to create a new alert or **Cancel** to return to the previous page.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4523BaA7JfghHEYBbLWY%2Fuploads%2FzBDKe4rsn2hIxrZeFc8D%2FCreate_Alerts_ENG%20-%20Made%20with%20Clipchamp.mp4?alt=media&token=0260a7f5-34ed-4cf4-94eb-69e134987140>" %}

## Examples of alert messages

Different types of messages can be generated based on the configured alert settings. Below you can see the alert messages configured to be received by email for all pipelines.

<figure><img src="/files/9VTdO1FObiVOAArogeCo" alt=""><figcaption></figcaption></figure>

Check out the documentation below to see other examples of alert messages:

* [Alerts examples on Slack](/documentation/developer-guide/development-cycle/dashboards/alerts/how-to-configure-alerts-on-slack.md)
* [Alert examples on Telegram](/documentation/developer-guide/development-cycle/dashboards/alerts/how-to-configure-alerts-on-telegram.md)
* [Alerts examples on Webhook](/documentation/developer-guide/development-cycle/dashboards/alerts/webhook.md)


---

# 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.digibee.com/documentation/developer-guide/development-cycle/dashboards/alerts/how-to-create-an-alert.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.
