From 86f55abea4dfc95c3100b7e221afe2b49c86071e Mon Sep 17 00:00:00 2001 From: Flashduty AI-SRE Date: Mon, 5 Oct 2026 08:12:07 +0000 Subject: [PATCH 1/2] =?UTF-8?q?docs:=20doc-review=202026-10-05=20(diff)=20?= =?UTF-8?q?=E2=80=94=20integration-center=20catalog=20and=20request=20flow?= =?UTF-8?q?,=20AI=20SRE=20session=20header=20binding=20and=20subagent=20ro?= =?UTF-8?q?w,=20stale=20automation=20template=20name?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- en/ai-sre/automations.mdx | 4 +-- en/ai-sre/quickstart.mdx | 2 +- en/ai-sre/sessions.mdx | 4 +-- en/on-call/channel/integrate-data.mdx | 38 +++++++++++++++++++++++++++ zh/ai-sre/automations.mdx | 4 +-- zh/ai-sre/quickstart.mdx | 2 +- zh/ai-sre/sessions.mdx | 4 +-- zh/on-call/channel/integrate-data.mdx | 38 +++++++++++++++++++++++++++ 8 files changed, 86 insertions(+), 10 deletions(-) diff --git a/en/ai-sre/automations.mdx b/en/ai-sre/automations.mdx index ca06040f5..6812cad2a 100644 --- a/en/ai-sre/automations.mdx +++ b/en/ai-sre/automations.mdx @@ -40,7 +40,7 @@ The page header offers two creation entry points: an outline-style **Create via Choose **Start from scratch** to open a blank form and manually fill in the name, task prompt, and triggers. This suits cases where you already know what you want the agent to do and want a fully custom prompt. - Below, a set of **preset template** cards is listed (delivered by the backend per UI language: `zh-CN` for Chinese, `en-US` for English). Common ones include **Weekly Insights**, **Alert Governance**, **On-call Incident Analysis**, and **On-call Load Analysis**. Click any template card to prefill the form with the template's name and task prompt; tweak from there. + Below, a set of **preset template** cards is listed (delivered by the backend per UI language: `zh-CN` for Chinese, `en-US` for English). Common ones include **Weekly On-call Review**, **Alert Governance**, **On-call Incident Analysis**, and **On-call Load Analysis**. Click any template card to prefill the form with the template's name and task prompt; tweak from there. @@ -54,7 +54,7 @@ The configuration form has the following fields: | Field | Required | Notes | |---|---|---| -| Name | Yes | The rule name, up to 255 characters. Placeholder example: `Weekly on-call insight`. | +| Name | Yes | The rule name, up to 255 characters. Placeholder example: `Weekly On-call Review`. | | Scope | Yes | Use the **scope selector** to choose **Personal** (`team_id=0`) or a **Team** (`team_id>0`). Scope determines both the rule's ownership and edit permissions, and constrains the self-hosted Runners selectable in **Environment** — only account-global Runners and Runners belonging to the same team as the scope are selectable. | | Environment | No | Use the **environment picker** to choose the runtime environment: **Auto** (the backend picks the best available environment, the default), **Cloud Sandbox**, or a **self-hosted (BYOC) Runner**. After picking a team scope, a team Runner that does not belong to that scope is cleared automatically. | | Task prompt | Yes | Describe the task for AI SRE to perform, written in a rich-text editor. This prompt is exactly what is sent to the agent on each run. Placeholder: `Describe the task for Flashduty AI SRE to perform.` | diff --git a/en/ai-sre/quickstart.mdx b/en/ai-sre/quickstart.mdx index 78d46a961..e190d7b16 100644 --- a/en/ai-sre/quickstart.mdx +++ b/en/ai-sre/quickstart.mdx @@ -34,7 +34,7 @@ For actively investigating an issue, digging deeper, or building up knowledge. G ### Automations -For work that shouldn't need a human watching it — scheduled inspections, weekly insight reports, alert-noise cleanup. Go to **AI SRE → Automations** and create one from a built-in template (On-call Incident Analysis, Alert Governance, Weekly Insights, and more) or build one from scratch. Each run happens in a hidden session in the background, and the result lands in the run history where you can open the full trail any time. → See [Automations](/en/ai-sre/automations) +For work that shouldn't need a human watching it — scheduled inspections, weekly insight reports, alert-noise cleanup. Go to **AI SRE → Automations** and create one from a built-in template (On-call Incident Analysis, Alert Governance, Weekly On-call Review, and more) or build one from scratch. Each run happens in a hidden session in the background, and the result lands in the run history where you can open the full trail any time. → See [Automations](/en/ai-sre/automations) ### IM (@ Mentions + Automatic War Room Diagnosis) diff --git a/en/ai-sre/sessions.mdx b/en/ai-sre/sessions.mdx index 3b67ed6d7..90f6e5038 100644 --- a/en/ai-sre/sessions.mdx +++ b/en/ai-sre/sessions.mdx @@ -257,7 +257,7 @@ Channel differences: only the console (`web`) renders this card. IM and API chan ### Subagents -When the agent delegates a subtask, a clickable **dispatch reference line** appears in the conversation: a status ring, a type badge (Agent / A2A), the subtask's name and current intent, and right-aligned status and elapsed time; once finished it adds the tool-call count / token usage / total duration, and on failure a red reason line appears underneath. The reference line is a compact single row and carries **no stop button** — stopping lives in the task panel's detail header (see "Task Panel and Background Tasks" below). Clicking the line opens a subagent session panel on the right, side by side with the main conversation — the main chat area shrinks accordingly rather than being covered by a modal. The panel can be expanded to fill the main area, or collapsed back to the side-by-side layout. +When the agent delegates a subtask, a clickable **dispatch reference line** appears in the conversation: a status icon, the subtask's name (only when it has a custom one) and its current intent, with the elapsed time in parentheses after the intent and the running state at the end of the row (a completed row shows no status word; an A2A subagent carries an extra **A2A** badge before its name), and right-aligned tool-call count and token usage; on failure a red reason line appears underneath. The reference line is a compact single row and carries **no stop button** — stopping lives in the task panel's detail header (see "Task Panel and Background Tasks" below). Clicking the line opens a subagent session panel on the right, side by side with the main conversation — the main chat area shrinks accordingly rather than being covered by a modal. The panel can be expanded to fill the main area, or collapsed back to the side-by-side layout. Besides running, completed, failed, and interrupted, a subtask can also sit in one of two "needs you" states: @@ -463,7 +463,7 @@ When creating a session, the input area has a separate **environment** selector Self-hosted runners are shown by their current status: runners that are offline or have never connected appear dimmed in the list and cannot be selected; if a selected runner goes offline afterward, sending messages is also blocked with a corresponding notice. -The environment choice is fixed once the first message is sent and the session is created. To switch afterward, see the in-place switching capability for IM sessions under "Session entry kind" below, or fork a new session. +The environment choice is fixed once the first message is sent and the session is created. Once the session starts, the runtime environment and the bound team move out of the input area to the **chat header**, shown read-only on the same row as the context badge; the input area no longer shows either selector. To switch afterward, see the in-place switching capability for IM sessions under "Session entry kind" below, or fork a new session. ## Binding a Team diff --git a/en/on-call/channel/integrate-data.mdx b/en/on-call/channel/integrate-data.mdx index 463bfcb2b..006c92aeb 100644 --- a/en/on-call/channel/integrate-data.mdx +++ b/en/on-call/channel/integrate-data.mdx @@ -73,6 +73,44 @@ Shared integrations must have at least one routing rule configured, otherwise al Shared Integration +## Browsing and Finding Integrations + +The Integration Center groups the alert sources and change events it covers by category, so you can narrow the list with a category chip or search for the system you need. + +The add-integration panel has one set of chips per tab, and each tab opens on its own default category: + +| Tab | Category chips (in display order) | Default category | +| :--- | :--- | :--- | +| Alert Events | Generic, Popular, Cloud providers, Metrics & infrastructure, APM & observability, Event correlation & AIOps, Logs & error tracking, Security, Uptime & status pages, Jobs, delivery & app platforms, Network & hardware | **Popular** | +| Change Events | Generic, CI/CD & deploy, Source control, Config & feature flags, Infrastructure & platforms | **CI/CD & deploy** | + +- Integrations with no registered category are collected under **Uncategorized**; a category with no entries is not shown. +- When the chips do not fit, the panel keeps only **All**, **Generic**, the tab's default category, and the currently selected category; the rest collapse into **More N**, which expands on click. +- The search box matches across all categories (ignoring the selected chip) by integration name or type, and shows the hits as **Search results**; clearing the search returns you to the category you had selected. + +### All integrations catalog + +Clicking the **All** chip opens a full-screen catalog: + +- The number next to the title is how many integrations the catalog covers, and the search box at the top searches all of them. +- The category rail on the left lists every category with its entry count; clicking one scrolls the right side to that category (and clears the search). +- The right side lays out cards by category (logo, name, and a two-line blurb); hovering a card reveals **Add**, which opens the new-integration page for that system. + +At the bottom the catalog keeps a "Can't find your system?" fallback area with two ways out: connect it with a generic integration, or request an integration. + +### Requesting an Integration + +If the system you need is not covered yet, click **Submit a request** in the fallback area to tell us what to support. This entry point is available on Flashduty SaaS only; private deployments do not show it. + +| Field | Required | Limit | Notes | +| :--- | :--- | :--- | :--- | +| System name | Yes | Up to 100 characters | For example `Checkmk`; a term you searched for in the catalog is prefilled here | +| Website or docs link | No | Up to 500 characters | Must start with `http://` or `https://` | +| Notes | No | Up to 2000 characters | Which alerts you want to receive, and how you handle them today | +| Work email | See notes | Up to 200 characters | Not needed when your account already has an email — we reply to that address; required otherwise | + +After you submit, the dialog confirms that the request was received and explains that we will reply by email after review; until the request is supported, you can connect the system with a generic integration. + ## Integration Features Optional configurations for both integration methods, configurable on the integration details page: diff --git a/zh/ai-sre/automations.mdx b/zh/ai-sre/automations.mdx index dc5fa288b..5121da746 100644 --- a/zh/ai-sre/automations.mdx +++ b/zh/ai-sre/automations.mdx @@ -40,7 +40,7 @@ sidebarTitle: 自动化 选择 **从零开始**，进入空白表单，手动填写名称、任务提示词与触发方式。适合你已经清楚要让 Agent 做什么、想完全自定义提示词的场景。 - 下方列出一组 **预设模板** 卡片（由后端按界面语言下发，中文环境取 `zh-CN`、英文环境取 `en-US`），常见的有 **每周洞察**、**告警治理**、**故障自动分析**、**On-call 负载分析** 等。点击任一模板卡片，会用模板预置的名称与任务提示词预填表单，你在此基础上微调即可。 + 下方列出一组 **预设模板** 卡片（由后端按界面语言下发，中文环境取 `zh-CN`、英文环境取 `en-US`），常见的有 **值班周报**、**告警治理**、**故障自动分析**、**On-call 负载分析** 等。点击任一模板卡片，会用模板预置的名称与任务提示词预填表单，你在此基础上微调即可。 @@ -54,7 +54,7 @@ sidebarTitle: 自动化 | 字段 | 必填 | 说明 | |---|---|---| -| 名称 | 是 | 规则名称，最长 255 字符。占位示例：`每周洞察`。 | +| 名称 | 是 | 规则名称，最长 255 字符。占位示例：`值班周报`。 | | 范围 | 是 | 通过 **范围选择器** 选 **个人**（`team_id=0`）或某个 **团队**（`team_id>0`）。范围既决定这条规则的归属与编辑权限，也限定 **执行 Environment** 里可选的自托管 Runner——只有账户全局的 Runner，以及与该范围同团队的 Runner 才可选。 | | 执行 Environment | 否 | 通过 **环境选择器** 选运行环境：**自动**（由后端挑选最优可用环境，默认值）、**云端沙箱**，或某个 **自托管（BYOC）Runner**。选了某个团队范围后，不属于该范围的团队 Runner 会被自动清除。 | | 任务提示词 | 是 | 描述要让 AI SRE 执行的任务，用富文本编辑器撰写。这段提示词就是每次运行时发给 Agent 的内容。占位提示：`描述 Flashduty AI SRE 要执行的任务。` | diff --git a/zh/ai-sre/quickstart.mdx b/zh/ai-sre/quickstart.mdx index 2d1e310b5..03be7e59d 100644 --- a/zh/ai-sre/quickstart.mdx +++ b/zh/ai-sre/quickstart.mdx @@ -34,7 +34,7 @@ AI SRE 没有唯一入口，从你现在所在的场景开始就好： ### 自动化（Automations） -适合不需要人守着的周期性 / 触发式任务——定时巡检、周报洞察、告警治理。进入 **AI SRE → 自动化**，可从内置模板一键创建（如故障自动分析、告警治理、每周洞察），也可以从零开始自定义任务提示词。它在后台跑一个隐藏会话，结果记录进运行历史，随时可以打开查看完整的调查过程。→ 详见[自动化](/zh/ai-sre/automations) +适合不需要人守着的周期性 / 触发式任务——定时巡检、周报洞察、告警治理。进入 **AI SRE → 自动化**，可从内置模板一键创建（如故障自动分析、告警治理、值班周报），也可以从零开始自定义任务提示词。它在后台跑一个隐藏会话，结果记录进运行历史，随时可以打开查看完整的调查过程。→ 详见[自动化](/zh/ai-sre/automations) ### IM（@ 召唤 + 作战室自动诊断） diff --git a/zh/ai-sre/sessions.mdx b/zh/ai-sre/sessions.mdx index c0e20178c..05ec70565 100644 --- a/zh/ai-sre/sessions.mdx +++ b/zh/ai-sre/sessions.mdx @@ -257,7 +257,7 @@ OAuth 授权链接有过期时间；过期后卡片会提示「授权链接已 ### 子任务（Subagent） -Agent 委派子任务时，对话中会出现一行可点击的**派发引用**：状态环 + 类型徽标（Agent / A2A）+ 子任务名称与当前意图，右侧对齐显示状态与耗时；结束后补上工具调用数 / Token 用量 / 总耗时，失败时在下方附一行红色的失败原因。引用行是紧凑的一行，**不带停止按钮**——停止操作统一放在任务面板的详情头部（见下文「任务面板与后台任务」）。点击引用行会在右侧打开一个与主对话并排的子会话面板——主对话区域随之收窄，而不是被弹窗遮挡；面板可展开为占满主区域的全屏视图，也可以收起回并排布局。 +Agent 委派子任务时，对话中会出现一行可点击的**派发引用**：状态图标 + 子任务名称（仅当它有自定义名称时）与当前意图，意图后括号内是耗时，行尾标出运行状态（已完成的行不显示状态词；A2A 子代理在名称前额外带一枚 **A2A** 徽标），右侧对齐显示工具调用数 / Token 用量；失败时在下方附一行红色的失败原因。引用行是紧凑的一行，**不带停止按钮**——停止操作统一放在任务面板的详情头部（见下文「任务面板与后台任务」）。点击引用行会在右侧打开一个与主对话并排的子会话面板——主对话区域随之收窄，而不是被弹窗遮挡；面板可展开为占满主区域的全屏视图，也可以收起回并排布局。 除进行中、完成、失败、已中断外，子任务还可能处于两种「需要你」的状态： @@ -463,7 +463,7 @@ Fork 会话会清理只属于运行中的临时状态，例如当前回合缓存 自托管 Runner 会按当前状态展示：离线或从未连接过的 Runner 在列表中会置灰，无法选中；若已选中的 Runner 之后离线，也会阻止发送消息并给出提示。 -环境选择在发送第一条消息、创建会话时即固定；如需切换，可参考下文「会话入口类型」中 IM 会话的就地切换能力，或 Fork 出一个新会话。 +环境选择在发送第一条消息、创建会话时即固定。会话开始后，运行环境与绑定的团队会从输入区移到**聊天页头部**，以只读形式与 Context 徽标显示在同一行；输入区不再显示这两个选择器。如需切换，可参考下文「会话入口类型」中 IM 会话的就地切换能力，或 Fork 出一个新会话。 ## 绑定团队 diff --git a/zh/on-call/channel/integrate-data.mdx b/zh/on-call/channel/integrate-data.mdx index fabaa3180..8eda83d21 100644 --- a/zh/on-call/channel/integrate-data.mdx +++ b/zh/on-call/channel/integrate-data.mdx @@ -74,6 +74,44 @@ Flashduty On-call 提供两种告警接入方式： 共享集成 +## 浏览与查找集成 + +集成中心把收录的告警源与变更事件按分类组织，您可以用分类胶囊缩小范围，也可以直接搜索目标系统。 + +添加集成面板的胶囊按页签分成两套，打开时默认落在各页签的默认分类： + +| 页签 | 分类胶囊（按显示顺序） | 默认分类 | +| :--- | :--- | :--- | +| 告警事件 | 通用接入、热门、云厂商、指标与基础设施监控、APM 与可观测平台、事件关联与 AIOps、日志与错误追踪、安全、拨测与状态页、任务、交付与应用平台、网络与硬件 | **热门** | +| 变更事件 | 通用接入、CI/CD 与部署、代码仓库、配置与功能开关、基础设施与平台 | **CI/CD 与部署** | + +- 未登记分类的集成统一归入 **未分类**；本身没有条目的分类不会显示。 +- 胶囊排不下时，面板只保留 **全部**、**通用接入**、当前页签的默认分类与当前选中的分类，其余收进 **更多 N**，点击后展开。 +- 搜索框跨全部分类匹配（忽略当前选中的胶囊），按集成名称或集成类型查找，结果以 **搜索结果** 呈现；清空搜索后回到原来选中的分类。 + +### 全部集成目录 + +点击 **全部** 胶囊会打开一个全屏集成目录： + +- 标题右侧是该目录收录的集成总数，顶部搜索框跨全部集成查找。 +- 左侧分类导航列出每个分类及其条目数，点击即在右侧滚动定位到该分类（同时清空搜索）。 +- 右侧按分类平铺卡片（图标、名称、两行简介），鼠标悬停出现 **添加**，点击进入该系统的新建集成页。 + +目录底部还有一块「没有找到你要接的系统？」的兜底区，给出两条出路：用通用集成接入，或提交集成需求。 + +### 提交集成需求 + +要接入的系统如果还没收录，可以在兜底区点击 **提交需求** 告诉我们需要支持什么。该入口只在 Flashduty SaaS 环境提供，私有化部署不显示。 + +| 字段 | 必填 | 限制 | 说明 | +| :--- | :--- | :--- | :--- | +| 系统名称 | 是 | 最长 100 个字符 | 例如 `Checkmk`；从目录搜索进来的词会带入此栏 | +| 官网或文档链接 | 否 | 最长 500 个字符 | 需以 `http://` 或 `https://` 开头 | +| 补充说明 | 否 | 最长 2000 个字符 | 希望接入哪些告警、目前怎么处理这些告警 | +| 工作邮箱 | 见说明 | 最长 200 个字符 | 账号已绑定邮箱时无需填写，直接用账号邮箱联系您；未绑定时必填 | + +提交后弹窗给出「已收到「系统名称」的集成需求」的回执，并说明我们评估后会通过邮箱联系您；在需求被支持之前，可以先用通用集成接入。 + ## 集成功能 两种集成方式的可选配置，可在集成详情页中配置： From 948a850a5a972530261c919e5887cc3589293744 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Mon, 5 Oct 2026 20:11:23 -0700 Subject: [PATCH 2/2] docs(integrations): keep the borrowed-integration vendor section alongside the new browsing catalog --- en/on-call/channel/integrate-data.mdx | 48 +++++++++++++++++++++++++++ zh/on-call/channel/integrate-data.mdx | 48 +++++++++++++++++++++++++++ 2 files changed, 96 insertions(+) diff --git a/en/on-call/channel/integrate-data.mdx b/en/on-call/channel/integrate-data.mdx index 67bf2d55f..1b46e148a 100644 --- a/en/on-call/channel/integrate-data.mdx +++ b/en/on-call/channel/integrate-data.mdx @@ -125,6 +125,54 @@ Optional configurations for both integration methods, configurable on the integr | Alert Processing | Configure Pipeline to filter, modify, or drop alerts | ✓ | ✓ | | Routing Rules | Distribute alerts to different channels based on conditions | ✗ | ✓ (Required) | +### 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 29 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 | +| [Kapacitor](/en/on-call/integration/alert-integration/alert-sources/kapacitor) | InfluxData | + +## Integration Features + +Optional configurations for both integration methods, configurable on the integration details page: + +| Feature | Description | Dedicated Integration | Shared Integration | +| :--- | :--- | :---: | :---: | +| Label Enhancement | Dynamically generate new labels through regex extraction, mapping tables, etc. | ✓ | ✓ | +| Alert Processing | Configure Pipeline to filter, modify, or drop alerts | ✓ | ✓ | +| Routing Rules | Distribute alerts to different channels based on conditions | ✗ | ✓ (Required) | + ### Label Enhancement After alerts enter the system, automatically add or modify labels for subsequent routing, searching, and analysis. Multiple enhancement methods supported: diff --git a/zh/on-call/channel/integrate-data.mdx b/zh/on-call/channel/integrate-data.mdx index 4742822d2..c60b8fd6e 100644 --- a/zh/on-call/channel/integrate-data.mdx +++ b/zh/on-call/channel/integrate-data.mdx @@ -126,6 +126,54 @@ Flashduty On-call 提供两种告警接入方式： | 告警处理 | 配置 Pipeline 对告警进行过滤、修改、丢弃等处理 | ✓ | ✓ | | 路由规则 | 按条件将告警分发到不同的协作空间 | ✗ | ✓（必填） | +### 借用其它集成接入的厂商 + +有些厂商没有自己的集成类型，而是借用兼容的集成类型接入。它们的卡片与集成类型卡片一起出现在上面的选择列表里，也一起参与搜索：除了厂商名，还可以按常见别名找到，例如 `VSPC`、`PDU`、`WUG`、`UPS`、`OCP`、`Azure Sentinel`、`Bro` 等。 + +点开厂商卡片，打开的仍是所借用集成类型的创建页，右侧文档面板改为显示该厂商自己的文档；**最终保存的集成类型是借用的那个**，不是厂商名。下面 29 个厂商属于这一类。 + +| 厂商卡片 | 借用集成类型 | +| :--- | :--- | +| [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 | +| [Kapacitor](/zh/on-call/integration/alert-integration/alert-sources/kapacitor) | InfluxData | + +## 集成功能 + +两种集成方式的可选配置，可在集成详情页中配置： + +| 功能 | 说明 | 专属集成 | 共享集成 | +| :--- | :--- | :---: | :---: | +| 标签增强 | 通过正则提取、映射表等方式动态生成新标签 | ✓ | ✓ | +| 告警处理 | 配置 Pipeline 对告警进行过滤、修改、丢弃等处理 | ✓ | ✓ | +| 路由规则 | 按条件将告警分发到不同的协作空间 | ✗ | ✓（必填） | + ### 标签增强 在告警进入系统后，自动为其添加或修改标签，便于后续的路由、检索和分析。支持多种增强方式：