diff --git a/docs/enterprise/trigger.md b/docs/enterprise/trigger.md
index 44c23a4f7..7ab392198 100644
--- a/docs/enterprise/trigger.md
+++ b/docs/enterprise/trigger.md
@@ -9,146 +9,267 @@ Trigger allows you to define evaluation rules with SQL.
 GreptimeDB evaluates these rules periodically; once the condition is met, a
 notification is sent out.
 
-The following content is a quick start example that sets up a Trigger to monitor system load and raise alerts step by step.
-For details on how to write a Trigger,
-please refer to the [Syntax](/reference/sql/trigger-syntax.md) documentation.
+## Key Features
+
+- **SQL-native**: Define trigger rules in SQL, reusing GreptimeDB's built-in
+    functions without a learning curve
+- **Multi-stage state management**: Built-in pending / firing / inactive state
+    machine prevents flapping and duplicate notifications
+- **Rich context**: Custom labels and annotations with automatic injection of
+    query result fields to pinpoint root causes
+- **Ecosystem-friendly**: Alert payload fully compatible with Prometheus 
+    Alertmanager—use its grouping, inhibition, silencing, and routing without
+    adapters
 
 ## Quick Start Example
 
-This section walks through an end-to-end example that uses Trigger to monitor
-system load and raise an alert.
+This section walks through an end-to-end alerting scenario: monitor system load
+(`load1`) and fire alerts when load exceeds a threshold.
 
-The diagram illustrates the complete end-to-end workflow of the example.
+In this quick start, you will:
 
-![Trigger demo architecture](/trigger-demo-architecture.png)
+- Create a `load1` table to store host load metrics
+- Define a Trigger with conditions, labels, annotations, and notifications
+- Simulate data ingestion with normal and abnormal values
+- Watch alerts transition through pending → firing → inactive
 
-1. Vector continuously scrapes host metrics and writes them to GreptimeDB.
-2. A Trigger in GreptimeDB evaluates a rule every minute; whenever the condition
-    is met, it sends a notification to Alertmanager.
-3. Alertmanager applies its own policies and finally delivers the alert to Slack.
+### 1. Create the Data Table
 
-### Use Vector to Scrape Host Metrics
+Connect to GreptimeDB with a MySQL client and create the `load1` table:
 
-Use Vector to scrape host metrics and write it to GreptimeDB. Below is a Vector
-configuration example:
+```sql
+CREATE TABLE `load1` (
+    host            STRING,
+    load1           FLOAT32,
+    ts              TIMESTAMP TIME INDEX
+) WITH ('append_mode'='true');
+```
+
+### 2. Create Trigger
+
+Connect to GreptimeDB with MySQL client and create the `load1_monitor` trigger:
+
+```sql
+CREATE TRIGGER IF NOT EXISTS `load1_monitor`
+    ON (
+        SELECT
+            host          AS label_host,
+            avg(load1)    AS avg_load1,
+            max(ts)       AS ts
+        FROM public.load1
+        WHERE ts >= NOW() - '1 minutes'::INTERVAL
+        GROUP BY host
+        HAVING avg(load1) > 10
+    ) EVERY '1 minutes'::INTERVAL
+    FOR '3 minutes'::INTERVAL
+    KEEP FIRING FOR '3 minutes'::INTERVAL
+    LABELS (severity=warning)
+    ANNOTATIONS (comment='Your computer is smoking, should take a break.')
+    NOTIFY(
+        WEBHOOK alert_manager URL 'http://localhost:9093' WITH (timeout='1m')
+    );
+```
+
+This Trigger runs every minute, computes average load per host over the last
+60 seconds, and produces an alert instance for each host where `avg(load1) > 10`.
+
+Key parameters:
+
+- **FOR**: Specifies how long the condition must continuously hold before an
+    alert instance enters firing state.
+- **KEEP FIRING FOR**: Specifies how long an alert instance stays in the firing
+    state after the condition no longer holds.
+
+See the [trigger syntax](/reference/sql/trigger-syntax.md) for more detail.
+
+### 3. Check Trigger Status
+
+#### List all Triggers
+
+```sql
+SHOW TRIGGERS;
+```
 
