chore: fix conflict

Author: ysyneu

docs.json

@@ -49,7 +49,8 @@
                   "zh/platform/pricing",
                   "zh/platform/team-members",
                   "zh/platform/permission-design",
-                  "zh/platform/configure-sso"
+                  "zh/platform/configure-sso",
+                  "zh/platform/audit-log"
                 ]
               },
               {
@@ -97,6 +98,7 @@
                   "zh/on-call/incident/search-view-incident",
                   "zh/on-call/incident/handle-update-incident",
                   "zh/on-call/incident/escalate-dispatch-incident",
+                  "zh/on-call/incident/alert-management",
                   "zh/on-call/incident/custom-actions",
                   "zh/on-call/incident/past-incidents",
                   "zh/on-call/incident/outlier-incidents"
@@ -105,7 +107,12 @@
               {
                 "group": "状态页",
                 "pages": [
-                  "zh/on-call/statuspage/statuspage"
+                  "zh/on-call/statuspage/statuspage",
+                  "zh/on-call/statuspage/create-manage-page",
+                  "zh/on-call/statuspage/components-sections",
+                  "zh/on-call/statuspage/publish-events",
+                  "zh/on-call/statuspage/templates",
+                  "zh/on-call/statuspage/subscriptions"
                 ]
               },
               {
@@ -367,6 +374,19 @@
                   "zh/monitors/quickstart/quickstart"
                 ]
               },
+              {
+                "group": "数据源",
+                "pages": [
+                  "zh/monitors/data-sources/data-sources"
+                ]
+              },
+              {
+                "group": "告警引擎",
+                "pages": [
+                  "zh/monitors/engine/engine",
+                  "zh/monitors/engine/engine-lost-alert"
+                ]
+              },
               {
                 "group": "告警规则",
                 "pages": [
@@ -381,6 +401,18 @@
                   "zh/monitors/alert-rules/victorialogs"
                 ]
               },
+              {
+                "group": "规则仓库",
+                "pages": [
+                  "zh/monitors/rule-repository/rule-repository"
+                ]
+              },
+              {
+                "group": "文件夹管理",
+                "pages": [
+                  "zh/monitors/folders/folders"
+                ]
+              },
               {
                 "group": "常见问题",
                 "pages": [
@@ -420,7 +452,8 @@
                   "en/platform/pricing",
                   "en/platform/team-members",
                   "en/platform/permission-design",
-                  "en/platform/configure-sso"
+                  "en/platform/configure-sso",
+                  "en/platform/audit-log"
                 ]
               },
               {
@@ -468,6 +501,7 @@
                   "en/on-call/incident/search-view-incident",
                   "en/on-call/incident/handle-update-incident",
                   "en/on-call/incident/escalate-dispatch-incident",
+                  "en/on-call/incident/alert-management",
                   "en/on-call/incident/custom-actions",
                   "en/on-call/incident/past-incidents",
                   "en/on-call/incident/outlier-incidents"
@@ -476,7 +510,12 @@
               {
                 "group": "Status Page",
                 "pages": [
-                  "en/on-call/statuspage/statuspage"
+                  "en/on-call/statuspage/statuspage",
+                  "en/on-call/statuspage/create-manage-page",
+                  "en/on-call/statuspage/components-sections",
+                  "en/on-call/statuspage/publish-events",
+                  "en/on-call/statuspage/templates",
+                  "en/on-call/statuspage/subscriptions"
                 ]
               },
               {
@@ -739,6 +778,19 @@
                   "en/monitors/quickstart/quickstart"
                 ]
               },
+              {
+                "group": "Data Sources",
+                "pages": [
+                  "en/monitors/data-sources/data-sources"
+                ]
+              },
+              {
+                "group": "Alert Engine",
+                "pages": [
+                  "en/monitors/engine/engine",
+                  "en/monitors/engine/engine-lost-alert"
+                ]
+              },
               {
                 "group": "Alert Rules",
                 "pages": [
@@ -753,6 +805,18 @@
                   "en/monitors/alert-rules/victorialogs"
                 ]
               },
