Merge pull request #71 from flashcatcloud/f-0819

F 0819

Author: niuweili

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

@@ -0,0 +1,20 @@
+---
+title: "Monit Alert Integration"
+description: "Flashduty Monit alert integration, Monit service reports alerts through this integration"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/monit-alert-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+
+When you enable the Monit service, the system will automatically create this integration for you. This integration is used to collect alert events generated by the Monit service.
+
+:::tips
+You cannot modify or delete this integration. However, you can manage the label enrichment, alert pipeline, and routing rules under the integration.
+:::
+
+## How to Enable Monit Alerts
+
+Go to the `Monit` - `Alert Rules` - `Rule Details` page to configure monitoring metrics and threshold conditions, and enable alerts. You can choose to deliver alerts to multiple channels. Alert notification rules follow the escalation rules under the channel, and you can set responders for the team to assign to responders when alerts occur.
+
+![2025-08-19-20-35-45](https://docs-cdn.flashcat.cloud/images/png/59c9d2566db9a0482fb2eabb729ea739.png)
+
+In some cases, you may want to route alerts generated by the same alert rule to different channels based on conditions. In this case, you can choose to deliver alerts directly to the integration rather than to the channels, and set routing rules under the current integration.

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

@@ -0,0 +1,20 @@
+---
+title: "RUM Alert Integration"
+description: "Flashduty RUM alert integration, RUM service reports alerts through this integration"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/rum-alert-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+
+When you enable the RUM service, the system will automatically create this integration for you. This integration is used to collect alert events generated by the RUM service.
+
+:::tips
+You cannot modify or delete this integration. However, you can manage the label enrichment, alert pipeline, and routing rules under the integration.
+:::
+
+## How to Enable RUM Alerts
+
+Go to the `RUM` - `Application Details` - `Alert Settings` page to enable alerts. You can choose to deliver alerts to multiple channels. Alert notification rules follow the escalation rules under the channel, and you can set responders for the team to assign to responders when alerts occur.
+
+![2025-08-20-10-16-14](https://docs-cdn.flashcat.cloud/images/png/b6ad24809a2ee8f0b3c0b38988b46030.png)
+
+For more information, please refer to [RUM Issue Alerting](https://docs.flashcat.cloud/en/flashduty/rum/issue-alerting?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).

flashduty/en/1. On-call/8. Integrations/8.5 Webhooks/8.5.2 Incident webhook.md

@@ -98,7 +98,7 @@ acknowledged_at | int64| No | Acknowledgment time
 |      fields       |  map[string]interface{}  |  No   | Custom field key-value pairs, Key is string, Value can be any type depending on field type |
 |      creator      |  [Person](#Person)  |  No   | Creator information, exists only for manually created incidents |
 |       closer      |  [Person](#Person)  |  No   | Closer information, exists only for manually closed incidents |
-|    responders     | [][Responder](#Responder) |  No   | List of responder information |
+|    responders     | [][Responder](#Responder) |  No   | List of responder information, only exists after the incident is assigned. For i_new events, this value may be empty |
 |     alert_cnt     |        int64        |  No   | Number of associated alerts |
 |     channel_id     |        int64        |  No   | Channel ID, 0 means not belonging to any channel |
 |     channel_name   |        string        |  No   | Channel name |

flashduty/en/2. RUM/4. Error Tracking/7. Issue Alerting.md

@@ -15,7 +15,7 @@ You can perform daily inspections of aggregated Issues in the console, or config
 
 Navigate to the `Application Details` - `Alert Settings` page to enable alerts. You can choose to deliver alerts to multiple collaboration spaces. Alert notification rules follow the dispatch strategy under the collaboration space. You can set up on-call personnel for your team, so alerts will be assigned to the person on duty when they occur.
 
-![2025-05-20-10-53-57](https://docs-cdn.flashcat.cloud/images/png/2bbd455a2ac702246e8399b6628f9158.png)
+![2025-08-20-10-16-14](https://docs-cdn.flashcat.cloud/images/png/b6ad24809a2ee8f0b3c0b38988b46030.png)
 
 :::tip
 You must activate the On-call service to enable Issue alerts. Note that the On-call service charges based on active users, but members without licenses can still receive alert notifications, as even the free version has basic notification capabilities.

flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.49 Monit 告警集成指引.md

@@ -0,0 +1,20 @@
+---
+title: "Monit 告警集成"
+description: "Flashduty Monit 告警集成，Monit 服务通过此集成上报告警"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/monit-alert-integration-guide"
+---
+
+当您开通 Monit 服务时，系统会自动为您创建此集成。此集成用于收集 Monit 服务产生的告警事件。
+
+:::tips
+您无法修改或删除此集成。但您可以管理集成下的标签增强、告警处理以及路由等规则。
+:::
+
+## 如何开启 Monit 告警
+
+前往`Monit`-`告警规则`-`规则详情`页面，配置监控指标和阈值等条件，并开启告警。您可以选择将告警投递至多个协作空间。告警的通知规则遵循协作空间下的分派策略，您可以为团队设定值班人员，在告警发生时分派给值班人。
+
+![2025-08-19-20-35-45](https://docs-cdn.flashcat.cloud/images/png/59c9d2566db9a0482fb2eabb729ea739.png)
+
+某些情况下，您可能希望将同一个告警规则产生的告警，按条件路由到不同的协作空间，这个时候您可以选择将告警直接投递到集成，而非协作空间列表。并在当前集成下，设置路由规则。

flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.50 RUM 告警集成指引.md

@@ -0,0 +1,20 @@
+---
+title: "RUM 告警集成"
+description: "Flashduty RUM 告警集成，RUM 服务通过此集成上报告警"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/rum-alert-integration-guide"
+---
+
+当您开通 RUM 服务时，系统会自动为您创建此集成。此集成用于收集 RUM 服务产生的告警事件。
+
+:::tips
+您无法修改或删除此集成。但您可以管理集成下的标签增强、告警处理以及路由等规则。
+:::
+
+## 如何开启 RUM 告警
+
+前往`RUM`-`应用详情`-`告警设置`页面，开启告警。您可以选择将告警投递至多个协作空间。告警的通知规则遵循协作空间下的分派策略，您可以为团队设定值班人员，在告警发生时分派给值班人。
+
+![2025-05-20-10-53-57](https://docs-cdn.flashcat.cloud/images/png/2bbd455a2ac702246e8399b6628f9158.png)
+
+更多内容，请您参考 [RUM Issue 告警](https://docs.flashcat.cloud/zh/flashduty/rum/issue-alerting)。

flashduty/zh/1. On-call/5. 集成引导/8.5 Webhooks/8.5.2 故障 webhook.md

@@ -98,7 +98,7 @@ acknowledged_at | int64| 否 | 认领时间
 |      fields       |  map[string]interface{}  |  否  | 自定义字段 KV，Key 为字符串，Value 可能为任意类型，取决于字段类型|
 |      creator      |  [Person](#Person)  |  否  | 创建人员信息，仅手动创建故障时存在 |
 |       closer      |  [Person](#Person)  |  否  | 关闭人员信息，仅手动关闭故障时存在 |
-|    responders     | [][Responder](#Responder) |  否  | 处理人员信息列表 |
+|    responders     | [][Responder](#Responder) |  否  | 处理人员信息列表，仅故障被分派后存在。对于i_new事件，此值可能为空 |
 |     alert_cnt     |        int64        |  否  | 关联告警个数 |
 |     channel_id     |        int64        |  否  | 协作空间ID，为0代表不属于任何空间 |
 |     channel_name   |        string        |  否  | 协作空间名称 |

package.json

@@ -1,6 +1,6 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "flashduty knowledge base",
   "type": "module",
   "engines": {

src/en.ts

@@ -48,6 +48,8 @@ import ElastAlert2 from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts i
 import DingtalkAlert from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.46 DingtalkAlert Integration.md?raw";
 import FeishuAlert from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.47 Feishu(Lark)Alert Integration.md?raw";
 import VolcEngineDetect from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.48 Volcengine Detect Integration.md?raw";
+import Monit from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.49 Monit Alert Integration.md?raw";
+import Rum from "../flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.50 RUM Alert Integration.md?raw";
 /** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
 
 /** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -144,5 +146,7 @@ const docs = {
   VolcEngineDetect,
   Link,
   ServiceNowSync,
+  Monit,
+  Rum
 };
 export default docs;

src/zh.ts

@@ -48,6 +48,8 @@ import ElastAlert2 from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警
 import DingtalkAlert from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.46 钉钉告警集成指引.md?raw";
 import FeishuAlert from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.47 飞书 Lark 告警集成指引.md?raw";
 import VolcEngineDetect from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.48 火山引擎云拨测集成指引.md?raw";
+import Monit from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.49 Monit 告警集成指引.md?raw";
+import Rum from "../flashduty/zh/1. On-call/5. 集成引导/8.1 告警集成/8.1.50 RUM 告警集成指引.md?raw";
 /** ⬆️⬆️⬆️⬆️ 告警集成 ⬆️⬆️⬆️⬆️ */
 
 /** ⬇️⬇️⬇️⬇️ 变更事件 ⬇️⬇️⬇️⬇️ */
@@ -75,7 +77,7 @@ import ServiceNowSync from "../flashduty/zh/1. On-call/5. 集成引导/8.5 Webho
 import Templates from "../flashduty/zh/1. On-call/3. 配置管理/4.7 配置通知模板.md?raw";
 
 /** ⬇️⬇️⬇️⬇️ Other ⬇️⬇️⬇️⬇️ */
-import Link from  "../flashduty/zh/1. On-call/5. 集成引导/8.6 其他集成/8.6.1 Link 集成指引.md?raw";
+import Link from "../flashduty/zh/1. On-call/5. 集成引导/8.6 其他集成/8.6.1 Link 集成指引.md?raw";
 /** ⬆️⬆️⬆️⬆️ Other ⬆️⬆️⬆️⬆️ */
 
 const docs = {
@@ -142,5 +144,7 @@ const docs = {
   VolcEngineDetect,
   Link,
   ServiceNowSync,
+  Monit,
+  Rum,
 };
-export default docs;
+export default docs;