This is an automated email from the ASF dual-hosted git repository.
gongchao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git
The following commit(s) were added to refs/heads/master by this push:
new 092091073 [improve] add pulsar push rabbitmq i18n (#2509)
092091073 is described below
commit 09209107380c534fcce6275a8f0c144054e509dc
Author: aias00 <[email protected]>
AuthorDate: Mon Aug 12 22:45:40 2024 +0800
[improve] add pulsar push rabbitmq i18n (#2509)
Co-authored-by: tomsun28 <[email protected]>
---
manager/src/main/resources/define/app-pulsar.yml | 76 +++++++++++++++++++++-
manager/src/main/resources/define/app-push.yml | 3 +
manager/src/main/resources/define/app-rabbitmq.yml | 12 ++++
3 files changed, 89 insertions(+), 2 deletions(-)
diff --git a/manager/src/main/resources/define/app-pulsar.yml
b/manager/src/main/resources/define/app-pulsar.yml
index ce274f42d..5fdf89276 100644
--- a/manager/src/main/resources/define/app-pulsar.yml
+++ b/manager/src/main/resources/define/app-pulsar.yml
@@ -87,6 +87,9 @@ metrics:
method: GET
parseType: prometheus
- name: process_start_time_seconds
+ i18n:
+ zh-CN: 进程启动时间
+ en-US: Process Start Time
priority: 0
fields:
- field: value
@@ -109,6 +112,9 @@ metrics:
method: GET
parseType: prometheus
- name: process_open_fds
+ i18n:
+ zh-CN: 打开的文件描述符
+ en-US: Open File Descriptors
priority: 0
fields:
- field: value
@@ -130,6 +136,9 @@ metrics:
method: GET
parseType: prometheus
- name: process_max_fds
+ i18n:
+ zh-CN: 最大文件描述符
+ en-US: Max File Descriptors
priority: 0
fields:
- field: value
@@ -151,6 +160,9 @@ metrics:
method: GET
parseType: prometheus
- name: jvm_memory_pool_allocated_bytes
+ i18n:
+ zh-CN: JVM 内存池已分配字节
+ en-US: JVM Memory Pool Allocated Bytes
priority: 0
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
@@ -158,14 +170,20 @@ metrics:
- field: .name
type: 1
i18n:
- zh-CN: 指标名称
- en-US: Metric Name
+ zh-CN: 名称
+ en-US: Name
label: true
- field: pool
type: 1
label: true
+ i18n:
+ zh-CN: 池
+ en-US: Pool
- field: value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
# the config content when protocol is http
http:
# http host: ipv4 ipv6 domain
@@ -178,15 +196,24 @@ metrics:
method: GET
parseType: prometheus
- name: jvm_memory_pool_bytes_used
+ i18n:
+ zh-CN: JVM 内存池已使用字节
+ en-US: JVM Memory Pool Used Bytes
priority: 0
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
fields:
- field: pool
type: 1
+ i18n:
+ zh-CN: 池
+ en-US: Pool
label: true
- field: value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
# the config content when protocol is http
http:
# http host: ipv4 ipv6 domain
@@ -199,15 +226,24 @@ metrics:
method: GET
parseType: prometheus
- name: jvm_memory_pool_bytes_committed
+ i18n:
+ zh-CN: JVM 内存池已提交字节
+ en-US: JVM Memory Pool Committed Bytes
priority: 0
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
fields:
- field: pool
type: 1
+ i18n:
+ zh-CN: 池
+ en-US: Pool
label: true
- field: value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
# the config content when protocol is http
http:
# http host: ipv4 ipv6 domain
@@ -220,15 +256,24 @@ metrics:
method: GET
parseType: prometheus
- name: jvm_memory_pool_bytes_max
+ i18n:
+ zh-CN: JVM 内存池最大字节
+ en-US: JVM Memory Pool Max Bytes
priority: 0
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
fields:
- field: pool
type: 1
+ i18n:
+ zh-CN: 池
+ en-US: Pool
label: true
- field: value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
# the config content when protocol is http
http:
# http host: ipv4 ipv6 domain
@@ -241,6 +286,9 @@ metrics:
method: GET
parseType: prometheus
- name: pulsar_broker_publish_latency
+ i18n:
+ zh-CN: broker 发布延迟
+ en-US: Broker Publish Latency
priority: 0
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
@@ -253,12 +301,21 @@ metrics:
label: true
- field: cluster
type: 1
+ i18n:
+ zh-CN: 集群
+ en-US: Cluster
label: true
- field: quantile
type: 1
+ i18n:
+ zh-CN: 分位数
+ en-US: Quantile
label: true
- field: value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
# the config content when protocol is http
http:
# http host: ipv4 ipv6 domain
@@ -271,6 +328,9 @@ metrics:
method: GET
parseType: prometheus
- name: pulsar_metadata_store_ops_latency_ms
+ i18n:
+ zh-CN: 元数据存储操作延迟
+ en-US: Metadata Store Ops Latency
priority: 0
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
@@ -283,15 +343,27 @@ metrics:
label: true
- field: cluster
type: 1
+ i18n:
+ zh-CN: 集群
+ en-US: Cluster
label: true
- field: name
type: 1
+ i18n:
+ zh-CN: 名称
+ en-US: Name
label: true
- field: type
type: 1
+ i18n:
+ zh-CN: 类型
+ en-US: Type
label: true
- field: status
type: 1
+ i18n:
+ zh-CN: 状态
+ en-US: Status
label: true
- field: le
type: 0
diff --git a/manager/src/main/resources/define/app-push.yml
b/manager/src/main/resources/define/app-push.yml
index e16a35a5b..91bcd15ba 100644
--- a/manager/src/main/resources/define/app-push.yml
+++ b/manager/src/main/resources/define/app-push.yml
@@ -62,6 +62,9 @@ params:
metrics:
# metrics - all
- name: metrics
+ i18n:
+ zh-CN: 指标
+ en-US: Metrics
# metrics scheduling priority(0->127)->(high->low), metrics with the same
priority will be scheduled in parallel
# priority 0's metrics is availability metrics, it will be scheduled
first, only availability metrics collect success will the scheduling continue
priority: 0
diff --git a/manager/src/main/resources/define/app-rabbitmq.yml
b/manager/src/main/resources/define/app-rabbitmq.yml
index 58c3f9d11..eb2e2064a 100644
--- a/manager/src/main/resources/define/app-rabbitmq.yml
+++ b/manager/src/main/resources/define/app-rabbitmq.yml
@@ -104,6 +104,9 @@ params:
metrics:
# Note: The built-in monitoring metrics include (responseTime - response
time)
- name: overview
+ i18n:
+ zh-CN: 概览
+ en-US: Overview
# metrics scheduling priority(0->127)->(high->low), metrics with the same
priority will be scheduled in parallel
# priority 0's metrics is availability metrics, it will be scheduled
first, only availability metrics collect success will the scheduling continue
priority: 0
@@ -170,6 +173,9 @@ metrics:
parseType: default
- name: object_totals
+ i18n:
+ zh-CN: 对象总数
+ en-US: Object Totals
# metrics scheduling priority(0->127)->(high->low), metrics with the same
priority will be scheduled in parallel
# priority 0's metrics is availability metrics, it will be scheduled
first, only availability metrics collect success will the scheduling continue
priority: 1
@@ -224,6 +230,9 @@ metrics:
parseScript: '$.object_totals'
- name: nodes
+ i18n:
+ zh-CN: 节点数
+ en-US: Nodes
# metrics scheduling priority(0->127)->(high->low), metrics with the same
priority will be scheduled in parallel
# priority 0's metrics is availability metrics, it will be scheduled
first, only availability metrics collect success will the scheduling continue
priority: 1
@@ -443,6 +452,9 @@ metrics:
parseScript: '$.*'
- name: queues
+ i18n:
+ zh-CN: 队列数
+ en-US: Queues
# metrics scheduling priority(0->127)->(high->low), metrics with the same
priority will be scheduled in parallel
# priority 0's metrics is availability metrics, it will be scheduled
first, only availability metrics collect success will the scheduling continue
priority: 1
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
