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 ade04d2cf2 [doc] japanese hbase region server (#3479)
ade04d2cf2 is described below
commit ade04d2cf2b18c8f5c0c87d675e0d940d5869c75
Author: Calvin <[email protected]>
AuthorDate: Fri Jun 20 09:03:09 2025 +0800
[doc] japanese hbase region server (#3479)
---
.../src/main/resources/define/app-ftp.yml | 2 +-
.../src/main/resources/define/app-greenplum.yml | 2 +-
.../src/main/resources/define/app-h3c_switch.yml | 2 +-
.../src/main/resources/define/app-hadoop.yml | 2 +-
.../src/main/resources/define/app-hbase_master.yml | 2 +-
.../resources/define/app-hbase_regionserver.yml | 57 ++++++++++++++++++++++
6 files changed, 62 insertions(+), 5 deletions(-)
diff --git a/hertzbeat-manager/src/main/resources/define/app-ftp.yml
b/hertzbeat-manager/src/main/resources/define/app-ftp.yml
index 0deb961314..dfbc0b1884 100644
--- a/hertzbeat-manager/src/main/resources/define/app-ftp.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-ftp.yml
@@ -113,7 +113,7 @@ metrics:
i18n:
zh-CN: 概要
en-US: Basic
- ja-JP: 基本情報
+ ja-JP: 基礎情報
# 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/hertzbeat-manager/src/main/resources/define/app-greenplum.yml
b/hertzbeat-manager/src/main/resources/define/app-greenplum.yml
index fc4a8431f9..121aac6c19 100644
--- a/hertzbeat-manager/src/main/resources/define/app-greenplum.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-greenplum.yml
@@ -108,7 +108,7 @@ metrics:
i18n:
zh-CN: 基本信息
en-US: Basic Info
- ja-JP: 基本情報
+ ja-JP: 基礎情報
# 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/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml
b/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml
index 4a6c7f2dc3..de18d20563 100644
--- a/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml
@@ -27,7 +27,7 @@ help:
zh-CN: Hertzbeat 使用 <a class='help_module_content'
href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 协议</a> 对
华三交换机 的通用指标(可用性，系统信息，端口流量等)进行采集监控。<br>您可以点击 “<i>新建 华三通用交换机</i>”
并进行配置SNMP相关参数添加，或者选择“<i>更多操作</i>”，导入已有配置。
en-US: HertzBeat uses <a class='help_module_content'
href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP
Protocol</a> to monitoring H3C Switch general performance metrics. <br>You can
click the "<i>New H3C Switch</i>" button and config snmp params to add monitor
or import an existing setup through the "<i>More Actions</i>" menu.
zh-TW: Hertzbeat 使用 <a class='help_module_content'
href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 協議</a> 對
華三交換機 的通用指標(可用性，系統信息，端口流量等)進行采集監控。<br>您可以點擊 “<i>新建 華三通用交換機</i>”
並進行配置SNMP相關參數添加，或者選擇“<i>更多操作</i>”，導入已有配置。
- ja-JP: Hertzbeat は <a class='help_module_content'
href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP
プロトコルを介して</a> H3Cスイッチングハブの一般的なメトリック監視します。<br>「<i>新規
シスコ・スイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
+ ja-JP: Hertzbeat は <a class='help_module_content'
href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP
プロトコルを介して</a> H3Cスイッチングハブの一般的なメトリック監視します。<br>「<i>新規
H3Cスイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
helpLink:
zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/h3c_switch
en-US: https://hertzbeat.apache.org/docs/help/h3c_switch
diff --git a/hertzbeat-manager/src/main/resources/define/app-hadoop.yml
b/hertzbeat-manager/src/main/resources/define/app-hadoop.yml
index ffe4c8a1a4..f3e053e082 100644
--- a/hertzbeat-manager/src/main/resources/define/app-hadoop.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-hadoop.yml
@@ -27,7 +27,7 @@ help:
zh-CN: HertzBeat 使用<a class='help_module_content'
href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'>
JMX 协议</a>对 Hadoop 的 JVM 虚拟机的通用性能指标（memory pool，限JDK8及以下的code cache、class
loading、thread）进行采集监控。<br><span class='help_module_span'>⚠️注意：您需要在 Hadoop 应用开启
JMX 服务, <a class='help_module_content'
href='https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>点击查看开启步骤</a>。</span>
en-US: "HertzBeat monitors general performance metrics(memory pool, class
loading, thread) of Hadoop VMware through <a class='help_module_content'
href='https://zh.wikipedia.org/JMX'>JMX protocol</a>. <br><span
class='help_module_span'>⚠️Note: You should enable the JMX service in Hadoop
application, and the metric of code cache is only available to JDK8 and
below.<a class='help_module_content'
href='https://hertzbeat.apache.org/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%A
[...]
zh-TW: HertzBeat使用<a class='help_ module_ content'
href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'>
JMX協定</a>對Hadoop的JVM虛擬機器的通用性能指標（memory pool，限JDK8及以下的code cache、class
loading、thread）進行採集監控。<br><span class='help_ module_ span'> ⚠️
️注意：您需要在Hadoop應用開啟JMX服務，<a class='help_ module_ content'
href='https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>點擊查看開啟步驟</a>。</span>
- ja-JP: HertzBeatは <a class='help_module_content'
href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'>
JMXプロトコルを介して</a> Hadoopのランタイムステータス、ノード、トピック、その他の関連メトリックを監視します。<br><span
class='help_module_span'> ⚠️注意：Hadoop で JMX サービスを有効にする必要があります。<a
class='help_module_content' href='
https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>クリックしてガイドを見ます</a>。</span>
+ ja-JP: HertzBeatは <a class='help_module_content'
href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'>
JMXプロトコルを介して</a> HadoopのJava仮想マシンの一般的なパフォーマンスのメトリックを監視します。<br><span
class='help_module_span'> ⚠️注意：Hadoop で JMX サービスを有効にする必要があります。<a
class='help_module_content' href='
https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>クリックしてガイドを見ます</a>。</span>
helpLink:
zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hadoop/
en-US: https://hertzbeat.apache.org/docs/help/hadoop/
diff --git a/hertzbeat-manager/src/main/resources/define/app-hbase_master.yml
b/hertzbeat-manager/src/main/resources/define/app-hbase_master.yml
index c48470427f..e723fe2a77 100644
--- a/hertzbeat-manager/src/main/resources/define/app-hbase_master.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-hbase_master.yml
@@ -194,7 +194,7 @@ metrics:
i18n:
zh-CN: 基础信息
en-US: Basic Info
- ja-JP: 基本情報
+ ja-JP: 基礎情報
# 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: 2
diff --git
a/hertzbeat-manager/src/main/resources/define/app-hbase_regionserver.yml
b/hertzbeat-manager/src/main/resources/define/app-hbase_regionserver.yml
index af1e6a3a24..12a24f6488 100644
--- a/hertzbeat-manager/src/main/resources/define/app-hbase_regionserver.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-hbase_regionserver.yml
@@ -21,11 +21,13 @@ app: hbase_regionserver
name:
zh-CN: Apache Hbase RegionServer
en-US: Apache Hbase RegionServer
+ ja-JP: Apache Hbase RegionServer
# The description and help of this monitoring type
help:
zh-CN: Hertzbeat 对 Hbase 数据库 RegionServer 节点监控指标进行监控。<br>您可以点击 “<i>新建 Apache
Hbase RegionServer</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
en-US: Hertzbeat monitors the RegionServer node monitoring indicators of the
Hbase database. <br>You can click "<i>New Apache Hbase RegionServer</i>" to
configure, or select "<i>More Actions</i>" to import an existing configuration.
zh-TW: Hertzbeat 對 Hbase 數據庫 RegionServer 节點監控指標進行監控。<br>您可以點擊 “<i>新建 Apache
Hbase RegionServer</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
+ ja-JP: Hertzbeat は HbaseデータベースのRegionServerノードの一般的なメトリック監視します。<br>「<i>新規
Apache Hbase RegionServer</i>」をクリックしてパラメタを設定した後、新規することができます。
helpLink:
zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hbase_regionserver/
@@ -38,6 +40,7 @@ params:
name:
zh-CN: 目标Host
en-US: Target Host
+ ja-JP: 目標ホスト
# type-param field type(most mapping the html input type)
type: host
# required-true or false
@@ -48,6 +51,7 @@ params:
name:
zh-CN: 端口
en-US: Port
+ ja-JP: ポート
# type-param field type(most mapping the html input type)
type: number
# when type is number, range is required
@@ -62,6 +66,7 @@ params:
name:
zh-CN: 查询超时时间
en-US: Query Timeout
+ ja-JP: クエリタイムアウト
# type-param field type(most mapping the html input type)
type: number
# required-true or false
@@ -76,6 +81,7 @@ params:
name:
zh-CN: 启用HTTPS
en-US: HTTPS
+ ja-JP: HTTPS
# type-param field type(most mapping the html input type)
type: boolean
# required-true or false
@@ -87,6 +93,7 @@ metrics:
i18n:
zh-CN: RegionServer 服务信息
en-US: RegionServer Service Info
+ ja-JP: RegionServerサービス情報
# 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
@@ -98,24 +105,28 @@ metrics:
i18n:
zh-CN: Region数量
en-US: regionCount
+ ja-JP: Region数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: readRequestCount
type: 0
i18n:
zh-CN: 重启集群后的读请求数量
en-US: readRequestCount
+ ja-JP: 読み取りリクエスト数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: writeRequestCount
type: 0
i18n:
zh-CN: 重启集群后的写请求数量
en-US: writeRequestCount
+ ja-JP: 書き込みリクエスト数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: averageRegionSize
type: 0
i18n:
zh-CN: 平均Region大小
en-US: averageRegionSize
+ ja-JP: Regionの平均サイズ
unit: 'MB'
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: totalRequestCount
@@ -123,108 +134,126 @@ metrics:
i18n:
zh-CN: 全部请求数量
en-US: totalRequestCount
+ ja-JP: リクエスト総数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanTime_num_ops
type: 0
i18n:
zh-CN: Scan 请求总量
en-US: ScanTime_num_ops
+ ja-JP: Scan操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: Append_num_ops
type: 0
i18n:
zh-CN: Append 请求量
en-US: Append_num_ops
+ ja-JP: Append操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: Increment_num_ops
type: 0
i18n:
zh-CN: Increment请求量
en-US: Increment_num_ops
+ ja-JP: Increment操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: Get_num_ops
type: 0
i18n:
zh-CN: Get 请求量
en-US: Get_num_ops
+ ja-JP: Get操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: Delete_num_ops
type: 0
i18n:
zh-CN: Delete 请求量
en-US: Delete_num_ops
+ ja-JP: Delete操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: Put_num_ops
type: 0
i18n:
zh-CN: Put 请求量
en-US: Put_num_ops
+ ja-JP: Put操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanTime_mean
type: 0
i18n:
zh-CN: 平均 Scan 请求时间
en-US: ScanTime_mean
+ ja-JP: Scan操作の平均時間
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanTime_min
type: 0
i18n:
zh-CN: 最小 Scan 请求时间
en-US: ScanTime_min
+ ja-JP: Scan操作の最小時間
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanTime_max
type: 0
i18n:
zh-CN: 最大 Scan 请求时间
en-US: ScanTime_max
+ ja-JP: Scan操作の最大時間
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanSize_mean
type: 0
i18n:
zh-CN: 平均 Scan 请求大小
en-US: ScanSize_mean
+ ja-JP: Scan操作の平均サイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanSize_min
type: 0
i18n:
zh-CN: 最小 Scan 请求大小
en-US: ScanSize_min
+ ja-JP: Scan操作の最小サイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: ScanSize_max
type: 0
i18n:
zh-CN: 最大 Scan 请求大小
en-US: ScanSize_max
+ ja-JP: Scan操作の最大サイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: slowPutCount
type: 0
i18n:
zh-CN: 慢操作次数/Put
en-US: slowPutCount
+ ja-JP: スローPut操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: slowGetCount
type: 0
i18n:
zh-CN: 慢操作次数/Get
en-US: slowGetCount
+ ja-JP: スローGet操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: slowAppendCount
type: 0
i18n:
zh-CN: 慢操作次数/Append
en-US: slowAppendCount
+ ja-JP: スローAppend操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: slowIncrementCount
type: 0
i18n:
zh-CN: 慢操作次数/Increment
en-US: slowIncrementCount
+ ja-JP: スローIncrement操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: slowDeleteCount
type: 0
i18n:
zh-CN: 慢操作次数/Delete
en-US: slowDeleteCount
+ ja-JP: スローDelete操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: blockCacheSize
type: 0
@@ -232,36 +261,42 @@ metrics:
i18n:
zh-CN: 缓存块内存占用大小
en-US: blockCacheSize
+ ja-JP: ブロックキャッシュのサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: blockCacheCount
type: 0
i18n:
zh-CN: 缓存块数量_Block Cache 中的 Block 数量
en-US: blockCacheCount
+ ja-JP: ブロックキャッシュ数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: blockCacheExpressHitPercent
type: 0
i18n:
zh-CN: 读缓存命中率
en-US: blockCacheExpressHitPercent
+ ja-JP: ブロックキャッシュ命中率
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: memStoreSize
type: 0
i18n:
zh-CN: Memstore 大小
en-US: memStoreSize
+ ja-JP: Memstoreサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: FlushTime_num_ops
type: 0
i18n:
zh-CN: RS写磁盘次数/MemStore Flush 写磁盘次数
en-US: FlushTime_num_ops
+ ja-JP: MemStore Flush操作回数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: flushQueueLength
type: 0
i18n:
zh-CN: Region Flush 队列长度
en-US: flushQueueLength
+ ja-JP: Region Flushキューの長さ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: flushedCellsSize
type: 0
@@ -269,18 +304,21 @@ metrics:
i18n:
zh-CN: flush到磁盘大小
en-US: flushedCellsSize
+ ja-JP: flushedサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: storeCount
type: 0
i18n:
zh-CN: Store 个数
en-US: storeCount
+ ja-JP: Store数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: storeFileCount
type: 0
i18n:
zh-CN: Storefile 个数
en-US: storeFileCount
+ ja-JP: Storeファイル数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: storeFileSize
type: 0
@@ -288,36 +326,42 @@ metrics:
i18n:
zh-CN: Storefile 大小
en-US: storeFileSize
+ ja-JP: Storeファイルサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: compactionQueueLength
type: 0
i18n:
zh-CN: Compaction 队列长度
en-US: compactionQueueLength
+ ja-JP: Compactionキューの長さ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: percentFilesLocal
type: 0
i18n:
zh-CN: Region 的 HFile 位于本地 HDFS data node的比例
en-US: percentFilesLocal
+ ja-JP: Regionのローカルファイルのパーセント
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: percentFilesLocalSecondaryRegions
type: 0
i18n:
zh-CN: Region 副本的 HFile 位于本地 HDFS data node的比例
en-US: percentFilesLocalSecondaryRegions
+ ja-JP: Secondary Regionのローカルファイルのパーセント
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: hlogFileCount
type: 0
i18n:
zh-CN: WAL 文件数量
en-US: hlogFileCount
+ ja-JP: WALファイル数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: hlogFileSize
type: 0
i18n:
zh-CN: WAL 文件大小
en-US: hlogFileSize
+ ja-JP: WALファイルサイズ
# (optional)metrics field alias name, it is used as an alias field to
map and convert the collected data and metrics field
aliasFields:
- $.regionCount
@@ -414,6 +458,7 @@ metrics:
i18n:
zh-CN: RegionServer IPC 信息
en-US: RegionServer IPC Info
+ ja-JP: RegionServer IPC 情報
# 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
@@ -425,24 +470,28 @@ metrics:
i18n:
zh-CN: RPC句柄数
en-US: numActiveHandler
+ ja-JP: RPCハンドル数
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: NotServingRegionException
type: 0
i18n:
zh-CN: NotServingRegionException 异常数量
en-US: NotServingRegionException
+ ja-JP: NotServingRegionException
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: RegionMovedException
type: 0
i18n:
zh-CN: RegionMovedException异常数量
en-US: RegionMovedException
+ ja-JP: RegionMovedException
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: RegionTooBusyException
type: 0
i18n:
zh-CN: RegionTooBusyException异常数量
en-US: RegionTooBusyException
+ ja-JP: RegionTooBusyException
# (optional)metrics field alias name, it is used as an alias field to
map and convert the collected data and metrics field
aliasFields:
- $.numActiveHandler
@@ -468,6 +517,7 @@ metrics:
i18n:
zh-CN: RegionServer JVM 信息
en-US: RegionServer JVM Info
+ ja-JP: RegionServer Java仮想マシン情報
# 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: 2
@@ -480,6 +530,7 @@ metrics:
i18n:
zh-CN: 进程使用的非堆内存大小
en-US: MemNonHeapUsedM
+ ja-JP: 使用済みのノンヒープメモリサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: MemNonHeapCommittedM
type: 0
@@ -487,6 +538,7 @@ metrics:
i18n:
zh-CN: 进程 commit 的非堆内存大小
en-US: MemNonHeapCommittedM
+ ja-JP: コミットのノンヒープメモリサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: MemHeapUsedM
type: 0
@@ -494,6 +546,7 @@ metrics:
i18n:
zh-CN: 进程使用的堆内存大小
en-US: MemHeapUsedM
+ ja-JP: 使用済みのヒープメモリサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: MemHeapCommittedM
type: 0
@@ -501,6 +554,7 @@ metrics:
i18n:
zh-CN: 进程 commit 的堆内存大小
en-US: MemHeapCommittedM
+ ja-JP: コミットのヒープメモリサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: MemHeapMaxM
type: 0
@@ -508,6 +562,7 @@ metrics:
i18n:
zh-CN: 进程最大的堆内存大小
en-US: MemHeapMaxM
+ ja-JP: 最大のヒープメモリサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: MemMaxM
type: 0
@@ -515,12 +570,14 @@ metrics:
i18n:
zh-CN: 进程最大内存大小
en-US: MemMaxM
+ ja-JP: 最大のメモリサイズ
# field-metric name, type-metric type(0-number,1-string), unit-metric
unit('%','ms','MB'), label-whether it is a metrics label field
- field: GcCount
type: 0
i18n:
zh-CN: Young GC次数
en-US: GcCount
+ ja-JP: GC回数
# (optional)metrics field alias name, it is used as an alias field to
map and convert the collected data and metrics field
aliasFields:
- $.MemNonHeapUsedM
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
