From 4c9812411fe019039196a9d6c86b42e7fec2cdad Mon Sep 17 00:00:00 2001 From: Flashduty AI-SRE Date: Fri, 2 Oct 2026 02:06:04 +0000 Subject: [PATCH 1/2] =?UTF-8?q?docs(doc-review):=20daily=20incremental=20r?= =?UTF-8?q?eview=202026-10-02=20(diff)=20=E2=80=94=20AI=20SRE=20nav,=20con?= =?UTF-8?q?text=20file=20tree,=20borrowed-integration=20vendor=20cards?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Window: 2026-09-30T16:35:38Z -> 2026-10-02T02:03Z Findings: 6 total (1 medium, 5 low) — 3 applied, 2 skipped, 1 cross-repo - environments/quickstart: the self-hosted/cloud switch moved from top tabs to a left menu; the docs still pointed at a tab at the top of the page. - knowledge: the Context page's file panel is now a collapsible directory tree (DUTY.md pinned, folders before files); the docs described a flat list. - integrate-data (+ quickstart step two): the integration-type picker now also lists 28 vendor doc-cards that borrow another integration type; documented the list, alias search and what actually gets saved. - cubeapm / red-hat-openshift: the disambiguation clause was copy-pasted from chronosphere.mdx ("not Chronosphere"); corrected in both locales. --- en/ai-sre/environments.mdx | 2 +- en/ai-sre/knowledge.mdx | 2 +- en/ai-sre/quickstart.mdx | 2 +- en/on-call/channel/integrate-data.mdx | 41 ++++++++++++++++++- .../alert-sources/cubeapm.mdx | 2 +- .../alert-sources/red-hat-openshift.mdx | 2 +- zh/ai-sre/environments.mdx | 2 +- zh/ai-sre/knowledge.mdx | 2 +- zh/ai-sre/quickstart.mdx | 2 +- zh/on-call/channel/integrate-data.mdx | 41 ++++++++++++++++++- .../alert-sources/cubeapm.mdx | 2 +- .../alert-sources/red-hat-openshift.mdx | 2 +- 12 files changed, 88 insertions(+), 14 deletions(-) diff --git a/en/ai-sre/environments.mdx b/en/ai-sre/environments.mdx index 4903e7e97..7ba800b67 100644 --- a/en/ai-sre/environments.mdx +++ b/en/ai-sre/environments.mdx @@ -59,7 +59,7 @@ For lifecycle, egress boundaries, and session-selection details, see [Sandbox](/ A cloud environment template is a reusable, predefined configuration for the Flashduty-managed cloud Sandbox: egress policy, environment variables, and a setup script. If a session's cloud Sandbox has no template bound, it starts with the system default configuration; once a template is bound, new Sandboxes start with that template's configuration. -Go to **Environments** in the AI SRE sidebar and switch to the **Cloud** tab at the top to view, create, edit, or delete cloud environment templates. +Go to **Environments** in the AI SRE sidebar and pick **Cloud** from its menu to view, create, edit, or delete cloud environment templates. ### Create a cloud environment template diff --git a/en/ai-sre/knowledge.mdx b/en/ai-sre/knowledge.mdx index 7585cfdf3..013945de5 100644 --- a/en/ai-sre/knowledge.mdx +++ b/en/ai-sre/knowledge.mdx @@ -73,7 +73,7 @@ After reading `DUTY.md`, the agent decides which `@references` to expand based o Open **Context**. The knowledge base appears under Shared, and under a Team that already has one. Personal scope has no knowledge base. -Files are on the left. The body and the last edit time are on the right. `DUTY.md` is the guide, and every session reads it. The pencil edits the open file, and saving writes it. +Files are on the left, grouped into an expandable directory tree — folders collapse and expand, `DUTY.md` is pinned to the top (shown as the guide), and the rest are sorted by folder and then by name. The body and the last edit time are on the right. `DUTY.md` is the guide, and every session reads it. The pencil edits the open file, and saving writes it. You can also describe a change in the box at the bottom of the page. The system shows what it would write, and it saves only after you confirm. The change is to a knowledge file already in this scope. diff --git a/en/ai-sre/quickstart.mdx b/en/ai-sre/quickstart.mdx index 78d46a961..ed735b6fa 100644 --- a/en/ai-sre/quickstart.mdx +++ b/en/ai-sre/quickstart.mdx @@ -102,7 +102,7 @@ By default the agent only sees Flashduty's own data. To let it query your actual - Go to **AI SRE → Environments** and click **Create** on the **Self-hosted** tab. The name is optional (the first heartbeat fills it in with the machine's hostname); pick Shared (account-level) or team scope. + Go to **AI SRE → Environments**, pick **Self-hosted** from the menu, and click **Create**. The name is optional (the first heartbeat fills it in with the machine's hostname); pick Shared (account-level) or team scope. After creation, the **setup guide** opens with install commands that already include your Token — a Linux one-liner (needs sudo; registers a systemd service), plus Docker and macOS variants. Copy it onto a machine that can reach your target resources and run it. diff --git a/en/on-call/channel/integrate-data.mdx b/en/on-call/channel/integrate-data.mdx index 463bfcb2b..446784ace 100644 --- a/en/on-call/channel/integrate-data.mdx +++ b/en/on-call/channel/integrate-data.mdx @@ -35,7 +35,7 @@ Integration created within a channel, alerts automatically enter that channel. Go to Channel Details → Configuration → Integrations → **Private integration** - Click **Add an integration**, select alert type + Click **Add an integration** and select the alert type (the list also carries vendor cards that ride on another integration — see [Vendors that ride on another integration](#vendors-that-ride-on-another-integration)) Copy the generated **Push URL** to your monitoring platform @@ -55,7 +55,7 @@ Global integration created in the Integration Center, distributes alerts to diff Go to Integration Center → Alert Events → **Add Integration** - Select alert type, set **Management Team** (optional) + Select the alert type (vendor cards that ride on another integration show up here too), set **Management Team** (optional) Copy the generated **Push URL** to your monitoring platform @@ -73,6 +73,43 @@ Shared integrations must have at least one routing rule configured, otherwise al Shared Integration +### Vendors that ride on another integration + +Some vendors have no integration type of their own; they ingest through a compatible one. Their cards appear in the selection list above alongside the integration types, and they are searchable too — by vendor name and by common aliases such as `VSPC`, `PDU`, `WUG`, `UPS`, `OCP`, `Azure Sentinel`, and `Bro`. + +Opening a vendor card still lands on the creation page of the borrowed integration type, with the right-hand doc panel showing that vendor's own guide; **what gets saved is the borrowed integration type**, not the vendor name. The 28 vendors below work this way. + +| Vendor card | Borrowed integration type | +| :--- | :--- | +| [Last9](/en/on-call/integration/alert-integration/alert-sources/last9) | PagerDuty | +| [SigNoz](/en/on-call/integration/alert-integration/alert-sources/signoz) | Prometheus | +| [Veeam ONE](/en/on-call/integration/alert-integration/alert-sources/veeam-one) | Email | +| [Veeam Service Provider Console](/en/on-call/integration/alert-integration/alert-sources/veeam-service-provider-console) | Email | +| [Raritan PX](/en/on-call/integration/alert-integration/alert-sources/raritan-px) | Email | +| [WhatsUp Gold](/en/on-call/integration/alert-integration/alert-sources/whatsup-gold) | Email | +| [Flowmon ADS](/en/on-call/integration/alert-integration/alert-sources/flowmon-ads) | Email | +| [IBM QRadar](/en/on-call/integration/alert-integration/alert-sources/ibm-qradar) | Email | +| [OPNsense](/en/on-call/integration/alert-integration/alert-sources/opnsense) | Email | +| [NUT](/en/on-call/integration/alert-integration/alert-sources/nut) | Standard Alert Event | +| [apcupsd](/en/on-call/integration/alert-integration/alert-sources/apcupsd) | Standard Alert Event | +| [Opsview](/en/on-call/integration/alert-integration/alert-sources/opsview) | Standard Alert Event | +| [Fail2ban](/en/on-call/integration/alert-integration/alert-sources/fail2ban) | Standard Alert Event | +| [Microsoft Sentinel](/en/on-call/integration/alert-integration/alert-sources/microsoft-sentinel) | Standard Alert Event | +| [Microsoft Defender for Cloud](/en/on-call/integration/alert-integration/alert-sources/microsoft-defender-for-cloud) | Standard Alert Event | +| [Centreon](/en/on-call/integration/alert-integration/alert-sources/centreon) | PagerDuty | +| [AWS Health](/en/on-call/integration/alert-integration/alert-sources/aws-health) | AWS EventBridge | +| [AWS Security Hub](/en/on-call/integration/alert-integration/alert-sources/aws-security-hub) | AWS EventBridge | +| [Amazon Inspector](/en/on-call/integration/alert-integration/alert-sources/amazon-inspector) | AWS EventBridge | +| [Azure Service Health](/en/on-call/integration/alert-integration/alert-sources/azure-service-health) | Azure Monitor | +| [GCP Personalized Service Health](/en/on-call/integration/alert-integration/alert-sources/gcp-personalized-service-health) | Google Cloud Monitoring | +| [Suricata](/en/on-call/integration/alert-integration/alert-sources/suricata) | Wazuh | +| [Check Point SmartEvent](/en/on-call/integration/alert-integration/alert-sources/check-point-smartevent) | Email | +| [OSSEC](/en/on-call/integration/alert-integration/alert-sources/ossec) | Email | +| [Zeek](/en/on-call/integration/alert-integration/alert-sources/zeek) | Email | +| [Chronosphere](/en/on-call/integration/alert-integration/alert-sources/chronosphere) | Prometheus | +| [CubeAPM](/en/on-call/integration/alert-integration/alert-sources/cubeapm) | Prometheus | +| [Red Hat OpenShift](/en/on-call/integration/alert-integration/alert-sources/red-hat-openshift) | Prometheus | + ## Integration Features Optional configurations for both integration methods, configurable on the integration details page: diff --git a/en/on-call/integration/alert-integration/alert-sources/cubeapm.mdx b/en/on-call/integration/alert-integration/alert-sources/cubeapm.mdx index bed8e3d7f..184ce35d9 100644 --- a/en/on-call/integration/alert-integration/alert-sources/cubeapm.mdx +++ b/en/on-call/integration/alert-integration/alert-sources/cubeapm.mdx @@ -11,7 +11,7 @@ CubeAPM can send alert notifications by HTTP POST to any webhook URL. The defaul ## In Flashduty On-call --- -Get an integration push URL in either of the two ways below. **Choose the Prometheus integration type** in both, not Chronosphere. +Get an integration push URL in either of the two ways below. **Choose the Prometheus integration type** in both, not CubeAPM. ### Use a dedicated integration diff --git a/en/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx b/en/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx index 1c8818248..3a9c48769 100644 --- a/en/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx +++ b/en/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx @@ -11,7 +11,7 @@ The OpenShift Container Platform monitoring stack ships its own Alertmanager (`a ## In Flashduty On-call --- -Get an integration push URL in either of the two ways below. **Choose the Prometheus integration type** in both, not Chronosphere. +Get an integration push URL in either of the two ways below. **Choose the Prometheus integration type** in both, not Red Hat OpenShift. ### Use a dedicated integration diff --git a/zh/ai-sre/environments.mdx b/zh/ai-sre/environments.mdx index 91af4c8c7..469261785 100644 --- a/zh/ai-sre/environments.mdx +++ b/zh/ai-sre/environments.mdx @@ -59,7 +59,7 @@ AI SRE 提供两类运行环境： 云端环境模板是为 Flashduty 托管的云端 Sandbox 预定义的可复用配置：出口网络策略、环境变量与启动脚本。会话使用的云端 Sandbox 如果没有绑定模板，就用系统默认配置启动；绑定了模板后，新建的 Sandbox 会按模板配置启动。 -在 AI SRE 左侧菜单进入 **Environments**，切换到顶部的**云端**标签页，即可查看、创建、编辑或删除云端环境模板。 +在 AI SRE 左侧菜单进入 **Environments**，再在菜单里选择 **云端**，即可查看、创建、编辑或删除云端环境模板。 ### 创建云端环境模板 diff --git a/zh/ai-sre/knowledge.mdx b/zh/ai-sre/knowledge.mdx index 4bfd7e5d2..c4084cb4f 100644 --- a/zh/ai-sre/knowledge.mdx +++ b/zh/ai-sre/knowledge.mdx @@ -73,7 +73,7 @@ Agent 读取 `DUTY.md` 后，会根据当前故障判断需要展开哪些 `@引 打开 **上下文**。知识库出现在「共享」和已经有知识库的「团队」里。个人范围没有知识库。 -左侧是文件，右侧是正文和上次修改时间。`DUTY.md` 是使用说明，每次会话都会读到它。点铅笔可以改当前这份文件，保存后写入。 +左侧是文件，右侧是正文和上次修改时间。文件按路径分组为可展开的目录树——目录可以折叠与展开，`DUTY.md` 固定置顶（显示为「使用说明」），其余文件按目录归类、同级按名称排序。`DUTY.md` 是使用说明，每次会话都会读到它。点铅笔可以改当前这份文件，保存后写入。 也可以在页面底部用一句话说明要改什么。系统先给出将要写入的内容，确认后才保存。改的是这个范围里已有的知识文件。 diff --git a/zh/ai-sre/quickstart.mdx b/zh/ai-sre/quickstart.mdx index 2d1e310b5..22f3a2269 100644 --- a/zh/ai-sre/quickstart.mdx +++ b/zh/ai-sre/quickstart.mdx @@ -102,7 +102,7 @@ Agent 每次排障都从零猜「这是什么服务」「谁负责」「以前 - 进入 **AI SRE → Environments**，在 **自托管** 标签页点击 **创建**。名称可以留空（Runner 首次连接后会自动用主机名命名），范围选共享（即账户级）或团队。 + 进入 **AI SRE → Environments**，在左侧菜单选择 **自托管**，点击 **创建**。名称可以留空（Runner 首次连接后会自动用主机名命名），范围选共享（即账户级）或团队。 创建成功后弹出**接入指引**，里面是已带 Token 的安装命令——Linux 一条命令装完（需要 sudo，会注册为 systemd 服务），也提供 Docker 和 macOS 方式。复制到能访问目标资源的机器上执行。 diff --git a/zh/on-call/channel/integrate-data.mdx b/zh/on-call/channel/integrate-data.mdx index fabaa3180..f98a6d8c4 100644 --- a/zh/on-call/channel/integrate-data.mdx +++ b/zh/on-call/channel/integrate-data.mdx @@ -36,7 +36,7 @@ Flashduty On-call 提供两种告警接入方式： 进入 协作空间详情 → 配置 → 集成数据 → **专属集成** - 点击 **新增一个集成**，选择告警类型 + 点击 **新增一个集成**，选择告警类型（列表中还有借用其它集成接入的厂商卡片，见 [借用其它集成接入的厂商](#借用其它集成接入的厂商)） 复制生成的 **推送地址** 到监控平台 @@ -56,7 +56,7 @@ Flashduty On-call 提供两种告警接入方式： 进入 集成中心 → 告警事件 → **添加集成** - 选择告警类型，设置 **管理团队**（可选） + 选择告警类型（列表中同样有借用其它集成接入的厂商卡片），设置 **管理团队**（可选） 复制生成的 **推送地址** 到监控平台 @@ -74,6 +74,43 @@ Flashduty On-call 提供两种告警接入方式： 共享集成 +### 借用其它集成接入的厂商 + +有些厂商没有自己的集成类型，而是借用兼容的集成类型接入。它们的卡片与集成类型卡片一起出现在上面的选择列表里，也一起参与搜索：除了厂商名，还可以按常见别名找到，例如 `VSPC`、`PDU`、`WUG`、`UPS`、`OCP`、`Azure Sentinel`、`Bro` 等。 + +点开厂商卡片，打开的仍是所借用集成类型的创建页，右侧文档面板改为显示该厂商自己的文档；**最终保存的集成类型是借用的那个**，不是厂商名。下面 28 个厂商属于这一类。 + +| 厂商卡片 | 借用集成类型 | +| :--- | :--- | +| [Last9](/zh/on-call/integration/alert-integration/alert-sources/last9) | PagerDuty | +| [SigNoz](/zh/on-call/integration/alert-integration/alert-sources/signoz) | Prometheus | +| [Veeam ONE](/zh/on-call/integration/alert-integration/alert-sources/veeam-one) | 邮件 Email | +| [Veeam Service Provider Console](/zh/on-call/integration/alert-integration/alert-sources/veeam-service-provider-console) | 邮件 Email | +| [Raritan PX](/zh/on-call/integration/alert-integration/alert-sources/raritan-px) | 邮件 Email | +| [WhatsUp Gold](/zh/on-call/integration/alert-integration/alert-sources/whatsup-gold) | 邮件 Email | +| [Flowmon ADS](/zh/on-call/integration/alert-integration/alert-sources/flowmon-ads) | 邮件 Email | +| [IBM QRadar](/zh/on-call/integration/alert-integration/alert-sources/ibm-qradar) | 邮件 Email | +| [OPNsense](/zh/on-call/integration/alert-integration/alert-sources/opnsense) | 邮件 Email | +| [NUT](/zh/on-call/integration/alert-integration/alert-sources/nut) | 标准告警事件 | +| [apcupsd](/zh/on-call/integration/alert-integration/alert-sources/apcupsd) | 标准告警事件 | +| [Opsview](/zh/on-call/integration/alert-integration/alert-sources/opsview) | 标准告警事件 | +| [Fail2ban](/zh/on-call/integration/alert-integration/alert-sources/fail2ban) | 标准告警事件 | +| [Microsoft Sentinel](/zh/on-call/integration/alert-integration/alert-sources/microsoft-sentinel) | 标准告警事件 | +| [Microsoft Defender for Cloud](/zh/on-call/integration/alert-integration/alert-sources/microsoft-defender-for-cloud) | 标准告警事件 | +| [Centreon](/zh/on-call/integration/alert-integration/alert-sources/centreon) | PagerDuty | +| [AWS Health](/zh/on-call/integration/alert-integration/alert-sources/aws-health) | AWS EventBridge | +| [AWS Security Hub](/zh/on-call/integration/alert-integration/alert-sources/aws-security-hub) | AWS EventBridge | +| [Amazon Inspector](/zh/on-call/integration/alert-integration/alert-sources/amazon-inspector) | AWS EventBridge | +| [Azure Service Health](/zh/on-call/integration/alert-integration/alert-sources/azure-service-health) | Azure Monitor | +| [GCP Personalized Service Health](/zh/on-call/integration/alert-integration/alert-sources/gcp-personalized-service-health) | Google Cloud Monitoring | +| [Suricata](/zh/on-call/integration/alert-integration/alert-sources/suricata) | Wazuh | +| [Check Point SmartEvent](/zh/on-call/integration/alert-integration/alert-sources/check-point-smartevent) | 邮件 Email | +| [OSSEC](/zh/on-call/integration/alert-integration/alert-sources/ossec) | 邮件 Email | +| [Zeek](/zh/on-call/integration/alert-integration/alert-sources/zeek) | 邮件 Email | +| [Chronosphere](/zh/on-call/integration/alert-integration/alert-sources/chronosphere) | Prometheus | +| [CubeAPM](/zh/on-call/integration/alert-integration/alert-sources/cubeapm) | Prometheus | +| [Red Hat OpenShift](/zh/on-call/integration/alert-integration/alert-sources/red-hat-openshift) | Prometheus | + ## 集成功能 两种集成方式的可选配置，可在集成详情页中配置： diff --git a/zh/on-call/integration/alert-integration/alert-sources/cubeapm.mdx b/zh/on-call/integration/alert-integration/alert-sources/cubeapm.mdx index 22508a146..3a2fb1c9f 100644 --- a/zh/on-call/integration/alert-integration/alert-sources/cubeapm.mdx +++ b/zh/on-call/integration/alert-integration/alert-sources/cubeapm.mdx @@ -11,7 +11,7 @@ CubeAPM 支持把告警通知以 HTTP POST 的方式发送到任意 Webhook URL ## 在 Flashduty On-call --- -您可通过以下两种方式获取集成推送地址，任选其一即可。**集成类型都选择 Prometheus**，不是 Chronosphere。 +您可通过以下两种方式获取集成推送地址，任选其一即可。**集成类型都选择 Prometheus**，不是 CubeAPM。 ### 使用专属集成 diff --git a/zh/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx b/zh/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx index edd0d2e20..188fa2670 100644 --- a/zh/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx +++ b/zh/on-call/integration/alert-integration/alert-sources/red-hat-openshift.mdx @@ -11,7 +11,7 @@ OpenShift Container Platform 的监控栈自带 Alertmanager（`openshift-monito ## 在 Flashduty On-call --- -您可通过以下两种方式获取集成推送地址，任选其一即可。**集成类型都选择 Prometheus**，不是 Chronosphere。 +您可通过以下两种方式获取集成推送地址，任选其一即可。**集成类型都选择 Prometheus**，不是 Red Hat OpenShift。 ### 使用专属集成 From 0b5007498b8ffa909db9f201cc96a90e85211027 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Mon, 5 Oct 2026 20:07:42 -0700 Subject: [PATCH 2/2] docs(integrations): add Kapacitor to the borrowed-integration vendor table (29 vendors) --- en/on-call/channel/integrate-data.mdx | 3 ++- zh/on-call/channel/integrate-data.mdx | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/en/on-call/channel/integrate-data.mdx b/en/on-call/channel/integrate-data.mdx index 68f0bc61f..60699cfdb 100644 --- a/en/on-call/channel/integrate-data.mdx +++ b/en/on-call/channel/integrate-data.mdx @@ -81,7 +81,7 @@ Shared integrations must have at least one routing rule configured, otherwise al Some vendors have no integration type of their own; they ingest through a compatible one. Their cards appear in the selection list above alongside the integration types, and they are searchable too — by vendor name and by common aliases such as `VSPC`, `PDU`, `WUG`, `UPS`, `OCP`, `Azure Sentinel`, and `Bro`. -Opening a vendor card still lands on the creation page of the borrowed integration type, with the right-hand doc panel showing that vendor's own guide; **what gets saved is the borrowed integration type**, not the vendor name. The 28 vendors below work this way. +Opening a vendor card still lands on the creation page of the borrowed integration type, with the right-hand doc panel showing that vendor's own guide; **what gets saved is the borrowed integration type**, not the vendor name. The 29 vendors below work this way. | Vendor card | Borrowed integration type | | :--- | :--- | @@ -113,6 +113,7 @@ Opening a vendor card still lands on the creation page of the borrowed integrati | [Chronosphere](/en/on-call/integration/alert-integration/alert-sources/chronosphere) | Prometheus | | [CubeAPM](/en/on-call/integration/alert-integration/alert-sources/cubeapm) | Prometheus | | [Red Hat OpenShift](/en/on-call/integration/alert-integration/alert-sources/red-hat-openshift) | Prometheus | +| [Kapacitor](/en/on-call/integration/alert-integration/alert-sources/kapacitor) | InfluxData | ## Integration Features diff --git a/zh/on-call/channel/integrate-data.mdx b/zh/on-call/channel/integrate-data.mdx index f3f3d4fab..c52aba55c 100644 --- a/zh/on-call/channel/integrate-data.mdx +++ b/zh/on-call/channel/integrate-data.mdx @@ -82,7 +82,7 @@ Flashduty On-call 提供两种告警接入方式： 有些厂商没有自己的集成类型，而是借用兼容的集成类型接入。它们的卡片与集成类型卡片一起出现在上面的选择列表里，也一起参与搜索：除了厂商名，还可以按常见别名找到，例如 `VSPC`、`PDU`、`WUG`、`UPS`、`OCP`、`Azure Sentinel`、`Bro` 等。 -点开厂商卡片，打开的仍是所借用集成类型的创建页，右侧文档面板改为显示该厂商自己的文档；**最终保存的集成类型是借用的那个**，不是厂商名。下面 28 个厂商属于这一类。 +点开厂商卡片，打开的仍是所借用集成类型的创建页，右侧文档面板改为显示该厂商自己的文档；**最终保存的集成类型是借用的那个**，不是厂商名。下面 29 个厂商属于这一类。 | 厂商卡片 | 借用集成类型 | | :--- | :--- | @@ -114,6 +114,7 @@ Flashduty On-call 提供两种告警接入方式： | [Chronosphere](/zh/on-call/integration/alert-integration/alert-sources/chronosphere) | Prometheus | | [CubeAPM](/zh/on-call/integration/alert-integration/alert-sources/cubeapm) | Prometheus | | [Red Hat OpenShift](/zh/on-call/integration/alert-integration/alert-sources/red-hat-openshift) | Prometheus | +| [Kapacitor](/zh/on-call/integration/alert-integration/alert-sources/kapacitor) | InfluxData | ## 集成功能