> 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/alibaba-cloud.md).
# Alibaba CloudMonitor Integration
Integrate Alibaba CloudMonitor with ilert to send alerts via webhook, notify on-call teams, and auto-resolve incidents when the alert recovers.
[Alibaba CloudMonitor](https://www.alibabacloud.com/en/product/cloud-monitor) integration allows you to route monitoring alerts from Alibaba Cloud directly into ilert. By combining CloudMonitor's metrics with ilert's alerting, on‑call scheduling, and incident workflows, you ensure that the right people are notified immediately, context is preserved, and incidents close automatically when CloudMonitor reports recovery, reducing MTTR and eliminating noise.
### In ilert: create an Alibaba CloudMonitor alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Alibaba CloudMonitor**, 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. Copy the generated **Webhook URL** (or API key). You will paste it into CloudMonitor later.
### In Alibaba CloudMonitor: create an alert contact and alert contact group
1. In the CloudMonitor console, open **Alert contacts**.
2. Click **Create alert contact**.
3. Enter a **Name** and paste the ilert webhook URL into the **Webhook** field.
4. Enable the contact (toggle the slider) and click **OK**.
5. Go to **Alert contact groups** and click **Create alert contact group**.
6. Provide a **Group name**, add the contact you just created, and click **Confirm**.
7. Click **Confirm**.
### In Alibaba CloudMonitor: assign the alert contact group to an alert rule
1. On the sidebar, navigate to **Alert Rules**.
2. Select or create an **Alert Rule**.
3. Head to the **Alert Contact Group** field and select the previously created Alert Contact Group.
4. Click **Confirm** to finish the setup.
### FAQ
**Q: Will alerts in ilert be resolved automatically?**
A: Yes, as soon as Alibaba CloudMonitor sends a notification with the `alertState` field set to `OK`, 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ilert.com/integrations/inbound-integrations/alibaba-cloud.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