+              {
+                "group": "Rule Repository",
+                "pages": [
+                  "en/monitors/rule-repository/rule-repository"
+                ]
+              },
+              {
+                "group": "Folder Management",
+                "pages": [
+                  "en/monitors/folders/folders"
+                ]
+              },
               {
                 "group": "FAQ",
                 "pages": [

en/monitors/data-sources/data-sources.mdx

@@ -0,0 +1,110 @@
+---
+title: "Data source management"
+description: "Configure and manage data sources for Monitors, including Prometheus, Elasticsearch, Loki, ClickHouse, MySQL, Oracle, PostgreSQL, and SLS"
+keywords: ["data source", "Prometheus", "Elasticsearch", "Loki", "ClickHouse", "MySQL", "Oracle", "PostgreSQL", "SLS"]
+---
+
+Data sources are where the alert engine queries data. You need to configure data sources first so the alert engine can read data from them for anomaly detection.
+
+**Menu Entry**: Data Sources
+
+## Supported data source types
+
+Monitors supports the following 8 data source types:
+
+| Type | Description |
+|------|-------------|
+| **Prometheus** | Time series database, queried via PromQL |
+| **Elasticsearch** | Distributed search and analytics engine |
+| **Loki** | Lightweight log aggregation system |
+| **ClickHouse** | Columnar analytics database |
+| **MySQL** | Relational database |
+| **Oracle** | Relational database |
+| **PostgreSQL** | Relational database |
+| **SLS** | Alibaba Cloud Log Service |
+
+## Data source list
+
+The data source list displays all configured data sources with the following information:
+
+- **Name**: The identifier for the data source
+- **Type**: Data source type with icon
+- **Connection URL**: The access address of the data source
+- **Associated Alert Engine**: The bound alert engine cluster name, with engine online status indicator
+- **Notes**: Supplementary description
+
+You can filter data sources by name or type using the search box. The list auto-refreshes every 5 seconds to reflect real-time engine connection status.
+
+## Create a data source
+
+<Steps>
+<Step title="Select data source type">
+Click the **New** button and select the data source type (e.g., Prometheus, MySQL) at the top of the form.
+</Step>
+<Step title="Fill in basic information">
+
+| Config Item | Description |
+|-------------|-------------|
+| **Name** | Unique identifier for the data source; alert rules reference data sources by name (wildcards supported) |
+| **Notes** | Optional supplementary description |
+| **Associated Alert Engine** | Select the engine cluster responsible for querying this data source; typically choose a cluster in the same datacenter |
+
+</Step>
+<Step title="Configure connection parameters">
+Fill in the connection parameters specific to the data source type. See the sections below for details.
+</Step>
+<Step title="Save">
+Click **OK** to complete creation.
+</Step>
+</Steps>
+
+<Warning>
+Data source names are used for association in alert rules (wildcard matching supported). Changing a data source name may cause existing alert rules to stop working. Please proceed with caution.
+</Warning>
+
+## Data source type configuration
+
+### Prometheus
+
+| Config Item | Description |
+|-------------|-------------|
+| **Server URL** | Prometheus server address, e.g., `http://localhost:9090` |
+| **Headers** | Custom HTTP request headers, supports multiple Key-Value pairs |
+| **Params** | Custom URL query parameters, supports multiple Key-Value pairs |
+| **Basic Authentication** | When enabled, requires username and password |
+| **Self-Signed Certificate** | When enabled, fill in CA certificate content |
+| **TLS Client Authentication** | When enabled, requires ServerName, client certificate, and client key |
+| **Skip TLS Certificate Validation** | Skip TLS certificate verification |
+
+### MySQL / Oracle / PostgreSQL
+
+Relational databases share a similar configuration structure:
+
+| Config Item | Description | Default |
+|-------------|-------------|---------|
+| **Connection URL** | Database address, e.g., `localhost:3306` (MySQL), `localhost:1521` (Oracle), `localhost:5432` (PostgreSQL) | - |
+| **Max Connections** | Maximum open connections in the connection pool | 32 |
+| **Idle Connections** | Maximum idle connections in the connection pool | 4 |
+| **Connection Lifetime (seconds)** | Maximum connection lifetime | 600 |
+| **Timeout (milliseconds)** | Query timeout | 5000 |
+| **Username** | Database username | - |
+| **Password** | Database password | - |
+
+Self-signed certificate and TLS client authentication configurations are also supported.
+
+### Elasticsearch / Loki / ClickHouse / SLS
+
+These data sources have connection configurations similar to Prometheus, including server address, authentication, and TLS settings. Refer to the creation form for specific parameters.
+
+## Test a data source
+
+In the data source list, click the **Test** button for the corresponding data source to open a query preview window, verify the connection, and preview query results.
+
+## Edit and delete
+
+- **Edit**: Click the **Edit** button in the data source list to modify the configuration and save.
+- **Delete**: Click the **Delete** button in the data source list and confirm to delete the data source.
+
+<Warning>
+Before deleting a data source, ensure no alert rules reference it, otherwise the related alert rules will not execute properly.
+</Warning>

en/monitors/engine/engine-lost-alert.mdx

@@ -0,0 +1,80 @@
+---
+title: "Engine disconnection alert"
+description: "Configure engine disconnection alert rules to receive timely notifications when the alert engine goes down"
+keywords: ["engine disconnection", "alert engine", "monitedge", "disconnection alert", "health check"]
+---
+
+If the alert engine (`monitedge`) goes down, alert rules cannot execute, which has a significant impact. The engine disconnection alert feature sends timely notifications when the engine goes down, ensuring the reliability of your monitoring system.
+
+**Menu Entry**: Alert Engine → Engine Disconnection Alert
+
+<Note>
+For an engine cluster composed of multiple instances, as long as at least one instance in the cluster is alive, the disconnection alert will not trigger. It only triggers when all instances in the cluster are disconnected.
+</Note>
+
+## Alert rule list
+
+The list displays all configured engine disconnection alert rules, with support for keyword search and customizable display columns.
+
+| Column | Description |
+|--------|-------------|
+| **Rule Name** | Name of the alert rule |
+| **Severity** | Critical (red), Warning (orange), Info (yellow) |
+| **Include Pattern** | Engine cluster name patterns to monitor; supports wildcard `*` |
+| **Exclude Pattern** | Engine cluster name patterns to exclude from monitoring |
+| **Lost Duration (seconds)** | Triggers an alert after the engine cluster has no heartbeat for this duration |
+| **Channel** | The channel where alert events are delivered |
+| **Trigger Count** | Maximum number of alert events to generate during disconnection |
+| **Trigger Interval (seconds)** | Time interval between repeated alert event generation |
+| **Enabled** | Enable/disable toggle for the rule |
+
+## Create an alert rule
+
+Click the **New** button to configure the following parameters in the side drawer:
+
+<Steps>
+<Step title="Basic information">
+
+| Config Item | Description | Default |
+|-------------|-------------|---------|
+| **Rule Name** | Rule name for identification and search | `monitedge lost` |
+| **Enabled** | Whether to enable this rule immediately | Enabled |
+
+</Step>
+<Step title="Severity">
+Select the severity level for alert events:
+
+- **Critical**: Urgent, typically used for core engines
+- **Warning**: Warning level, the default
+- **Info**: Informational level
+</Step>
+<Step title="Include and exclude rules">
+
+| Config Item | Description | Default |
+|-------------|-------------|---------|
+| **Include Pattern** | Enter engine cluster name patterns to monitor; supports multiple values; `*` matches all | `*` |
+| **Exclude Pattern** | Enter engine cluster name patterns to exclude | Empty |
+
+<Note>
+Include pattern and exclude pattern cannot both be empty.
+</Note>
+</Step>
+<Step title="Trigger conditions">
+
+| Config Item | Description | Default |
+|-------------|-------------|---------|
+| **Lost Duration (seconds)** | Triggers an alert when all instances in the cluster are disconnected for longer than this duration | 120 |
+| **Trigger Count** | Maximum number of alert events to repeatedly generate during continuous disconnection | 3 |
+| **Trigger Interval (seconds)** | Minimum time interval between each repeated alert event | 300 |
+
+</Step>
+<Step title="Channel">
+Select the channel where alert events should be delivered. Alert events are processed through Flashduty On-call channels for subsequent notification dispatch and handling.
+</Step>
+</Steps>
+
+## Edit and delete
+
+- **Edit**: Click the **Edit** button in the list to modify rule configuration. Only the rule creator, primary account, or admin roles can edit.
+- **Delete**: Click the **Delete** button in the list. Only the rule creator, primary account, or admin roles can delete.
+- **Enable/Disable**: Quickly toggle the rule status using the switch in the list.