Skip to content

Commit 19d65c7

Browse files
committed
fix: hide pull integration setup steps
1 parent 73f62f0 commit 19d65c7

4 files changed

Lines changed: 16 additions & 0 deletions

File tree

en/on-call/integration/alert-integration/alert-sources/db-pull.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ By configuring a database connection and SQL query, Flashduty periodically conne
1010
DB Pull is the right choice when **alert data is stored in a relational database**, **the monitoring system cannot send webhooks**, or when you **need to extract abnormal records directly from business tables as alerts**. If your system already supports webhook delivery, prefer the corresponding push-based integration. It has lower latency and a smaller resource footprint.
1111
</Tip>
1212

13+
<div className="hide">
14+
1315
## Setup steps
1416
---
1517

@@ -35,6 +37,8 @@ When you need to route alerts to different channels based on the alert event pay
3537
</Accordion>
3638
</AccordionGroup>
3739

40+
</div>
41+
3842
## Configuration
3943
---
4044

en/on-call/integration/alert-integration/alert-sources/http-pull.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ By configuring an HTTP endpoint, Flashduty issues a request on the schedule you
1010
HTTP Pull is the right choice when your source **cannot send webhooks**, **is query-only by nature**, or when you **do not want to modify the upstream system**. If your system already supports webhook delivery, prefer the corresponding push-based integration (Prometheus, Zabbix, etc.) — it has lower latency and a smaller resource footprint.
1111
:::
1212

13+
<div className="hide">
14+
1315
## Setup Steps
1416
---
1517

@@ -37,6 +39,8 @@ When you need to route alert events to different channels based on the alert pay
3739
4. Fill in the form as described in the "Configuration" section below and click **Save**.
3840
</details>
3941

42+
</div>
43+
4044
## Configuration
4145
---
4246

zh/on-call/integration/alert-integration/alert-sources/db-pull.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ keywords: ["告警集成", "DB Pull", "数据库拉取", "MySQL", "PostgreSQL",
1010
DB Pull 适合 **告警数据存储在关系型数据库中****监控系统无法推送 webhook**,或 **需要直接从业务表中抽取异常数据作为告警** 的场景。如果您的系统已经支持 webhook 推送,优先使用对应的推送式集成,延迟更低、资源开销更小。
1111
</Tip>
1212

13+
<div className="hide">
14+
1315
## 操作步骤
1416
---
1517

@@ -35,6 +37,8 @@ DB Pull 适合 **告警数据存储在关系型数据库中**、**监控系统
3537
</Accordion>
3638
</AccordionGroup>
3739

40+
</div>
41+
3842
## 配置项
3943
---
4044

zh/on-call/integration/alert-integration/alert-sources/http-pull.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ keywords: ["告警集成", "HTTP Pull", "拉取", "轮询", "Polling", "数据
1010
HTTP 拉取适合 **无法主动 webhook****接口本身就是查询型****不希望对告警源做改造** 的场景。如果您的系统已经支持 webhook 推送,优先使用对应的推送式集成(Prometheus、Zabbix 等),延迟更低、资源开销更小。
1111
</Tip>
1212

13+
<div className="hide">
14+
1315
## 操作步骤
1416
---
1517

@@ -35,6 +37,8 @@ HTTP 拉取适合 **无法主动 webhook**、**接口本身就是查询型** 或
3537
</Accordion>
3638
</AccordionGroup>
3739

40+
</div>
41+
3842
## 配置项
3943
---
4044

0 commit comments

Comments
 (0)