Merge pull request #109 from flashcatcloud/f-nagios-dev

F nagios dev

Author: pijiang3

flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.0 Standard Alert Integration.md

@@ -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.

flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.1 Email Integration.md

@@ -98,3 +98,4 @@ attachment_stripped = true
 ---
 
 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).
+

flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.57 Nagios Integration.md

@@ -0,0 +1,269 @@
+---
+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>

flashduty/en/2. RUM/1. Getting Started/1. Introduction.md

@@ -9,37 +9,35 @@ url: "https://docs.flashcat.cloud/en/flashduty/rum/introduction?nav=01JCQ7A4N4WR
 
 ---
 
-Real User Monitoring (RUM) is an innovative technology that tracks and analyzes the actual experience of real users as they interact with your web applications. Unlike traditional simulation testing, RUM collects data directly from users' browsers, showing you how your application performs in real-world conditions.
+Real User Monitoring (RUM) is an innovative technology that tracks and analyzes the actual experience of real users as they interact with your Web and native applications. Unlike traditional simulation testing, RUM collects data directly from users, showing you how your application performs in real-world conditions.
 
-Flashduty RUM enables developers, operations engineers, and business stakeholders to gain intuitive insights into application performance, promptly identify issues, and continuously optimize user experience—all powered by real-time collection and analysis of end-user browser data.
+Flashduty RUM enables developers, operations engineers, and business stakeholders to gain intuitive insights into application performance, promptly identify issues, and continuously optimize user experience—all powered by real-time collection and analysis of end-user data.
 
 ### Core Benefits
 
-1. **Performance monitoring**: Monitor key performance metrics in real-time, including page load time, resource loading efficiency, and JavaScript execution status, to quickly identify bottlenecks affecting user experience.
-
-2. **Error monitoring**: Automatically capture JavaScript errors, network failures, and other issues impacting users, with rich contextual information to help quickly locate and resolve problems.
-
-3. **Insights**: Analyze performance of images, scripts, API calls, and other resources in depth to optimize loading speed, understand data trends, reduce bandwidth consumption, and minimize errors.
+1. **Quickly identify root causes**: Perform multi-dimensional drill-down analysis through the Session Explorer linking various events (page visits, resource loading, user interactions, etc.), combined with trace linking to connect frontend and backend data, quickly locating problem sources from user side to server side.
+2. **Comprehensively improve application stability**: Automatically capture JavaScript errors, client crashes, network failures, and other issues affecting users, providing rich contextual information to discover and resolve problems before they spread.
+3. **Continuously optimize user experience**: Master key performance metrics in real-time including page load time, resource loading efficiency, and JavaScript execution status, scientifically guiding performance optimization based on real user data, eliminating guesswork.
+4. **Data-driven decision optimization**: Deeply understand APP crash situations, resource performance, and data trends through analysis dashboards, providing reliable basis for product iteration and business decisions.
+5. **Build a complete observability system**: Deeply integrated with the Flashduty monitoring system, enabling incident alerts through collaboration spaces, connecting frontend and backend monitoring links, and establishing a unified observability platform.
 
 ## Why Choose Flashduty RUM?
 
 ---
 
-1. **Comprehensive visualization**: Gain a holistic understanding of application performance across different browsers, devices, and regions from the user's perspective.
-
-2. **Early warning**: Identify and resolve issues before they become widespread, significantly improving application stability.
+1. **Out-of-the-box**: Quick integration in 5 minutes, no complex configuration needed, supporting unified monitoring across Web, iOS, and Android, reducing integration and maintenance costs.
 
-3. **Data-driven**: Develop optimization strategies based on real user data, eliminating subjective assumptions.
+2. **Ecosystem integration**: Deeply integrated with Flashduty and Flashcat monitoring systems, enabling incident alerts through collaboration spaces, combined with trace linking to achieve end-to-end problem identification and analysis across frontend and backend, providing a one-stop observability solution.
 
-4. **Ecosystem integration**: Deeply integrated with the Flashduty monitoring system, enabling incident alerts through channels and combining trace tracking for end-to-end problem identification and analysis across frontend and backend.
+3. **Lightweight and efficient**: SDK uses a lightweight design that minimizes impact on user experience while ensuring complete data collection.
 
