> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/user-guide/using/alerting-and-monitoring/alert-integration.md).

# Alert Integration

## Alert Connections

To send alerts, you first need to tell each Lenses agent when it can send alerts to, these are alert connections, defined in the [provisioning file](https://docs.lenses.io/latest/deployment/configuration/agent/automation).

You can integrate and send alerts to:

1. AWS Cloud Watch
2. Datadog
3. Pager Duty
4. Prometheus Alert Manager
5. Slack
6. Webhooks
   1. Email
   2. MS Teams
   3. SMS

You can configure the provisioning file by selecting  `Environments & Topics` option from the left sidebar, expand the environment node and select the the `Configuration` node. You can then edit, test and apply the provisioning file againts the connected agent.

## Alert Channels

Once you have alert connections configured, you can then create alert channels. Channels form the link to the connection, you can create multiple channels per connection, for example you have a connection to Slack but send different types of alerts to different Slack channels.

Select the `Environments & Topics` option from the left sidebar, expand the environment node you are interested in and select the `Alerts` node, this will open the listing of alerts.

Select the channels sub tab so view existing channels. You can either then edit the channel or create a new channel.

<figure><img src="/files/caJBXq8OPBcPEaHV507i" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Alerts are always stored in Lenses even if you don't send them out to an external alerting system.
{% endhint %}


---

# 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.lenses.io/latest/user-guide/using/alerting-and-monitoring/alert-integration.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.