From 3eb6fb35f452a7ded3e7e677cc4e48042936220e Mon Sep 17 00:00:00 2001 From: Jast Date: Thu, 29 Aug 2024 10:55:53 +0800 Subject: [PATCH] [improve]Optimize Hbase Master and Regionserver monitoring (#2624) Co-authored-by: shown Co-authored-by: Logic --- manager/src/main/resources/define/app-hbase_master.yml | 9 +++++++++ .../src/main/resources/define/app-hbase_regionserver.yml | 9 +++++++++ 2 files changed, 18 insertions(+) diff --git a/manager/src/main/resources/define/app-hbase_master.yml b/manager/src/main/resources/define/app-hbase_master.yml index c0bbb4e01a3..b3921217226 100644 --- a/manager/src/main/resources/define/app-hbase_master.yml +++ b/manager/src/main/resources/define/app-hbase_master.yml @@ -74,6 +74,9 @@ params: metrics: # metrics - Server - name: Server + i18n: + zh-CN: Master服务信息 + en-US: Master Service 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 @@ -125,6 +128,9 @@ metrics: parseType: jsonPath parseScript: '$.beans[?(@.name == "Hadoop:service=HBase,name=Master,sub=Server")]' - name: Rit + i18n: + zh-CN: Region In Transition 信息 + en-US: Region In Transition 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 @@ -168,6 +174,9 @@ metrics: parseType: jsonPath parseScript: '$.beans[?(@.name == "Hadoop:service=HBase,name=Master,sub=AssignmentManager")]' - name: basic + i18n: + zh-CN: 基础信息 + en-US: Basic 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 diff --git a/manager/src/main/resources/define/app-hbase_regionserver.yml b/manager/src/main/resources/define/app-hbase_regionserver.yml index 82476c56ee5..630a2f5c51e 100644 --- a/manager/src/main/resources/define/app-hbase_regionserver.yml +++ b/manager/src/main/resources/define/app-hbase_regionserver.yml @@ -74,6 +74,9 @@ params: metrics: # metrics - Server - name: Server + i18n: + zh-CN: RegionServer 服务信息 + en-US: RegionServer Service 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 @@ -435,6 +438,9 @@ metrics: parseScript: '$.beans[?(@.name == "Hadoop:service=HBase,name=RegionServer,sub=Server")]' # metrics - IPC - name: IPC + i18n: + zh-CN: RegionServer IPC 信息 + en-US: RegionServer IPC 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 @@ -490,6 +496,9 @@ metrics: parseScript: '$.beans[?(@.name == "Hadoop:service=HBase,name=RegionServer,sub=IPC")]' # metrics - JVM - name: JVM + i18n: + zh-CN: RegionServer JVM 信息 + en-US: RegionServer JVM 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