This is an automated email from the ASF dual-hosted git repository.

zhaoqingran 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 f28996255 [Improve] improve kafka monitor (#2813)
f28996255 is described below

commit f28996255a36d4f92f4ff5e52555868fa4673c0e
Author: Jast <[email protected]>
AuthorDate: Wed Nov 13 21:35:04 2024 +0800

    [Improve] improve kafka monitor (#2813)
---
 .../src/main/resources/define/app-kafka_client.yml | 35 ++++------------------
 1 file changed, 5 insertions(+), 30 deletions(-)

diff --git a/hertzbeat-manager/src/main/resources/define/app-kafka_client.yml 
b/hertzbeat-manager/src/main/resources/define/app-kafka_client.yml
index 39601632b..82df32c04 100644
--- a/hertzbeat-manager/src/main/resources/define/app-kafka_client.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-kafka_client.yml
@@ -13,65 +13,50 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# The monitoring type category:service-application service monitoring 
db-database monitoring custom-custom monitoring os-operating system monitoring
 category: mid
-# The monitoring type eg: linux windows tomcat mysql aws...
 app: kafka_client
-# The monitoring i18n name
 name:
   zh-CN: Kafka消息系统(客户端)
   en-US: Kafka Message(Client)
-# The description and help of this monitoring type
+
 help:
   zh-CN: HertzBeat 使用 <a 
href="https://hertzbeat.apache.org/zh-cn/docs/help/kafka_client";>Kafka Admin 
Client</a> 对 Kafka 的通用指标进行采集监控。</span>
   en-US: HertzBeat uses <a 
href='https://hertzbeat.apache.org/docs/help/kafka_client'>Kafka Admin 
Client</a> to monitoring kafka general metrics. </span>
   zh-TW: HertzBeat 使用 <a 
href="https://hertzbeat.apache.org/zh-cn/docs/help/kafka_client";>Kafka Admin 
Client</a> 對 Kafka 的通用指標進行采集監控。</span>
+
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/kafka_client
   en-US: https://hertzbeat.apache.org/docs/help/kafka_client
-# Input params define for monitoring(render web ui by the definition)
+
 params:
-  # field-param field key
   - field: host
-    # name-param field display i18n name
     name:
       zh-CN: 目标Host
       en-US: Target Host
-    # type-param field type(most mapping the html input type)
     type: host
-    # required-true or false
     required: true
   - field: port
     name:
       zh-CN: 端口
       en-US: Port
     type: number
-    # when type is number, range is required
     range: '[0,65535]'
     required: true
     defaultValue: 9092
 
-# collect metrics config list
 metrics:
-  # metrics - server_info
   - name: topic_list
     i18n:
       zh-CN: 主题列表
       en-US: Topic List
-    # 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
-    # collect metrics content
     fields:
-      # field-metric name, type-metric type(0-number,1-string), unit-metric 
unit('%','ms','MB'), label-whether it is a metrics label field
       - field: TopicName
         type: 1
         i18n:
           zh-CN: 主题名称
           en-US: Topic Name
-    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, 
sdk
     protocol: kclient
-    # the config content when protocol is jmx
     kclient:
       host: ^_^host^_^
       port: ^_^port^_^
@@ -80,12 +65,8 @@ metrics:
     i18n:
       zh-CN: 主题详细信息
       en-US: Topic Detail 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: 1
-    # collect metrics content
     fields:
-      # field-metric name, type-metric type(0-number,1-string), unit-metric 
unit('%','ms','MB'), label-whether it is a metrics label field
       - field: TopicName
         type: 1
         i18n:
@@ -121,9 +102,7 @@ metrics:
         i18n:
           zh-CN: 复制因子
           en-US: Replication Factor
-    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, 
sdk
     protocol: kclient
-    # the config content when protocol is jmx
     kclient:
       host: ^_^host^_^
       port: ^_^port^_^
@@ -132,12 +111,10 @@ metrics:
     i18n:
       zh-CN: 主题偏移量
       en-US: Topic Offset
-    # 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
-    # collect metrics content
+    # Kafka offset does not need to be obtained frequently, as getting it too 
quickly will affect performance
+    interval: 300
     fields:
-      # field-metric name, type-metric type(0-number,1-string), unit-metric 
unit('%','ms','MB'), label-whether it is a metrics label field
       - field: TopicName
         type: 1
         i18n:
@@ -158,9 +135,7 @@ metrics:
         i18n:
           zh-CN: 最新偏移量
           en-US: Latest Offset
-    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, 
sdk
     protocol: kclient
-    # the config content when protocol is jmx
     kclient:
       host: ^_^host^_^
       port: ^_^port^_^


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to