flashduty-knowledge-base 1.3.6 → 1.3.7

package/dist/iife/en.js

@@ -77,7 +77,7 @@ Field|Required|Type|Description
 
 Field|Required|Type|Description
 :-:|:-:|:-:|:---
-| title_rule | Yes | string | Alert title, no more than \`512\` characters, will be truncated if exceeded.<br><br>Supports dynamic title generation based on alert content, see [Customizing Incidents](https://docs.flashcat.cloud/en/flashduty/customize-incident-attrs) for generation rules.
+| title_rule | Yes | string | Alert title, no more than \`512\` characters, will be truncated if exceeded.<br><br>Supports dynamic title generation based on alert content, see [Customizing Incidents](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines) for generation rules.
 | event_status | Yes | string | Alert status.<br><br>Enumerated values (case-sensitive): *Critical*, *Warning*, *Info*, *Ok*.<br><br>When specified as Ok, it means automatic recovery of the alert.
 | alert_key | No | string | Alert identifier, used to update or automatically recover existing alerts.<br><br>You can customize this value, but it cannot exceed \`255\` characters. You can also rely on system auto-generation, this value will be returned in the response.<br><br>If you're reporting a recovery event, this value must exist.
 | description | No | string | Alert description, no more than \`2048\` characters, will be truncated if exceeded.
@@ -218,7 +218,7 @@ Failed Response:
   3. The new event might be discarded due to matching exclusion, discard, suppression, or silence rules.
   4. When a new event triggers a new alert, the system enters the second layer of noise reduction check, determining if the new alert can be merged into an active incident. If possible, it will only merge into the existing incident without generating a new one.
 
-  For more information, please refer to [Alert Noise Reduction](https://docs.flashcat.cloud/en/flashduty/what-is-noise-reduction).
+  For more information, please refer to [Alert Noise Reduction](https://docs.flashcat.cloud/en/on-call/channel/noise-reduction).
 </details> `,a=`---
 title: "Email Integration"
 description: "Generate a unique email address in Flashduty to synchronize alert triggers and recoveries through email"
@@ -318,7 +318,8 @@ attachment_stripped = true
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the email integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the email integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
+
 `,o=`---
 title: "Nightingale/Flashcat Integration"
 description: "Push alert events from Nightingale (n9e) or Flashcat to Flashduty via webhook. When an alert is triggered, send a trigger event to Flashduty; when an alert recovers, send a recovery event to Flashduty"
@@ -2776,7 +2777,7 @@ OCP Alert Notification - Single Alert
 |OceanBase|Flashduty|Status|
 |---|---|---|
 |Down|Critical|Critical|
-|Critical|Warning|Critical|
+|Critical|Critical|Critical|
 |Warning|Warning|Warning|
 |Caution|Info|Info|
 |Notice|Info|Info|
@@ -4525,7 +4526,7 @@ url: "https://docs.flashcat.cloud/en/flashduty/statecloud-integration-guide"
 
 Sync StateCloud monitoring alert events to Flashduty via webhook for automated alert noise reduction.
 
-For resource monitoring events from StateCloud [secondary nodes](#secondary-nodes), please use Huawei Cloud integration. Refer to [Huawei Cloud Alert Integration Guide](https://docs.flashcat.cloud/en/flashduty/huawei-ces-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+For resource monitoring events from StateCloud [secondary nodes](#secondary-nodes), please use Huawei Cloud integration. Refer to [Huawei Cloud Alert Integration Guide](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-sources/huawei-ces).
 
 
 <div class="hide">
@@ -4902,7 +4903,8 @@ Go to the **Permission Management** page and apply for the following permissions
 
 - \`im:chat\`: Get and update group information
 - \`im:message\`: Get and send single chat and group messages
-- \`contact:user.id:readonly\`: Get user ID by phone number or email <span id="war-room-scope"></span>
+- \`contact:user.id:readonly\`: Get user ID by phone number or email
+- \`im:message.group_msg\`: Read group chat history (required for AI-generated post-mortem to access war room conversations) <span id="war-room-scope"></span>
 
 ![2025-09-17-19-59-38](https://docs-cdn.flashcat.cloud/images/png/61cb9fbc295e94b4d9acd7e44ac75e13.png)
 
@@ -4965,7 +4967,8 @@ After completing the previous steps, in the **Enhanced Features** module of the
    > After exceeding API call limits, the Feishu/Lark application will not be able to push messages normally. It is recommended to use notification channels reasonably. See [Feishu/Lark official documentation](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit) for details.
 5. **Why is the war room feature not working as expected?**
    - Please check again whether you have configured the [required permissions](#war-room-scope) for the war room feature.
-   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).`,Dingtalk:`---
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+`,Dingtalk:`---
 title: "Dingtalk Integration"
 description: "By integrating a custom Dingtalk application, you can receive and respond to alerts within Dingtalk."
 date: "2025-05-19T10:00:00+08:00"
@@ -5354,6 +5357,8 @@ By integrating the Slack third-party application, you can receive and respond to
 
 After completing the previous steps, in the **Enhanced Features** module of the Flashduty integration configuration page, check **Enable War Room** to enable this feature without additional configuration.
 
+To enable AI-generated post-mortem with war room chat history, the app requires additional \`channels:history\` permission. For existing Slack integrations, you need to manually re-authorize to grant this permission.
+
 ## 3. FAQ
 
 ---
@@ -5384,7 +5389,8 @@ After completing the previous steps, in the **Enhanced Features** module of the
    - If the error persists after retrying, please contact customer service to record and resolve new issues.
 9. **Why is the war room feature not working as expected?**
    - For previously authorized Slack IM integrations, you need to manually reauthorize Slack in the Flashduty integration configuration page to grant the application the additional permissions required for the war room feature.
-   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).`,MicrosoftTeams:`---
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
+`,MicrosoftTeams:`---
 title: "Microsoft Teams Integration"
 description: "By integrating the Microsoft Teams third-party application, you can receive and respond to alerts within Microsoft Teams."
 date: "2025-05-19T10:00:00+08:00"
@@ -5653,7 +5659,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 
 2. **Will failed pushes continue to be pushed?**
 
-  For specific network errors, retries will be attempted up to a maximum of 2 times:
+  For specific network errors, retries will be attempted up to a maximum of 1 times:
     - context deadline exceeded (excluding cases involving "awaiting headers")
     - i/o timeout
     - eof
@@ -5864,7 +5870,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 2. **Will failed pushes continue to be pushed?**
 
-  For specific network errors, retries will be attempted up to a maximum of 2 times:
+  For specific network errors, retries will be attempted up to a maximum of 1 times:
     - context deadline exceeded (excluding cases involving "awaiting headers")
     - i/o timeout
     - eof
@@ -6673,7 +6679,8 @@ If you want to display only key label information, you can refer to the code seg
 \`\`\`
 </div>
 
-<div class="sms hide">
+<div class="feishu hide">
+
 
 ## Feishu/Lark Bot
 ---
@@ -6943,6 +6950,7 @@ Description：{{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
 Responders：{{range .Responders}}@{{.PersonName}} {{end}}{{end}}
 <br>Details：{{.DetailUrl}}
 \`\`\`
+
 </div>
 
 <div class="dingtalk hide">
@@ -7187,6 +7195,19 @@ You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Sever
 \`\`\`
 </div>
 
+
+<div class="voice hide">
+
+## Voice
+---
+If no custom content is set, the system default template will be used for notifications:
+
+\`\`\`go
+You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Severity: {{.IncidentSeverity}}{{if gt .AlertCnt 1}}, Grouped {{.AlertCnt}} alerts{{end}}
+\`\`\`
+</div>
+
+
 <div class="email hide">
 
 ## Email
@@ -8080,7 +8101,7 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 `,FeishuAlert:`---
 title: "Feishu Alert Integration"
 description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
@@ -8162,7 +8183,7 @@ By default, the system always creates new alerts for each message, but you can s
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Feishu(lark) integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Feishu(lark) integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 `,VolcEngineDetect:`---
 title: "Volcengine Cloud-Detect Alert Events"
 description: "Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction"
@@ -8725,7 +8746,7 @@ After configuring the Webhook channel, you can use it in notification policies.
 
 <div class="md-block">
 
-Currently, all alerts pushed to Flashduty through the Cloudflare integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Cloudflare integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 
 </div>
 
@@ -8804,12 +8825,12 @@ By default, the system always creates new alerts for each message, but you can s
 
 ### Notes
 - Wecom alert integration URL only supports Text and Markdown message types; other message types cannot be received
-- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines)"
+- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines)"
 
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 
 ---
 title: "Wecom Alert Integration"
@@ -8886,12 +8907,12 @@ By default, the system always creates new alerts for each message, but you can s
 
 ### Notes
 - Wecom alert integration URL only supports Text and Markdown message types; other message types cannot be received
-- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines)"
+- Flashduty will generate a default alert title: "Wecom robot Alert , If you need to change the title, you can customize it using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines)"
 
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).`,ServiceDeskPlusSync:`---
+Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).`,ServiceDeskPlusSync:`---
 title: "ServiceDesk Plus Sync"
 description: "Sync incidents with ServiceDesk Plus requests through ServiceDesk Plus sync webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -9123,7 +9144,7 @@ Choose this method when you need to route alerts to different channels based on
 ## Severity Mapping
 ---
 
-Currently, all alerts pushed to Flashduty through the Harbor integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
+Currently, all alerts pushed to Flashduty through the Harbor integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).
 
 `,LabelMappingAPI:`Configure Label Mapping API to automatically call your external API when alert events arrive, enabling dynamic enrichment and correlation of alert information. With this feature, you can automatically attach information from external data sources such as CMDB, HR systems, and more to your alerts.
 
@@ -9302,7 +9323,7 @@ To prevent security bypasses, request smuggling, IP spoofing, and cache poisonin
 ### Header Best Practices
 
 1. **Allowlist Mode**: It is recommended to only allow custom Headers prefixed with \`X-Custom-\` or \`X-Enrich-\`
-2. **Length Limits**: The Key or Value length of a single Header should not exceed 1024 bytes
+2. **Length Limits**: The Key length of a single Header should not exceed 1024 bytes, the Value length of a single Header should not exceed 4096 bytes
 3. **Format Validation**: Header Values must not contain line breaks (\`\\r\`, \`\\n\`) to prevent Header injection attacks
 
 ## V. Best Practices
@@ -9329,4 +9350,593 @@ To prevent security bypasses, request smuggling, IP spoofing, and cache poisonin
 3. **Can result_label_keys be changed dynamically?**
 
    - Yes, you can modify the list of expected labels in Flashduty at any time without modifying the API code
+`,VolcEngineRTC:`---
+title: "Volcengine RTC Alert Events"
+description: "Sync Volcengine RTC alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/volcengine-rtc-integration-guide"
+---
+
+Sync Volcengine RTC alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Volcengine RTC** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Volcengine RTC** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+## In Volcengine
+---
+
+### Configure Alert Rules
+
+1. Login to your \`Volcengine\` console, find \`RTC\`, and enter the corresponding product console.
+2. In the left menu, select \`Monitor->Alert Notifications\`, and go to the \`Alert Rules\` page.
+3. Create or edit an alert rule, check \`Alert Callback\` on the rule page and fill in the <span class='integration_url'>push URL</span> for the alert integration.
+4. Configure other options as needed.
+5. Click \`Confirm\` to complete the configuration.
+
+![2026-02-05-17-32-39](https://docs-cdn.flashcat.cloud/images/png/21908f6a040f61ad2e8091226874fe97.png)
+
+## Status Mapping
+  
+|Volcengine RTC|Flashduty|Status|
+|---|---|---|
+|Critical|Critical|Critical|
+|Warning|Warning|Warning|
+|Notice|Info|Info|
+
+
+You can customize the severity through [Alert Processing Pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).`,UcloudCloudWatch:`---
+title: "Ucloud CloudWatch Alert Events"
+description: "Sync Ucloud CloudWatch alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2024-07-05T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/ucloud-cloudwatch-integration-guide"
+---
+
+Sync Ucloud CloudWatch alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Ucloud CloudWatch** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Ucloud CloudWatch** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+## In Ucloud
+---
+
+### Step 1: Configure Notice Template
+
+1. Login to your Ucloud console, search for \`CloudWatch\` product, and enter the corresponding product console.
+2. In the menu, select \`Notice Management\`, and go to the \`Contact Template\` page.
+3. Create or edit a notification template, check \`Webhook\` on the template page.
+4. Select \`English\` for **Callback Language**, and enter the <span class='integration_url'>push URL</span> for the alert integration in the input box.
+5. Enter \`Flashduty\` or another name for the template name.
+6. Configure other options as needed.
+7. Click \`Submit\` to complete the configuration.
+
+![2026-02-05-14-16-00](https://docs-cdn.flashcat.cloud/images/png/9e6ee0943b6f3ee6b942229bd456cf75.png)
+
+### Step 2: Configure Alert Policy
+1. Login to your Ucloud console, search for \`CloudWatch\` product, and enter the corresponding product console.
+2. In the menu, select \`Alarm Management\`, and go to the \`Alarm Policy\` page.
+3. Create or edit an alert policy, find the **Notification Settings** on the policy configuration page, and select the notification template created in **Step 1**.
+4. Configure other options as needed.
+5. Click \`Submit\` to complete the configuration.
+
+
+## Severity Mapping
+---
+Currently, all Ucloud CloudWatch alert events pushed to Flashduty have a severity of Warning. You can customize the severity through [Alert Processing Pipeline](https://docs.flashcat.cloud/en/on-call/integration/alert-integration/alert-pipelines).`,Nagios:`---
+title: "Nagios Integration"
+description: "Synchronize Nagios alert events to Flashduty via script to achieve automated alert noise reduction"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/nagios-integration-guide"
+---
+
+Sync Nagios alert events to Flashduty via script to achieve automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Nagios** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Nagios** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+</div>
+
+
+## In Nagios
+
+---
+
+Nagios installation paths may vary depending on the system and installation method. Please adjust the paths in the following configuration according to your actual environment.
+
+### Step 1: Download Notification Script
+
+<div class="md-block">
+
+Log in to the Nagios Server host and download the notification script to the Nagios plugin directory:
+
+- **Debian/Ubuntu systems** (typically \`/usr/lib/nagios/plugins/\`):
+
+\`\`\`bash
+cd /usr/lib/nagios/plugins/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/send_to_flashduty.sh
+chmod +x send_to_flashduty.sh
+\`\`\`
+
+- **RHEL/CentOS systems** (typically \`/usr/lib64/nagios/plugins/\`):
+
+\`\`\`bash
+cd /usr/lib64/nagios/plugins/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/send_to_flashduty.sh
+chmod +x send_to_flashduty.sh
+\`\`\`
+
+- **Source installation** (typically \`/usr/local/nagios/libexec/\`):
+
+\`\`\`bash
+cd /usr/local/nagios/libexec/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/send_to_flashduty.sh
+chmod +x send_to_flashduty.sh
+\`\`\`
+
+#### Note: The script uses the \`curl\` command. Please ensure curl is installed on your Nagios Server.
+
+</div>
+
+### Step 2: Create Flashduty Configuration File
+
+<div class="md-block">
+
+Download the Flashduty configuration file to the Nagios configuration directory:
+
+- **Debian/Ubuntu systems** (typically \`/etc/nagios3/conf.d/\`):
+
+\`\`\`bash
+cd /etc/nagios3/conf.d/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/flashduty.cfg
+\`\`\`
+
+- **RHEL/CentOS systems** (typically \`/etc/nagios/objects/\`):
+
+\`\`\`bash
+cd /etc/nagios/objects/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/flashduty.cfg
+\`\`\`
+
+- **Source installation** (typically \`/usr/local/nagios/etc/objects/\`):
+
+\`\`\`bash
+cd /usr/local/nagios/etc/objects/
+wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/nagios/flashduty.cfg
+\`\`\`
+
+</div>
+
+### Step 3: Modify Configuration File
+
+<div class="md-block">
+
+Edit the downloaded \`flashduty.cfg\` file and modify the following:
+
+1. Replace the \`pager\` field value with the integration push URL obtained from the Flashduty console
+2. Modify the script path in \`command_line\` according to your Nagios installation path
+
+Configuration file example:
+
+\`\`\`
+define contact {
+    contact_name                    Flashduty
+    alias                           Flashduty Alert Receiver
+    service_notification_commands   notify-service-by-Flashduty
+    host_notification_commands      notify-host-by-Flashduty
+    service_notification_options    w,u,c,r
+    host_notification_options       d,u,r
+    service_notification_period     24x7   
+    host_notification_period        24x7   
+    pager                           <YOUR_FLASHDUTY_PUSH_URL>
+}
+
+
+define command {
+    command_name    notify-host-by-Flashduty
+    command_line    <NAGIOS_PLUGIN_PATH>/send_to_flashduty.sh type=HOST WEBHOOK_URL="$CONTACTPAGER$" hostname="$HOSTNAME$" state="$HOSTSTATE$" output="$HOSTOUTPUT$" notification_type="$NOTIFICATIONTYPE$" time="$LONGDATETIME$" host_address="$HOSTADDRESS$" host_alias="$HOSTALIAS$" check_command="$HOSTCHECKCOMMAND$"
+}
+
+define command {
+    command_name    notify-service-by-Flashduty
+    command_line    <NAGIOS_PLUGIN_PATH>/send_to_flashduty.sh type=SERVICE WEBHOOK_URL="$CONTACTPAGER$" hostname="$HOSTNAME$" state="$SERVICESTATE$" output="$SERVICEOUTPUT$" notification_type="$NOTIFICATIONTYPE$" time="$LONGDATETIME$" host_address="$HOSTADDRESS$" service_desc="$SERVICEDESC$" host_alias="$HOSTALIAS$" max_attempts="$MAXSERVICEATTEMPTS$" 
+}
+\`\`\`
+
+Parameter descriptions:
+- \`pager\`: Flashduty push URL, the integration push URL obtained from the Flashduty console
+- \`<NAGIOS_PLUGIN_PATH>\`: Replace with the actual script path, such as \`/usr/local/nagios/libexec\`
+- \`service_notification_options\`: Service alert notification options, w=warning, u=unknown, c=critical, r=recovery
+- \`host_notification_options\`: Host alert notification options, d=down, u=unreachable, r=recovery
+
+**To include additional information in alerts, you can append parameters in \`key=value\` format at the end of \`command_line\`, for example: \`environment="production" region="$_HOSTREGION$"\`. These parameters will be pushed to Flashduty as labels.**
+
+</div>
+
+### Step 4: Include Configuration File
+
+<div class="md-block">
+
+If you are using **RHEL/CentOS systems** or **source installation**, you need to include the Flashduty configuration file in the Nagios main configuration file.
+
+- **RHEL/CentOS systems**: Edit \`/etc/nagios/nagios.cfg\` and add:
+
+\`\`\`
+cfg_file=/etc/nagios/objects/flashduty.cfg
+\`\`\`
+
+- **Source installation**: Edit \`/usr/local/nagios/etc/nagios.cfg\` and add:
+
+\`\`\`
+cfg_file=/usr/local/nagios/etc/objects/flashduty.cfg
+\`\`\`
+
+:::tips
+Debian/Ubuntu systems typically auto-load all configuration files in the \`/etc/nagios3/conf.d/\` directory, so manual inclusion is not required.
+:::
+
+</div>
+
+### Step 5: Add Flashduty to Contact Group
+
+<div class="md-block">
+
+Edit the contacts configuration file to add the Flashduty contact to the \`admins\` contact group (or another contact group you use):
+
+- **Debian/Ubuntu systems**: Edit \`/etc/nagios3/conf.d/contacts_nagios2.cfg\`
+- **RHEL/CentOS systems**: Edit \`/etc/nagios/objects/contacts.cfg\`
+- **Source installation**: Edit \`/usr/local/nagios/etc/objects/contacts.cfg\`
+
+Find the contact group definition and add Flashduty to the members list:
+
+\`\`\`
+define contactgroup {
+    contactgroup_name       admins
+    alias                   Nagios Administrators
+    members                 nagiosadmin,Flashduty
+}
+\`\`\`
+
+</div>
+
+### Step 6: Verify Configuration and Restart Service
+
+<div class="md-block">
+
+1. Verify the Nagios configuration file:
+
+- **Debian/Ubuntu systems**:
+
+\`\`\`bash
+/usr/sbin/nagios3 -v /etc/nagios3/nagios.cfg
+\`\`\`
+
+- **RHEL/CentOS systems**:
+
+\`\`\`bash
+/usr/sbin/nagios -v /etc/nagios/nagios.cfg
+\`\`\`
+
+- **Source installation**:
+
+\`\`\`bash
+/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
+\`\`\`
+
+2. If verification passes, restart the Nagios service:
+
+\`\`\`bash
+# Debian/Ubuntu
+systemctl restart nagios3
+# or
+service nagios3 restart
+
+# RHEL/CentOS/Source installation
+systemctl restart nagios
+# or
+service nagios restart
+\`\`\`
+
+3. After configuration is complete, Nagios will automatically push alerts to Flashduty when detected
+
+</div>
+
+## Status Mapping
+
+---
+
+<div class="md-block">
+
+Nagios to Flashduty alert severity mapping:
+
+| Nagios          | Flashduty | Status   |
+| --------------- | --------- | -------- |
+| CRITICAL        | Critical  | Critical |
+| DOWN            | Critical  | Critical |
+| UNREACHABLE     | Critical  | Critical |
+| WARNING         | Warning   | Warning  |
+| OK              | Ok        | Recovered |
+| UP              | Ok        | Recovered |
+| UNKNOWN         | Info      | Info     |
+
+</div>
+`,JDCloudMonitor:`---
+title: "JD Cloud Monitoring Alert Events"
+description: "Sync JD Cloud monitoring alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jdcloud-integration-guide"
+---
+
+Sync JD Cloud monitoring alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **JD Cloud Monitoring** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **JD Cloud Monitoring** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+
+</div>
+
+## In JD Cloud
+---
+
+### Step 1: Create Notification Template
+1. Login to your JD Cloud console, search for \`Monitoring\` product, and enter the corresponding product console.
+2. In the left menu, select \`Alarm Management->Notice Templates\`, and create or edit a notification template.
+3. Check \`Alert Callback\` on the template page, and enter the <span class='integration_url'>push URL</span> for the alert integration in the \`URL\` field.
+4. Enter the following template content in the \`POST\` input box.
+  \`\`\`
+    {
+      "resource_id": "\${resourceId}",
+      "request_id": "\${requestId}",
+      "metric": "\${metric}",
+      "current_value": "\${currentValue}",
+      "times": "\${times}",
+      "tags": "\${tags}",
+      "alert_time": "\${alertTime}",
+      "region": "\${region}",
+      "threshold": "\${threshold}",
+      "service_code": "\${serviceCode}",
+      "as_group_id": "\${asGroupId}",
+      "unhealthy_instance": "\${unhealthyInstance}",
+      "rule_policy_id": "\${rulePolicyId}",
+      "service_code_en": "\${serviceCodeEN}",
+      "service_code_cn": "\${serviceCodeCN}",
+      "level": "\${level}",
+      "resource_name": "\${resourceName}",
+      "ip_address": "\${ipAddress}",
+      "status": "\${status}"
+    }
+
+  \`\`\`
+5. Configure other options as needed.
+6. Click \`Save\` to complete the configuration.
+
+### Step 2: Configure Alert Rules
+1. Login to your JD Cloud console, search for \`Monitoring\` product, and enter the corresponding product console.
+2. In the left menu, select \`Alarm Management->Alarm Rules\`, and create or edit an alert rule.
+3. In the **Notification Policy** section of the rule configuration page, select \`Use Template\` and choose the template created in **Step 1**.
+4. Configure other options as needed.
+5. Click \`Save\` to complete the configuration.
+
+## Severity Mapping
+---
+<div class="md-block">
+
+JD Cloud Monitoring to Flashduty severity mapping:
+
+| JD Cloud Monitoring | Flashduty | Status   |
+| ------------------- | --------- | -------- |
+| Critical            | Critical  | Critical |
+| Major               | Warning   | Warning  |
+| General             | Info      | Info     |
+
+</div>
+`,AliyunPrometheus:`---
+title: "Alibaba Cloud Monitor Prometheus"
+description: "Sync Alibaba Cloud Monitor Prometheus alert events to Flashduty via webhook for automated alert noise reduction"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/aliyun-prometheus-integration-guide"
+---
+
+Sync Alibaba Cloud Monitor Prometheus alert events to Flashduty via webhook for automated alert noise reduction.
+
+<div class="hide">
+
+## In Flashduty
+---
+You can obtain an integration push URL through either of these two methods:
+
+### Using Private Integration
+
+Choose this method when you don't need to route alert events to different channels - it's simpler.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
+  2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
+  3. Choose **Alibaba Cloud Monitor Prometheus** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Push URL**, copy it for later use, and you're done
+  
+</details>
+
+### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event payload.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
+  2. Select **Alibaba Cloud Monitor Prometheus** integration:
+        - **Integration Name**: Define a name for this integration
+  3. Configure the default route and select the corresponding channel (after the integration is created, you can go to \`Route\` to configure more routing rules)
+  4. Click **Save** and copy the newly generated **push URL** for later use
+  5. Done
+    
+</details>
+
+</div>
+
+## In Alibaba Cloud
+---
+
+### Step 1: Create a Custom Webhook
+1. Login to your Alibaba Cloud console, search for \`Cloud Monitor\` product, and enter the corresponding product console.
+2. In the left menu, select \`Prometheus Monitoring->Notification Objects\`, and create or edit a \`Custom Webhook\`.
+3. On the edit page, enter \`Flashduty\` for both the name and identifier, and enter the <span class='integration_url'>push URL</span> for the alert integration in the \`URL\` field.
+4. In the \`Headers\` section, set **Header Key** to **Content-Type** and **Header Value** to **application/json**.
+5. Select **POST** for \`Method\` and **JSON** for \`Data Format\`.
+6. Click \`OK\` to complete the configuration.
+
+### Step 2: Configure Alert Rules
+1. Login to your Alibaba Cloud console, search for \`Cloud Monitor\` product, and enter the corresponding product console.
+2. In the left menu, select \`Prometheus Monitoring->Alert Rules\`, and create or edit an alert rule.
+3. In the **Notification Mode** section of the rule configuration page, select \`Simple Mode\`.
+4. For \`Notification Object\`, select the custom webhook created in **Step 1**.
+5. Click \`OK\` to complete the configuration.
+
+## Severity Mapping
+---
+<div class="md-block">
+
+Alibaba Cloud Prometheus to Flashduty severity mapping:
+
+| Alibaba Cloud Monitor | Flashduty | Status   |
+| --------------------- | --------- | -------- |
+| Critical              | Critical  | Critical |
+| Error                 | Critical  | Critical |
+| Warning               | Warning   | Warning  |
+| Normal                | Info      | Info     |
+
+</div>
 `};n.FlashDocsEn=h})(window);