Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[improve]Optimize Hbase Master and Regionserver monitoring #2624

Merged
merged 3 commits into from
Aug 29, 2024
Merged

[improve]Optimize Hbase Master and Regionserver monitoring #2624

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b6e0ff0
[improve]add hbase mertics info
zhangshenghang Aug 28, 2024
58658b1
Merge branch 'master' into improve-add-hbase-metrics-info
yuluo-yx Aug 28, 2024
41814ca
Merge branch 'master' into improve-add-hbase-metrics-info
zqr10159 Aug 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions manager/src/main/resources/define/app-hbase_master.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
9 changes: 9 additions & 0 deletions manager/src/main/resources/define/app-hbase_regionserver.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
Loading