This is an automated email from the ASF dual-hosted git repository.
morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new b1b07d7f149 [fix] correct doris_fe_txn_counter metric label typo and
description (#3676)
b1b07d7f149 is described below
commit b1b07d7f149cd3984a50b357499478dd468c61aa
Author: boluor <[email protected]>
AuthorDate: Tue May 19 13:08:16 2026 -0700
[fix] correct doris_fe_txn_counter metric label typo and description (#3676)
## Summary
Two errors in the metrics doc (`admin-manual/maint-monitor/metrics.md`)
for the `doris_fe_txn_counter` metric, both verified against the FE
source `MetricRepo.java`:
- **#14** — the `type` label is written `succes`; the metric actually
emits `success` (`COUNTER_TXN_SUCCESS.addLabel(new MetricLabel("type",
"success"))`). Fixed the doc typo.
- **#15** — the `type="begin"` row was described as "Number of committed
transactions" (Chinese: "提交的事务数量"). The `begin` counter counts begun
transactions (FE source description: "counter of beginning
transactions"); commit corresponds to `success`. Corrected to "Number of
begun transactions" / "开始的事务数量". The BE metric
`doris_be_stream_load_txn_request {type="begin"}` in the same doc
already correctly says "begun".
Applied across all affected versions: EN (next + 4.x) and Chinese (next
+ 2.1/3.x/4.x).
## Test plan
- [x] Verified the label spelling and the `begin` counter semantics
against `apache/doris` FE `MetricRepo.java`
- [x] Verified which versions contained each issue
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
---
docs/admin-manual/maint-monitor/metrics.md | 4 ++--
.../current/admin-manual/maint-monitor/metrics.md | 4 ++--
.../version-2.1/admin-manual/maint-monitor/metrics.md | 4 ++--
.../version-3.x/admin-manual/maint-monitor/metrics.md | 4 ++--
.../version-4.x/admin-manual/maint-monitor/metrics.md | 4 ++--
versioned_docs/version-4.x/admin-manual/maint-monitor/metrics.md | 4 ++--
6 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/docs/admin-manual/maint-monitor/metrics.md
b/docs/admin-manual/maint-monitor/metrics.md
index a8d3317afbb..1fc27c239dd 100644
--- a/docs/admin-manual/maint-monitor/metrics.md
+++ b/docs/admin-manual/maint-monitor/metrics.md
@@ -146,10 +146,10 @@ curl http://be_host:webserver_port/metrics?type=json
| | {name="schema-change-pool"} | Num | Thread pool used by the Master FE to
schedule schema change jobs | | |
| | {name="thrift-server-pool"} | Num | Worker thread pool of the FE-side
ThriftServer. Corresponds to `rpc_port` in fe.conf and is used to interact with
BEs | | |
| `doris_fe_txn_counter` | | Num | Cumulative count of load transactions in
each state | Observe the execution status of load transactions | P0 |
-| | {type="begin"} | Num | Number of committed transactions | | |
+| | {type="begin"} | Num | Number of begun transactions | | |
| | {type="failed"} | Num | Number of failed transactions | | |
| | {type="reject"} | Num | Number of rejected transactions (for example,
when the current number of running transactions exceeds the threshold, new
transactions are rejected) | | |
-| | {type="succes"} | Num | Number of successful transactions | | |
+| | {type="success"} | Num | Number of successful transactions | | |
| `doris_fe_txn_status` | | Num | Number of load transactions currently in
each state. For example, {type="committed"} indicates the number of
transactions in the committed state | Observe the number of load transactions
in each state to determine whether there is a backlog | P0 |
| `doris_fe_query_instance_num` | | Num | Number of fragment instances
currently being requested by a specific user. For example, {user="test_u"}
indicates the number of instances currently being requested by user test_u |
Use this value to observe whether a specific user is consuming too many query
resources | P0 |
| `doris_fe_query_instance_begin` | | Num | Number of fragment instances for
which a specific user has started requests. For example, {user="test_u"}
indicates the number of instances for which user test_u has started requests |
Use this value to observe whether a specific user has submitted too many
queries | P0 |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metrics.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metrics.md
index 44beb58fa78..e20e93e0c01 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metrics.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metrics.md
@@ -146,10 +146,10 @@ curl http://be_host:webserver_port/metrics?type=json
| | {name="schema-change-pool"} | Num | Master FE 用于调度 schema change 作业的线程池 |
| |
| | {name="thrift-server-pool"} | Num | FE 端 ThriftServer 的工作线程池。对应 fe.conf 中
`rpc_port`，用于和 BE 进行交互 | | |
| `doris_fe_txn_counter` | | Num | 统计各个状态的导入事务的数量的累计值 | 可以观测导入事务的执行情况 | P0 |
-| | {type="begin"} | Num | 提交的事务数量 | | |
+| | {type="begin"} | Num | 开始的事务数量 | | |
| | {type="failed"} | Num | 失败的事务数量 | | |
| | {type="reject"} | Num | 被拒绝的事务数量（如当前运行事务数大于阈值，则新的事务会被拒绝） | | |
-| | {type="succes"} | Num | 成功的事务数量 | | |
+| | {type="success"} | Num | 成功的事务数量 | | |
| `doris_fe_txn_status` | | Num | 统计当前处于各个状态的导入事务的数量。如 {type="committed"}
表示处于 committed 状态的事务的数量 | 可以观测各个状态下导入事务的数量，来判断是否有堆积 | P0 |
| `doris_fe_query_instance_num` | | Num | 指定用户当前正在请求的 fragment instance 数目。如
{user="test_u"} 表示用户 test_u 当前正在请求的 instance 数目 | 该数值可以用于观测指定用户是否占用过多查询资源 | P0 |
| `doris_fe_query_instance_begin` | | Num | 指定用户请求开始的 fragment instance 数目。如
{user="test_u"} 表示用户 test_u 开始请求的 instance 数目 | 该数值可以用于观测指定用户是否提交了过多查询 | P0 |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metrics.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metrics.md
index 05827eabccd..f3f4f33910e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metrics.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metrics.md
@@ -111,10 +111,10 @@ curl http://be_host:webserver_port/metrics?type=json
| | {name="schema-change-pool"}
| Num | Master FE 用于调度 schema change 作业的线程池
|
|
| | {name="thrift-server-pool"}
| Num | FE 端 ThriftServer 的工作线程池。对应 fe.conf 中 `rpc_port`。用于和 BE 进行交互。
|
|
| `doris_fe_txn_counter` |
| Num | 统计各个状态的导入事务的数量的累计值
| 可以观测导入事务的执行情况。
| P0 |
-| | {type="begin"}
| Num | 提交的事务数量
|
|
+| | {type="begin"}
| Num | 开始的事务数量
|
|
| | {type="failed"}
| Num | 失败的事务数量
|
|
| | {type="reject"}
| Num | 被拒绝的事务数量。（如当前运行事务数大于阈值，则新的事务会被拒绝）
|
|
-| | {type="succes"}
| Num | 成功的事务数量
|
|
+| | {type="success"}
| Num | 成功的事务数量
|
|
| `doris_fe_txn_status` |
| Num | 统计当前处于各个状态的导入事务的数量。如 {type="committed"} 表示处于 committed 状态的事务的数量
| 可以观测各个状态下导入事务的数量，来判断是否有堆积
| P0 |
| `doris_fe_query_instance_num` |
| Num | 指定用户当前正在请求的 fragment instance 数目。如 {user="test_u"} 表示用户 test_u
当前正在请求的 instance 数目 | 该数值可以用于观测指定用户是否占用过多查询资源
| P0 |
| `doris_fe_query_instance_begin` |
| Num | 指定用户请求开始的 fragment instance 数目。如 {user="test_u"} 表示用户 test_u
开始请求的 instance 数目 | 该数值可以用于观测指定用户是否提交了过多查询
| P0 |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/maint-monitor/metrics.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/maint-monitor/metrics.md
index 75fa8e26065..1390b569ee6 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/maint-monitor/metrics.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/admin-manual/maint-monitor/metrics.md
@@ -119,10 +119,10 @@ curl http://be_host:webserver_port/metrics?type=json
| | {name="schema-change-pool"}
| Num | Master FE 用于调度 schema change 作业的线程池
|
|
| | {name="thrift-server-pool"}
| Num | FE 端 ThriftServer 的工作线程池。对应 fe.conf 中 `rpc_port`。用于和 BE 进行交互。
|
|
| `doris_fe_txn_counter` |
| Num | 统计各个状态的导入事务的数量的累计值
| 可以观测导入事务的执行情况。
| P0 |
-| | {type="begin"}
| Num | 提交的事务数量
|
|
+| | {type="begin"}
| Num | 开始的事务数量
|
|
| | {type="failed"}
| Num | 失败的事务数量
|
|
| | {type="reject"}
| Num | 被拒绝的事务数量。（如当前运行事务数大于阈值，则新的事务会被拒绝）
|
|
-| | {type="succes"}
| Num | 成功的事务数量
|
|
+| | {type="success"}
| Num | 成功的事务数量
|
|
| `doris_fe_txn_status` |
| Num | 统计当前处于各个状态的导入事务的数量。如 {type="committed"} 表示处于 committed 状态的事务的数量
| 可以观测各个状态下导入事务的数量，来判断是否有堆积
| P0 |
| `doris_fe_query_instance_num` |
| Num | 指定用户当前正在请求的 fragment instance 数目。如 {user="test_u"} 表示用户 test_u
当前正在请求的 instance 数目 | 该数值可以用于观测指定用户是否占用过多查询资源
| P0 |
| `doris_fe_query_instance_begin` |
| Num | 指定用户请求开始的 fragment instance 数目。如 {user="test_u"} 表示用户 test_u
开始请求的 instance 数目 | 该数值可以用于观测指定用户是否提交了过多查询
| P0 |
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/maint-monitor/metrics.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/maint-monitor/metrics.md
index 44beb58fa78..e20e93e0c01 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/maint-monitor/metrics.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/maint-monitor/metrics.md
@@ -146,10 +146,10 @@ curl http://be_host:webserver_port/metrics?type=json
| | {name="schema-change-pool"} | Num | Master FE 用于调度 schema change 作业的线程池 |
| |
| | {name="thrift-server-pool"} | Num | FE 端 ThriftServer 的工作线程池。对应 fe.conf 中
`rpc_port`，用于和 BE 进行交互 | | |
| `doris_fe_txn_counter` | | Num | 统计各个状态的导入事务的数量的累计值 | 可以观测导入事务的执行情况 | P0 |
-| | {type="begin"} | Num | 提交的事务数量 | | |
+| | {type="begin"} | Num | 开始的事务数量 | | |
| | {type="failed"} | Num | 失败的事务数量 | | |
| | {type="reject"} | Num | 被拒绝的事务数量（如当前运行事务数大于阈值，则新的事务会被拒绝） | | |
-| | {type="succes"} | Num | 成功的事务数量 | | |
+| | {type="success"} | Num | 成功的事务数量 | | |
| `doris_fe_txn_status` | | Num | 统计当前处于各个状态的导入事务的数量。如 {type="committed"}
表示处于 committed 状态的事务的数量 | 可以观测各个状态下导入事务的数量，来判断是否有堆积 | P0 |
| `doris_fe_query_instance_num` | | Num | 指定用户当前正在请求的 fragment instance 数目。如
{user="test_u"} 表示用户 test_u 当前正在请求的 instance 数目 | 该数值可以用于观测指定用户是否占用过多查询资源 | P0 |
| `doris_fe_query_instance_begin` | | Num | 指定用户请求开始的 fragment instance 数目。如
{user="test_u"} 表示用户 test_u 开始请求的 instance 数目 | 该数值可以用于观测指定用户是否提交了过多查询 | P0 |
diff --git a/versioned_docs/version-4.x/admin-manual/maint-monitor/metrics.md
b/versioned_docs/version-4.x/admin-manual/maint-monitor/metrics.md
index a8d3317afbb..1fc27c239dd 100644
--- a/versioned_docs/version-4.x/admin-manual/maint-monitor/metrics.md
+++ b/versioned_docs/version-4.x/admin-manual/maint-monitor/metrics.md
@@ -146,10 +146,10 @@ curl http://be_host:webserver_port/metrics?type=json
| | {name="schema-change-pool"} | Num | Thread pool used by the Master FE to
schedule schema change jobs | | |
| | {name="thrift-server-pool"} | Num | Worker thread pool of the FE-side
ThriftServer. Corresponds to `rpc_port` in fe.conf and is used to interact with
BEs | | |
| `doris_fe_txn_counter` | | Num | Cumulative count of load transactions in
each state | Observe the execution status of load transactions | P0 |
-| | {type="begin"} | Num | Number of committed transactions | | |
+| | {type="begin"} | Num | Number of begun transactions | | |
| | {type="failed"} | Num | Number of failed transactions | | |
| | {type="reject"} | Num | Number of rejected transactions (for example,
when the current number of running transactions exceeds the threshold, new
transactions are rejected) | | |
-| | {type="succes"} | Num | Number of successful transactions | | |
+| | {type="success"} | Num | Number of successful transactions | | |
| `doris_fe_txn_status` | | Num | Number of load transactions currently in
each state. For example, {type="committed"} indicates the number of
transactions in the committed state | Observe the number of load transactions
in each state to determine whether there is a backlog | P0 |
| `doris_fe_query_instance_num` | | Num | Number of fragment instances
currently being requested by a specific user. For example, {user="test_u"}
indicates the number of instances currently being requested by user test_u |
Use this value to observe whether a specific user is consuming too many query
resources | P0 |
| `doris_fe_query_instance_begin` | | Num | Number of fragment instances for
which a specific user has started requests. For example, {user="test_u"}
indicates the number of instances for which user test_u has started requests |
Use this value to observe whether a specific user has submitted too many
queries | P0 |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