-```toml
-[sources.in]
-type = "host_metrics"
-scrape_interval_secs = 15
+Output:
 
-[sinks.out]
-inputs = ["in"]
-type = "greptimedb"
-endpoint = "localhost:4001"
+```text
++---------------+
+| Triggers      |
++---------------+
+| load1_monitor |
++---------------+
 ```
 
-GreptimeDB auto-creates tables on the first write. The `host_load1` table stores
-the system load averaged over the last minute. It is a key performance indicator
-for measuring system activity. We can create a monitoring rule to track values
-in this table. The schema of this table is shown below:
+#### View the creation statement
 
 ```sql
-+-----------+----------------------+------+------+---------+---------------+
-| Column    | Type                 | Key  | Null | Default | Semantic Type |
-+-----------+----------------------+------+------+---------+---------------+
-| ts        | TimestampMillisecond | PRI  | NO   |         | TIMESTAMP     |
-| collector | String               | PRI  | YES  |         | TAG           |
-| host      | String               | PRI  | YES  |         | TAG           |
-| val       | Float64              |      | YES  |         | FIELD         |
-+-----------+----------------------+------+------+---------+---------------+
+SHOW CREATE TRIGGER `load1_monitor`\G
 ```
 
-### Set up Alertmanager with a Slack Receiver
+Output:
 
-The payload of GreptimeDB Trigger's Webhook is compatible with [Prometheus
-Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), so we
-can reuse Alertmanager’s grouping, inhibition, silencing and routing features
-without any extra glue code.
+```text
+*************************** 1. row ***************************
+       Trigger: load1_monitor
+Create Trigger: CREATE TRIGGER IF NOT EXISTS `load1_monitor`
+  ON (SELECT host AS label_host, avg(load1) AS avg_load1 ...) EVERY '1 minutes'::INTERVAL
+  FOR '3 minutes'::INTERVAL
+  KEEP FIRING FOR '3 minutes'::INTERVAL
+  LABELS (severity = 'warning')
+  ANNOTATIONS (comment = 'Your computer is smoking, should take a break.')
+  NOTIFY(
+    WEBHOOK `alert_manager` URL `http://localhost:9093` WITH (timeout = '1m'),
+  )
+```
 
-You can refer to the [official documentation](https://prometheus.io/docs/alerting/latest/configuration/)
-to configure Prometheus Alertmanager. Below is a minimal message template you
-can use:
+#### View Trigger details
+
+```sql
+SELECT * FROM information_schema.triggers\G
+```
+
+Output:
 
 ```text
