|
| 1 | +--- |
| 2 | +title: "Alibaba Cloud Prometheus integration" |
| 3 | +description: "Sync Alibaba Cloud Prometheus monitoring alert events to Flashduty On-call via webhook for automated alert noise reduction" |
| 4 | +keywords: ["alert integration", "Alibaba Cloud Prometheus integration", "monitoring alerts", "data ingestion"] |
| 5 | +--- |
| 6 | + |
| 7 | +<div className="hide"> |
| 8 | + |
| 9 | +## In Flashduty On-call |
| 10 | +--- |
| 11 | +You can obtain an integration push URL through either of these two methods: |
| 12 | + |
| 13 | +### Using private integration |
| 14 | + |
| 15 | +Choose this method when you don't need to route alert events to different channels — it's simpler. |
| 16 | + |
| 17 | +<AccordionGroup> |
| 18 | + <Accordion title="Expand"> |
| 19 | + |
| 20 | + 1. Go to the Flashduty console, select **Channel**, and enter a channel's details page |
| 21 | + 2. Select the **Integrations** tab, click **Add Integration** to enter the integration page |
| 22 | + 3. Choose **Alibaba Cloud Monitor Prometheus** integration and click **Save** to generate a card |
| 23 | + 4. Click the generated card to view the **Push URL**, copy it for later use |
| 24 | + |
| 25 | +</Accordion> |
| 26 | +</AccordionGroup> |
| 27 | + |
| 28 | +### Using shared integration |
| 29 | + |
| 30 | +Choose this method when you need to route alerts to different channels based on the alert event payload. |
| 31 | + |
| 32 | +<AccordionGroup> |
| 33 | + <Accordion title="Expand"> |
| 34 | + |
| 35 | + 1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page |
| 36 | + 2. Select **Alibaba Cloud Monitor Prometheus** integration: |
| 37 | + - **Integration Name**: Define a name for this integration |
| 38 | + 3. Configure the default route and select the corresponding channel (after creation, go to `Route` to configure more routing rules) |
| 39 | + 4. Click **Save** and copy the newly generated **Push URL** for later use |
| 40 | + |
| 41 | +</Accordion> |
| 42 | +</AccordionGroup> |
| 43 | +</div> |
| 44 | + |
| 45 | +## In Alibaba Cloud |
| 46 | +--- |
| 47 | + |
| 48 | +<Steps> |
| 49 | +<Step title="Create a custom webhook"> |
| 50 | + |
| 51 | +1. Log in to the Alibaba Cloud console, search for **Cloud Monitor**, and enter the corresponding console |
| 52 | +2. In the left menu, select **Prometheus Monitoring → Notification Objects**, and create or edit a **Custom Webhook** |
| 53 | +3. Enter `Flashduty` for both the name and identifier, and enter the integration push URL in the `URL` field |
| 54 | +4. In `Headers`, set **Header Key** to `Content-Type` and **Header Value** to `application/json` |
| 55 | +5. Select **POST** for `Method` and **JSON** for `Data Format` |
| 56 | +6. Click **OK** to complete |
| 57 | + |
| 58 | +</Step> |
| 59 | + |
| 60 | +<Step title="Configure alert rules"> |
| 61 | + |
| 62 | +1. In the left menu, select **Prometheus Monitoring → Alert Rules**, and create or edit an alert rule |
| 63 | +2. In the **Notification Mode** section, select **Simple Mode** |
| 64 | +3. For **Notification Object**, select the custom webhook created in the previous step |
| 65 | +4. Click **OK** to complete |
| 66 | + |
| 67 | +</Step> |
| 68 | + |
| 69 | +<Step title="Verify integration"> |
| 70 | + |
| 71 | +Go back to the Flashduty console integration list page. If the latest event time is displayed, the configuration is successful and events are being received. |
| 72 | + |
| 73 | +</Step> |
| 74 | +</Steps> |
| 75 | + |
| 76 | +## Severity mapping |
| 77 | +--- |
| 78 | +<div className="md-block"> |
| 79 | + |
| 80 | +Alibaba Cloud Prometheus to Flashduty severity mapping: |
| 81 | + |
| 82 | +| Alibaba Cloud Monitor | Flashduty | Status | |
| 83 | +| :--- | :--- | :--- | |
| 84 | +| Critical | Critical | Critical | |
| 85 | +| Error | Critical | Critical | |
| 86 | +| Warning | Warning | Warning | |
| 87 | +| Normal | Info | Info | |
| 88 | + |
| 89 | +</div> |
0 commit comments