-5. **Lightweight and efficient**: JavaScript SDK uses a lightweight design that minimizes performance impact while ensuring robust data collection.
+4. **Flexible deployment**: Supports both SaaS cloud services and private deployment modes to meet different enterprise data security and compliance requirements.
 
 ## How RUM Works
 
 ---
 
-Flashduty RUM collects data by embedding a lightweight JavaScript SDK in your web application. The SDK primarily collects the following types of data:
+Flashduty RUM collects data by embedding a lightweight SDK in your Web application or native (Android, iOS) application. The SDK primarily collects the following types of data:
 
 1. **Page visits**: Records page loading processes, navigation timing, and user environment information.
 
@@ -49,7 +47,7 @@ Flashduty RUM collects data by embedding a lightweight JavaScript SDK in your we
 
 4. **Error information**: Captures JavaScript exceptions, network failures, and other issues.
 
-5. **Long task tracking**: Monitors time-consuming JavaScript tasks that might cause page stuttering.
+5. **Long task tracking**: Monitors time-consuming tasks that might cause page stuttering.
 
 This data is transmitted to the Flashduty backend in real-time for processing and analysis, ultimately presented as intuitive dashboards and reports to help you fully understand your application's performance and user experience.
 
@@ -58,5 +56,8 @@ This data is transmitted to the Flashduty backend in real-time for processing an
 To learn more about RUM capabilities and best practices, we recommend reading the following documentation:
 
 - [Quick Start](https://docs.flashcat.cloud/en/flashduty/rum/getting-started?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Build your user monitoring system from scratch and quickly optimize user experience.
+- [Web Integration](https://docs.flashcat.cloud/en/flashduty/rum/web-sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Quick integration for Web applications
+- [iOS Integration](https://docs.flashcat.cloud/en/flashduty/rum/ios-sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Quick integration for iOS applications
+- [Android Integration](https://docs.flashcat.cloud/en/flashduty/rum/android-sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Quick integration for Android applications
 - [Performance Monitoring](https://docs.flashcat.cloud/en/flashduty/rum/performance-overview?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Learn more about performance monitoring features.
-- [Error Tracking](https://docs.flashcat.cloud/en/flashduty/rum/error-tracking-overview?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Learn more about error tracking features. 
+- [Error Tracking](https://docs.flashcat.cloud/en/flashduty/rum/error-tracking-overview?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) — Learn more about error tracking features.

flashduty/en/2. RUM/1. Getting Started/2. Quick Start.md

@@ -13,7 +13,7 @@ Get started with Flashduty RUM in just a few simple steps:
 
 ### Basic Process
 
-![2025-05-16-10-12-35](https://docs-cdn.flashcat.cloud/imges/png/d07dcc491678ab93ca5fe2302631913a.png)
+![2026-01-14-16-52-12](https://docs-cdn.flashcat.cloud/imges/png/8ca04502f817c2aeae91df79a73dd5e4.png)
 
 ### Create a RUM Application
 
@@ -30,11 +30,10 @@ Visit [Application Management](https://docs.flashcat.cloud/en/flashduty/rum/appl
 After creating a RUM application, you need to integrate the SDK into your application:
 
 1. Get the SDK integration configuration information from the application details page
-2. Choose the appropriate SDK integration method based on your application type:
-   - npm package import
-   - CDN import
-
-Visit [SDK Documentation](https://docs.flashcat.cloud/en/flashduty/rum/sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) for detailed setup instructions.
+2. Choose the appropriate SDK integration method based on your application type. Learn more through the following links:
+   - [Web](https://docs.flashcat.cloud/en/flashduty/rum/web-sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5)
+   - [iOS](https://docs.flashcat.cloud/en/flashduty/rum/ios-sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5)
+   - [Android](https://docs.flashcat.cloud/en/flashduty/rum/android-sdk-integration?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5)
 
 ### Data Reporting
 
@@ -61,6 +60,4 @@ Visit [Performance Monitoring](https://docs.flashcat.cloud/en/flashduty/rum/perf
 
 ### Formal Subscription
 
-Currently, the RUM service is in whitelist public beta, and all features are completely free. When the public beta ends, we will notify you to switch to a formal subscription or cancel the trial.
-
-When officially launched, RUM will be charged based on the number of Sessions, and a certain level of free quota will be provided.
+RUM is charged based on the number of Sessions, and a certain level of free quota is provided.