-{{ define "slack.text" }}
-{{ range .Alerts }}
+*************************** 1. row ***************************
+   trigger_name: load1_monitor
+     trigger_id: 1024
+        raw_sql: (SELECT host AS label_host, avg(load1) AS avg_load1, ...)
+       interval: 60
+         labels: {"severity":"warning"}
+    annotations: {"comment":"Your computer is smoking, should take a break."}
+            for: 180
+keep_firing_for: 180
+       channels: [{"channel_type":{"Webhook":{"opts":{"timeout":"1m"}, ...}]
+    flownode_id: 0
+```
 
-Labels:
-{{- range .Labels.SortedPairs }}
-- {{ .Name }}: {{ .Value }}
-{{ end }}
+See the [Triggers](/reference/sql/information-schema/triggers) for more details.
 
-Annotations:
-{{- range .Annotations.SortedPairs }}
-- {{ .Name }}: {{ .Value }}
-{{ end }}
+#### View alert instances
 
-{{ end }}
-{{ end }}
+```sql
+SELECT * FROM information_schema.alerts;
 ```
 
-Generating a Slack message using the above template will iterate over all alerts
-and display the labels and annotations for each alert.
+With no data written yet, this returns an empty set.
+
+See the [Alerts](/reference/sql/information-schema/alerts) for more details.
 
-Start Alertmanager once the configuration is ready.
+### 4. Write Data and Observe Alert States
 
-### Create Trigger
+This script simulates data ingestion: normal values for the first minute, high
+values for 6 minutes to trigger alerts, then back to normal.
+
+```bash
+#!/usr/bin/env bash
 
-Connect to GreptimeDB with MySQL client and run the following SQL:
+MYSQL="mysql -h 127.0.0.1 -P 4002"
+
+insert_normal() {
+  $MYSQL -e "INSERT INTO load1 (host, load1, ts) VALUES
+    ('newyork1', 1.2, now()),
+    ('newyork2', 1.1, now()),
+    ('newyork3', 1.3, now());"
+}
+
+insert_high() {
+  $MYSQL -e "INSERT INTO load1 (host, load1, ts) VALUES
+    ('newyork1', 1.2, now()),
+    ('newyork2', 12.1, now()),
+    ('newyork3', 11.5, now());"
+}
+
+# First minute: normal data
+for i in {1..4}; do insert_normal; sleep 15; done
+
+# Next 6 minutes: high values
+for i in {1..24}; do insert_high; sleep 15; done
+
+# After: back to normal
+while true; do insert_normal; sleep 15; done
+```
+
+#### State Transitions
+
+In another terminal, query alert status:
+
+**Phase 1: No alerts**
 
 ```sql
-CREATE TRIGGER IF NOT EXISTS load1_monitor
-        ON (
-                SELECT collector AS label_collector,
-                host as label_host, 
-                val
-                FROM host_load1 WHERE val > 10 and ts >= now() - '1 minutes'::INTERVAL
-        ) EVERY '1 minute'::INTERVAL
-        LABELS (severity=warning)
-        ANNOTATIONS (comment='Your computer is smoking, should take a break.')
-        NOTIFY(
-                WEBHOOK alert_manager URL 'http://localhost:9093' WITH (timeout="1m")
-        );
-```
-
-The above SQL will create a trigger named `load1_monitor` that runs every minute.
-It evaluates the last 60 seconds of data in `host_load1`; if any load1 value
-exceeds 10, the `WEBHOOK` option in the `NOTIFY` syntax specifies that this
-trigger will send a notification to Alertmanager which running on localhost with
-port 9093.
-
-You can execute `SHOW TRIGGERS` to view the list of created Triggers.
+SELECT * FROM information_schema.alerts\G
+```
+
+Output:
+
+```
+Empty set
+```
+
+**Phase 2: pending** (condition met, `FOR` duration not reached)
 
 ```sql
-SHOW TRIGGERS;
+SELECT trigger_id, labels, active_at, fired_at, resolved_at FROM information_schema.alerts;
 ```
 
-The output should look like this:
+```text
++------------+-----------------------------------------------------------------------+----------------------------+----------+-------------+
+| trigger_id | labels                                                                | active_at                  | fired_at | resolved_at |
++------------+-----------------------------------------------------------------------+----------------------------+----------+-------------+
+|       1024 | {"alert_name":"load1_monitor","host":"newyork3","severity":"warning"} | 2025-12-29 11:58:20.992670 | NULL     | NULL        |
+|       1024 | {"alert_name":"load1_monitor","host":"newyork2","severity":"warning"} | 2025-12-29 11:58:20.992670 | NULL     | NULL        |
++------------+-----------------------------------------------------------------------+----------------------------+----------+-------------+
+```
+
+**Phase 3: firing** (`FOR` satisfied, notifications sent)
+
+```sql
+SELECT trigger_id, labels, active_at, fired_at, resolved_at FROM information_schema.alerts;
+```
 
 ```text
-+---------------+
-| Triggers      |
-+---------------+
-| load1_monitor |
-+---------------+
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+-------------+
+| trigger_id | labels                                                                | active_at                  | fired_at                   | resolved_at |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+-------------+
+|       1024 | {"alert_name":"load1_monitor","host":"newyork3","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | NULL        |
+|       1024 | {"alert_name":"load1_monitor","host":"newyork2","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | NULL        |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+-------------+
 ```
 
-### Test Trigger
+**Phase 4: inactive** (condition cleared + `KEEP FIRING FOR` expired)
 
-Use [stress-ng](https://github.com/ColinIanKing/stress-ng) to simulate high CPU
-load for 60s:
+```sql
+SELECT trigger_id, labels, active_at, fired_at, resolved_at FROM information_schema.alerts;
+```
 
-```bash
-stress-ng --cpu 100 --cpu-load 10 --timeout 60
+```text
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+----------------------------+
+| trigger_id | labels                                                                | active_at                  | fired_at                   | resolved_at                |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+----------------------------+
+|       1024 | {"alert_name":"load1_monitor","host":"newyork3","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | 2025-12-29 12:05:20.991750 |
+|       1024 | {"alert_name":"load1_monitor","host":"newyork2","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | 2025-12-29 12:05:20.991750 |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+----------------------------+
 ```
 
-The load1 will rise quickly, the Trigger notification will fire, and within a
-minute Slack channel will receive an alert like:
+### 5. Alertmanager Integration (Optional)
+
+If you have Prometheus Alertmanager deployed, GreptimeDB automatically pushes
+firing and inactive alerts to it.
+
+After each evaluation, the Trigger injects fields from the query results into
+labels and annotations. In this example, `host` is included as a label and
+`avg_load1` is included as an annotation. These fields are propagated to
+Alertmanager and can be referenced in notification templates.
 
-![Trigger slack alert](/trigger-slack-alert.png)
+Since the payload is Alertmanager-compatible, you can use grouping, inhibition,
+silencing, and routing without adapters.
 
 ## Reference
 
-- [Syntax](/reference/sql/trigger-syntax.md): The syntax for SQL statements related to `TRIGGER`.
+- [Trigger Syntax](/reference/sql/trigger-syntax.md): The syntax for SQL statements
+related to `TRIGGER`
+- [INFORMATION_SCHEMA.TRIGGERS](/reference/sql/information-schema/triggers):
+    View for trigger metadata
+- [INFORMATION_SCHEMA.ALERTS](/reference/sql/information-schema/alerts):
+    View for alert instance metadata
 
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/enterprise/trigger.md b/i18n/zh/docusaurus-plugin-content-docs/current/enterprise/trigger.md
index 2e6fd0427..b1919d5e2 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/enterprise/trigger.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/enterprise/trigger.md
@@ -8,139 +8,259 @@ description: GreptimeDB 触发器概述。
 Trigger 允许用户基于 SQL 语句定义触发规则，GreptimeDB 根据这些触发规则进行周期性
 计算，当满足条件后对外发出通知。
 
-本篇文档的下述内容通过一个示例来展示如何使用 Trigger 监控系统负载并触发告警。
-如果想了解如何撰写 Trigger 的具体语法，请参考[语法](/reference/sql/trigger-syntax.md)文档。
+## 关键特性
 
-# 快速入门示例
+- **SQL 原生**：用 SQL 定义触发规则，复用 GreptimeDB 内置函数，无需额外学习成本
+- **多阶段状态管理**：内置 pending / firing / inactive 状态机，防止抖动和重复
+    通知
+- **丰富的上下文**：自定义 labels 和 annotations，并自动注入查询结果字段，便于精
+    准定位根因
+- **生态友好**：告警负载完全兼容 Prometheus Alertmanager，可直接使用其分组、抑制、
+    静默和路由功能
 
-本节将通过一个端到端示例展示如何使用触发器监控系统负载并触发告警。
+## 快速入门示例
 
-下图展示了该示例的完整端到端工作流程。
+本节通过端到端示例展示如何监控系统负载（`load1`），当负载超过阈值时触发告警。
 
-![触发器演示架构](/trigger-demo-architecture.png)
+在本示例中你将：
 
-1. Vector 持续采集主机指标并写入 GreptimeDB。
-2. GreptimeDB 中的 Trigger 每分钟评估规则；当条件满足时，会向 Alertmanager 发送
-    通知。
-3. Alertmanager 依据自身配置完成告警分组、抑制及路由，最终通过 Slack 集成将消息
-    发送至指定频道。
+- 创建指标表：建立 `load1` 表存储主机负载指标
+- 定义 Trigger：通过 SQL 设定触发条件，配置 labels、annotations 及通知方式
+- 模拟数据写入：依次注入正常与异常的负载数据，激活告警逻辑
+- 观察状态变化：实时查看告警实例从 pending → firing → inactive 的完整生命周期
 
-## 使用 Vector 采集主机指标
+### 1. 创建数据表
 
-首先，使用 Vector 采集本机的负载数据，并将数据写入 GreptimeDB 中。Vector 的配置
-示例如下所示：
+使用 MySQL 客户端连接 GreptimeDB，并创建 `load1` 表：
 
-```toml
-[sources.in]
-type = "host_metrics"
-scrape_interval_secs = 15
+```sql
+CREATE TABLE `load1` (
+    host            STRING,
+    load1           FLOAT32,
+    ts              TIMESTAMP TIME INDEX
+) WITH ('append_mode'='true');
+```
+
+### 2. 创建 Trigger
 
-[sinks.out]
-inputs = ["in"]
-type = "greptimedb"
-endpoint = "localhost:4001"
+使用 MySQL 客户端连接 GreptimeDB，并创建 `load1_monitor` Trigger：
+
+```sql
+CREATE TRIGGER IF NOT EXISTS `load1_monitor`
+    ON (
+        SELECT
+            host          AS label_host,
+            avg(load1)    AS avg_load1,
+            max(ts)       AS ts
+        FROM public.load1
+        WHERE ts >= NOW() - '1 minutes'::INTERVAL
+        GROUP BY host
+        HAVING avg(load1) > 10
+    ) EVERY '1 minutes'::INTERVAL
+    FOR '3 minutes'::INTERVAL
+    KEEP FIRING FOR '3 minutes'::INTERVAL
+    LABELS (severity=warning)
+    ANNOTATIONS (comment='Your computer is smoking, should take a break.')
+    NOTIFY(
+        WEBHOOK alert_manager URL 'http://localhost:9093' WITH (timeout='1m')
+    );
 ```
 
-GreptimeDB 会在数据写入的时候自动创建表，其中，`host_load1`表记录了 load1 数据，
-load1 是衡量系统活动的关键性能指标。我们可以创建监控规则来跟踪此表中的值。表结构
-如下所示：
+该 Trigger 每分钟运行一次，计算过去 60 秒内每台主机的平均负载，并为每个满足
+`avg(load1) > 10` 的主机生成告警实例。
+
+关键参数说明：
+
+- **FOR**：指定条件需要持续多久才会进入 firing 状态
+- **KEEP FIRING FOR**：指定条件不再满足后，告警实例在 firing 状态保持多久
+
+详见 [Trigger 语法](/reference/sql/trigger-syntax.md)。
+
+### 3. 查看 Trigger 状态
+
+#### 列出所有 Trigger
 
 ```sql
-+-----------+----------------------+------+------+---------+---------------+
-| Column    | Type                 | Key  | Null | Default | Semantic Type |
-+-----------+----------------------+------+------+---------+---------------+
-| ts        | TimestampMillisecond | PRI  | NO   |         | TIMESTAMP     |
-| collector | String               | PRI  | YES  |         | TAG           |
-| host      | String               | PRI  | YES  |         | TAG           |
-| val       | Float64              |      | YES  |         | FIELD         |
-+-----------+----------------------+------+------+---------+---------------+
+SHOW TRIGGERS;
 ```
 
-## 配置 Alertmanager 与 Slack 集成
+输出：
 
-GreptimeDB Trigger 的 Webhook payload 与 [Prometheus Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)
-兼容，因此我们可以复用 Alertmanager 的分组、抑制、静默和路由功能，而无需任何额外
-的胶水代码。
+```text
++---------------+
+| Triggers      |
++---------------+
+| load1_monitor |
++---------------+
+```
 
-你可以参考 [官方文档](https://prometheus.io/docs/alerting/latest/configuration/)
-对 Prometheus Alertmanager 进行配置。为在 Slack 消息中呈现一致、易读的内容，可以
-配置以下消息模板。
+#### 查看创建语句
+
+```sql
+SHOW CREATE TRIGGER `load1_monitor`\G
+```
+
+输出：
 
 ```text
-{{ define "slack.text" }}
-{{ range .Alerts }}
+*************************** 1. row ***************************
+       Trigger: load1_monitor
+Create Trigger: CREATE TRIGGER IF NOT EXISTS `load1_monitor`
+  ON (SELECT host AS label_host, avg(load1) AS avg_load1 ...) EVERY '1 minutes'::INTERVAL
+  FOR '3 minutes'::INTERVAL
+  KEEP FIRING FOR '3 minutes'::INTERVAL
+  LABELS (severity = 'warning')
+  ANNOTATIONS (comment = 'Your computer is smoking, should take a break.')
+  NOTIFY(
+    WEBHOOK `alert_manager` URL `http://localhost:9093` WITH (timeout = '1m'),
+  )
+```
 
-Labels:
-{{- range .Labels.SortedPairs }}
-- {{ .Name }}: {{ .Value }}
-{{ end }}
+#### 查看 Trigger 详情
 
-Annotations:
-{{- range .Annotations.SortedPairs }}
-- {{ .Name }}: {{ .Value }}
-{{ end }}
+```sql
+SELECT * FROM information_schema.triggers\G
+```
 
-{{ end }}
-{{ end }}
+输出：
+
+```text
+*************************** 1. row ***************************
+   trigger_name: load1_monitor
+     trigger_id: 1024
+        raw_sql: (SELECT host AS label_host, avg(load1) AS avg_load1, ...)
+       interval: 60
+         labels: {"severity":"warning"}
+    annotations: {"comment":"Your computer is smoking, should take a break."}
+            for: 180
+keep_firing_for: 180
+       channels: [{"channel_type":{"Webhook":{"opts":{"timeout":"1m"}, ...}]
+    flownode_id: 0
 ```
 
-使用上述模板生成 slack 消息会遍历所有的告警，并把每个告警的标签和注解展示出来。
+关于更多字段说明，参见 [Triggers](/reference/sql/information-schema/triggers)。
 
-当配置完成之后，启动 Alertmanager。
+#### 查看告警实例
+
+```sql
+SELECT * FROM information_schema.alerts;
+```
+
+如果尚未写入数据，将返回空结果。
 
-## 创建 Trigger
 
-在 GreptimeDB 中创建 Trigger。使用 MySQL 客户端连接 GreptimeDB 并执行以下 SQL：
+关于更多字段说明，参见 [Alerts](/reference/sql/information-schema/alerts)。
+
+### 4. 写入数据并观察告警状态
+
+下面的脚本模拟数据写入：先写入 1 分钟正常值，再写入 6 分钟的高值触发告警，随后
+恢复到正常值。
+
+```bash
+#!/usr/bin/env bash
+
+MYSQL="mysql -h 127.0.0.1 -P 4002"
+
+insert_normal() {
+  $MYSQL -e "INSERT INTO load1 (host, load1, ts) VALUES
+    ('newyork1', 1.2, now()),
+    ('newyork2', 1.1, now()),
+    ('newyork3', 1.3, now());"
+}
+
+insert_high() {
+  $MYSQL -e "INSERT INTO load1 (host, load1, ts) VALUES
+    ('newyork1', 1.2, now()),
+    ('newyork2', 12.1, now()),
+    ('newyork3', 11.5, now());"
+}
+
+# 第一分钟：正常数据
+for i in {1..4}; do insert_normal; sleep 15; done
+
+# 接下来 6 分钟：高负载
+for i in {1..24}; do insert_high; sleep 15; done
+
+# 之后：恢复正常
+while true; do insert_normal; sleep 15; done
+```
+
+#### 状态变迁
+
+在另一个终端中查询告警状态：
+
+**阶段 1：无告警**
 
 ```sql
-CREATE TRIGGER IF NOT EXISTS load1_monitor
-        ON (
-                SELECT collector AS label_collector,
-                host as label_host,
-                val
-                FROM host_load1 WHERE val > 10 and ts >= now() - '1 minutes'::INTERVAL
-        ) EVERY '1 minute'::INTERVAL
-        LABELS (severity=warning)
-        ANNOTATIONS (comment='Your computer is smoking, should take a break.')
-        NOTIFY(
-                WEBHOOK alert_manager URL 'http://localhost:9093' WITH (timeout="1m")
-        );
-```
-
-上述 SQL 将创建一个名为 `load1_monitor` 的触发器，每分钟运行一次。它会评估 `host_load1`
-表中最近 60 秒的数据；如果任何 load1 值超过 10，则 `NOTIFY` 子句中的 `WEBHOOK`
-选项会指定 Trigger 向在本地主机上运行且端口为 9093 的 Alertmanager 发送通知。
-
-执行 `SHOW TRIGGERS` 查看已创建的触发器列表。
+SELECT * FROM information_schema.alerts\G
+```
+
+输出：
+
+```
+Empty set
+```
+
+**阶段 2：pending**（条件首次满足，未达 `FOR` 时长）
 
 ```sql
-SHOW TRIGGERS;
+SELECT trigger_id, labels, active_at, fired_at, resolved_at FROM information_schema.alerts;
 ```
 
-输出结果应如下所示：
+```text
++------------+-----------------------------------------------------------------------+----------------------------+----------+-------------+
+| trigger_id | labels                                                                | active_at                  | fired_at | resolved_at |
++------------+-----------------------------------------------------------------------+----------------------------+----------+-------------+
+|       1024 | {"alert_name":"load1_monitor","host":"newyork3","severity":"warning"} | 2025-12-29 11:58:20.992670 | NULL     | NULL        |
+|       1024 | {"alert_name":"load1_monitor","host":"newyork2","severity":"warning"} | 2025-12-29 11:58:20.992670 | NULL     | NULL        |
++------------+-----------------------------------------------------------------------+----------------------------+----------+-------------+
+```
+
+**阶段 3：firing**（满足 `FOR`，开始发送通知）
+
+```sql
+SELECT trigger_id, labels, active_at, fired_at, resolved_at FROM information_schema.alerts;
+```
 
 ```text
-+---------------+
-| Triggers      |
-+---------------+
-| load1_monitor |
-+---------------+
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+-------------+
+| trigger_id | labels                                                                | active_at                  | fired_at                   | resolved_at |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+-------------+
+|       1024 | {"alert_name":"load1_monitor","host":"newyork3","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | NULL        |
+|       1024 | {"alert_name":"load1_monitor","host":"newyork2","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | NULL        |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+-------------+
 ```
 
-## 测试 Trigger
+**阶段 4：inactive**（条件不满足 + KEEP FIRING FOR 期满，发送恢复通知）
 
-使用 [stress-ng](https://github.com/ColinIanKing/stress-ng) 模拟 60 秒的高 CPU 负载：
+```sql
+SELECT trigger_id, labels, active_at, fired_at, resolved_at FROM information_schema.alerts;
+```
 
-```bash
-stress-ng --cpu 100 --cpu-load 10 --timeout 60
+```text
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+----------------------------+
+| trigger_id | labels                                                                | active_at                  | fired_at                   | resolved_at                |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+----------------------------+
+|       1024 | {"alert_name":"load1_monitor","host":"newyork3","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | 2025-12-29 12:05:20.991750 |
+|       1024 | {"alert_name":"load1_monitor","host":"newyork2","severity":"warning"} | 2025-12-29 11:58:20.992670 | 2025-12-29 12:02:20.991713 | 2025-12-29 12:05:20.991750 |
++------------+-----------------------------------------------------------------------+----------------------------+----------------------------+----------------------------+
 ```
 
-load1 值将快速上升，Trigger 通知将被触发，在一分钟之内，指定的 Slack 频道将收到如下
-告警：
+### 5. 集成 Alertmanager（可选）
+
+如果已部署 Prometheus Alertmanager，GreptimeDB 会自动将 firing 和 inactive 状态
+的告警推送过去。
+
+每次评估后，Trigger 会将查询结果中的字段注入 labels 和 annotations。本示例中，
+`host` 会作为 label，`avg_load1` 会作为 annotation。这些字段会传递到 Alertmanager，
+并可在通知模板中使用。
 
-![Slack 告警示意图](/trigger-slack-alert.png)
+由于 payload 与 Alertmanager 兼容，你可以直接复用其分组、抑制、静默和路由能力，
+无需适配器。
 
 ## 参考资料
 
-- [Trigger 语法](/reference/sql/trigger-syntax.md): 与 `TRIGGER` 相关的 SQL 语句的语法细节。
+- [Trigger 语法](/reference/sql/trigger-syntax.md): 与 `TRIGGER` 相关的 SQL 语句的语法细节
+- [INFORMATION_SCHEMA.TRIGGERS](/reference/sql/information-schema/triggers): 关于 `Trigger` 元数据的视图
+- [INFORMATION_SCHEMA.ALERTS](/reference/sql/information-schema/alerts): 关于告警实例元数据的视图