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 1c5b3f9c3 [improve] add kafka influxdb jetty i18n (#2507)
1c5b3f9c3 is described below
commit 1c5b3f9c3f7e7753807a1f54b2f27308f369973e
Author: aias00 <[email protected]>
AuthorDate: Mon Aug 12 21:14:33 2024 +0800
[improve] add kafka influxdb jetty i18n (#2507)
---
.../main/resources/define/app-influxdb_promql.yml | 55 ++++++++
manager/src/main/resources/define/app-jetty.yml | 12 ++
manager/src/main/resources/define/app-kafka.yml | 150 +++++++++++++++++++++
.../src/main/resources/define/app-kafka_promql.yml | 48 +++++++
4 files changed, 265 insertions(+)
diff --git a/manager/src/main/resources/define/app-influxdb_promql.yml
b/manager/src/main/resources/define/app-influxdb_promql.yml
index a013fdcc2..ba0fcadb8 100644
--- a/manager/src/main/resources/define/app-influxdb_promql.yml
+++ b/manager/src/main/resources/define/app-influxdb_promql.yml
@@ -138,6 +138,9 @@ metrics:
# The first monitoring metrics basic_influxdb_memstats_alloc.
# Note: Built-in monitoring metrics include (responseTime - response time)
- name: basic_influxdb_memstats_alloc
+ i18n:
+ zh-CN: InfluxDB内存分配
+ en-US: InfluxDB Memory Allocation
# metrics scheduling priority(0->127), 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
@@ -146,10 +149,19 @@ metrics:
# Metric information includes the following: Field name, Type: 0-number,
1-string, instance: indicates whether the metric is the primary key, unit: the
unit of the metric
- field: instance
type: 1
+ i18n:
+ zh-CN: 实例
+ en-US: Instance
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 值
+ en-US: Value
# Monitoring protocol used for data collection, e.g. sql, ssh, http, telnet,
wmi, snmp, sdk.
protocol: http
# When the protocol is HTTP, the specific collection configuration is as
follows
@@ -185,6 +197,9 @@ metrics:
parseType: PromQL
- name: influxdb_database_numMeasurements
+ i18n:
+ zh-CN: InfluxDB数据库测量值
+ en-US: InfluxDB Database Measurements
# 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
@@ -193,14 +208,29 @@ metrics:
# Metric information includes the following: Field name, Type: 0-number,
1-string, instance: indicates whether the metric is the primary key, unit: the
unit of the metric
- field: job
type: 1
+ i18n:
+ zh-CN: 任务
+ en-US: Job
- field: instance
type: 1
+ i18n:
+ zh-CN: 实例
+ en-US: Instance
- field: database
type: 1
+ i18n:
+ zh-CN: 数据库
+ en-US: Database
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 值
+ en-US: Value
# Monitoring protocol used for data collection, e.g. sql, ssh, http,
telnet, wmi, snmp, sdk.
protocol: http
# When the protocol is HTTP, the specific collection configuration is as
follows
@@ -236,6 +266,9 @@ metrics:
parseType: PromQL
- name: influxdb_query_rate_seconds # Query rate per second
+ i18n:
+ zh-CN: 每秒查询速率
+ en-US: Query Rate Per Second
# metrics scheduling priority(0->127), 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
@@ -244,10 +277,19 @@ metrics:
# Metric information includes the following: Field name, Type: 0-number,
1-string, instance: indicates whether the metric is the primary key, unit: the
unit of the metric
- field: instance
type: 1
+ i18n:
+ zh-CN: 实例
+ en-US: Instance
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 值
+ en-US: Value
# Monitoring protocol used for data collection, e.g. sql, ssh, http,
telnet, wmi, snmp, sdk.
protocol: http
# When the protocol is HTTP, the specific collection configuration is as
follows
@@ -283,6 +325,10 @@ metrics:
parseType: PromQL
- name: influxdb_queryExecutor_queriesFinished_10s # Query rate per second
+
+ i18n:
+ zh-CN: 查询执行器每10秒查询完成数
+ en-US: Query Executor Queries Finished Every 10 Seconds
# metrics scheduling priority(0->127), 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
@@ -291,10 +337,19 @@ metrics:
# Metric information includes the following: Field name, Type: 0-number,
1-string, instance: indicates whether the metric is the primary key, unit: the
unit of the metric
- field: instance
type: 1
+ i18n:
+ zh-CN: 实例
+ en-US: Instance
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 值
+ en-US: Value
# Monitoring protocol used for data collection, e.g. sql, ssh, http,
telnet, wmi, snmp, sdk.
protocol: http
# When the protocol is HTTP, the specific collection configuration is as
follows
diff --git a/manager/src/main/resources/define/app-jetty.yml
b/manager/src/main/resources/define/app-jetty.yml
index 3f37d05b1..288275431 100644
--- a/manager/src/main/resources/define/app-jetty.yml
+++ b/manager/src/main/resources/define/app-jetty.yml
@@ -247,6 +247,9 @@ metrics:
url: ^_^url^_^
# metrics - class_loading
- name: class_loading
+ i18n:
+ zh-CN: 类加载信息
+ en-US: Class Loading
# 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
@@ -255,10 +258,19 @@ metrics:
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: LoadedClassCount
type: 0
+ i18n:
+ zh-CN: 已加载类总数
+ en-US: Loaded Class Count
- field: TotalLoadedClassCount
type: 0
+ i18n:
+ zh-CN: 总加载类总数
+ en-US: Total Loaded Class Count
- field: UnloadedClassCount
type: 0
+ i18n:
+ zh-CN: 未加载类总数
+ en-US: Unloaded Class Count
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: jmx
# the config content when protocol is http
diff --git a/manager/src/main/resources/define/app-kafka.yml
b/manager/src/main/resources/define/app-kafka.yml
index 81b736ced..2616b5aa8 100644
--- a/manager/src/main/resources/define/app-kafka.yml
+++ b/manager/src/main/resources/define/app-kafka.yml
@@ -77,6 +77,9 @@ params:
metrics:
# metrics - server_info
- name: server_info
+ i18n:
+ zh-CN: 服务器信息
+ en-US: Server Info
# 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
@@ -85,10 +88,19 @@ metrics:
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: Version
type: 1
+ i18n:
+ zh-CN: 版本
+ en-US: Version
- field: StartTimeMs
type: 1
+ i18n:
+ zh-CN: 启动时间
+ en-US: Start Time
- field: CommitId
type: 1
+ i18n:
+ zh-CN: CommitId
+ en-US: CommitId
# the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: jmx
# the config content when protocol is jmx
@@ -193,10 +205,16 @@ metrics:
url: ^_^url^_^
- name: active_controller_count
+ i18n:
+ zh-CN: 活跃控制器数量
+ en-US: Active Controller Count
priority: 1
fields:
- field: Value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
protocol: jmx
jmx:
host: ^_^host^_^
@@ -208,10 +226,16 @@ metrics:
url: ^_^url^_^
- name: broker_partition_count
+ i18n:
+ zh-CN: Broker分区数量
+ en-US: Broker Partition Count
priority: 1
fields:
- field: Value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
protocol: jmx
jmx:
host: ^_^host^_^
@@ -223,10 +247,16 @@ metrics:
url: ^_^url^_^
- name: broker_leader_count
+ i18n:
+ zh-CN: Broker领导者数量
+ en-US: Broker Leader Count
priority: 1
fields:
- field: Value
type: 0
+ i18n:
+ zh-CN: 值
+ en-US: Value
protocol: jmx
jmx:
host: ^_^host^_^
@@ -238,22 +268,46 @@ metrics:
url: ^_^url^_^
- name: broker_handler_avg_percent
+ i18n:
+ zh-CN: Broker处理器平均百分比
+ en-US: Broker Handler Avg Percent
priority: 2
fields:
- field: EventType
type: 1
+ i18n:
+ zh-CN: 事件类型
+ en-US: Event Type
- field: RateUnit
type: 1
+ i18n:
+ zh-CN: 速率单位
+ en-US: Rate Unit
- field: Count
type: 0
+ i18n:
+ zh-CN: 计数
+ en-US: Count
- field: MeanRate
type: 0
+ i18n:
+ zh-CN: 平均速率
+ en-US: Mean Rate
- field: OneMinuteRate
type: 0
+ i18n:
+ zh-CN: 一分钟速率
+ en-US: One Minute Rate
- field: FiveMinuteRate
type: 0
+ i18n:
+ zh-CN: 五分钟速率
+ en-US: Five Minute Rate
- field: FifteenMinuteRate
type: 0
+ i18n:
+ zh-CN: 十五分钟速率
+ en-US: Fifteen Minute Rate
protocol: jmx
jmx:
host: ^_^host^_^
@@ -265,22 +319,46 @@ metrics:
url: ^_^url^_^
- name: topic_bytes_in_persec
+ i18n:
+ zh-CN: 每秒主题流入字节
+ en-US: Topic Bytes In PerSec
priority: 2
fields:
- field: EventType
type: 1
+ i18n:
+ zh-CN: 事件类型
+ en-US: Event Type
- field: RateUnit
type: 1
+ i18n:
+ zh-CN: 速率单位
+ en-US: Rate Unit
- field: MeanRate
type: 0
+ i18n:
+ zh-CN: 平均速率
+ en-US: Mean Rate
- field: OneMinuteRate
type: 0
+ i18n:
+ zh-CN: 一分钟速率
+ en-US: One Minute Rate
- field: FiveMinuteRate
type: 0
+ i18n:
+ zh-CN: 五分钟速率
+ en-US: Five Minute Rate
- field: FifteenMinuteRate
type: 0
+ i18n:
+ zh-CN: 十五分钟速率
+ en-US: Fifteen Minute Rate
- field: Count
type: 0
+ i18n:
+ zh-CN: 计数
+ en-US: Count
protocol: jmx
jmx:
host: ^_^host^_^
@@ -292,22 +370,46 @@ metrics:
url: ^_^url^_^
- name: topic_bytes_out_persec
+ i18n:
+ zh-CN: 每秒主题流出字节
+ en-US: Topic Bytes Out PerSec
priority: 2
fields:
- field: EventType
type: 1
+ i18n:
+ zh-CN: 事件类型
+ en-US: Event Type
- field: RateUnit
type: 1
+ i18n:
+ zh-CN: 速率单位
+ en-US: Rate Unit
- field: MeanRate
type: 0
+ i18n:
+ zh-CN: 平均速率
+ en-US: Mean Rate
- field: OneMinuteRate
type: 0
+ i18n:
+ zh-CN: 一分钟速率
+ en-US: One Minute Rate
- field: FiveMinuteRate
type: 0
+ i18n:
+ zh-CN: 五分钟速率
+ en-US: Five Minute Rate
- field: FifteenMinuteRate
type: 0
+ i18n:
+ zh-CN: 十五分钟速率
+ en-US: Fifteen Minute Rate
- field: Count
type: 0
+ i18n:
+ zh-CN: 计数
+ en-US: Count
protocol: jmx
jmx:
host: ^_^host^_^
@@ -319,22 +421,46 @@ metrics:
url: ^_^url^_^
- name: produce_message_conversions_persec
+ i18n:
+ zh-CN: 每秒生产消息转换
+ en-US: Produce Message Conversions PerSec
priority: 2
fields:
- field: EventType
type: 1
+ i18n:
+ zh-CN: 事件类型
+ en-US: Event Type
- field: RateUnit
type: 1
+ i18n:
+ zh-CN: 速率单位
+ en-US: Rate Unit
- field: MeanRate
type: 0
+ i18n:
+ zh-CN: 平均速率
+ en-US: Mean Rate
- field: OneMinuteRate
type: 0
+ i18n:
+ zh-CN: 一分钟速率
+ en-US: One Minute Rate
- field: FiveMinuteRate
type: 0
+ i18n:
+ zh-CN: 五分钟速率
+ en-US: Five Minute Rate
- field: FifteenMinuteRate
type: 0
+ i18n:
+ zh-CN: 十五分钟速率
+ en-US: Fifteen Minute Rate
- field: Count
type: 0
+ i18n:
+ zh-CN: 计数
+ en-US: Count
protocol: jmx
jmx:
host: ^_^host^_^
@@ -346,22 +472,46 @@ metrics:
url: ^_^url^_^
- name: produce_total_requests_persec
+ i18n:
+ zh-CN: 每秒生产总请求数
+ en-US: Produce Total Requests PerSec
priority: 2
fields:
- field: EventType
type: 1
+ i18n:
+ zh-CN: 事件类型
+ en-US: Event Type
- field: RateUnit
type: 1
+ i18n:
+ zh-CN: 速率单位
+ en-US: Rate Unit
- field: MeanRate
type: 0
+ i18n:
+ zh-CN: 平均速率
+ en-US: Mean Rate
- field: OneMinuteRate
type: 0
+ i18n:
+ zh-CN: 一分钟速率
+ en-US: One Minute Rate
- field: FiveMinuteRate
type: 0
+ i18n:
+ zh-CN: 五分钟速率
+ en-US: Five Minute Rate
- field: FifteenMinuteRate
type: 0
+ i18n:
+ zh-CN: 十五分钟速率
+ en-US: Fifteen Minute Rate
- field: Count
type: 0
+ i18n:
+ zh-CN: 计数
+ en-US: Count
protocol: jmx
jmx:
host: ^_^host^_^
diff --git a/manager/src/main/resources/define/app-kafka_promql.yml
b/manager/src/main/resources/define/app-kafka_promql.yml
index 8815f6ca8..4aadbd143 100644
--- a/manager/src/main/resources/define/app-kafka_promql.yml
+++ b/manager/src/main/resources/define/app-kafka_promql.yml
@@ -136,6 +136,9 @@ params:
metrics:
# metrics - kafka_brokers
- name: kafka_brokers
+ i18n:
+ zh-CN: Kafka Broker 数量
+ en-US: Kafka Broker Count
# 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
@@ -144,12 +147,24 @@ metrics:
# field-metric name, i18n-metric name i18n label, type-metric
type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a
metrics label field
- field: __name__
type: 1
+ i18n:
+ zh-CN: 名称
+ en-US: Name
- field: instance
type: 1
+ i18n:
+ zh-CN: 实例
+ en-US: Instance
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 数值
+ en-US: Value
# The protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
# The config content when protocol is http
@@ -183,6 +198,9 @@ metrics:
parseType: PromQL
- name: kafka_topic_partitions
+ i18n:
+ zh-CN: Kafka Topic 分区数量
+ en-US: Kafka Topic Partitions
# 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
@@ -191,12 +209,24 @@ metrics:
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: __name__
type: 1
+ i18n:
+ zh-CN: 名称
+ en-US: Name
- field: topic
type: 1
+ i18n:
+ zh-CN: 主题
+ en-US: Topic
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 数值
+ en-US: Value
# The protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
# The config content when protocol is http
@@ -231,6 +261,9 @@ metrics:
parseType: PromQL
- name: kafka_server_brokertopicmetrics_bytesinpersec # Query rate per
second
+ i18n:
+ zh-CN: Kafka Server Broker Topic 每秒字节入
+ en-US: Kafka Server Broker Topic Bytes In Per Second
# 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
@@ -239,14 +272,29 @@ metrics:
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: instance
type: 1
+ i18n:
+ zh-CN: 实例
+ en-US: Instance
- field: job
type: 1
+ i18n:
+ zh-CN: 任务
+ en-US: Job
- field: topic
type: 1
+ i18n:
+ zh-CN: 主题
+ en-US: Topic
- field: timestamp
type: 1
+ i18n:
+ zh-CN: 时间戳
+ en-US: Timestamp
- field: value
type: 1
+ i18n:
+ zh-CN: 数值
+ en-US: Value
# The protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp,
sdk
protocol: http
# The specific collection configuration when the protocol is http
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
