Merge branch 'master' into asf-footer

Co-authored-by: Calvin <zhengqiwei@apache.org>
Co-authored-by: tomsun28 <tomsun28@outlook.com>

.asf.yaml

@@ -16,7 +16,7 @@
 #
 
 github:
-  description: Apache HertzBeat(incubating) is a real-time monitoring system with agentless, performance cluster, prometheus-compatible, custom monitoring and status page building capabilities.
+  description: Real-time monitoring system with agentless, performance cluster, prometheus-compatible, custom monitoring and status page building capabilities.
   homepage: https://hertzbeat.apache.org/
   labels:
     - monitoring

.licenserc.yaml

@@ -67,6 +67,7 @@ header:
     - 'karma.conf.js'
     - 'proxy.conf.js'
     - '.helmignore'
+    - 'script/helm/**'
     - 'web-app/src/app/core/**'
     - 'web-app/src/app/layout/**'
     - 'web-app/src/app/routes/exception/**'

DISCLAIMER

@@ -1,10 +0,0 @@
-Apache HertzBeat (incubating) is an effort undergoing incubation at the Apache 
-Software Foundation (ASF), sponsored by the Apache Incubator PMC.
-
-Incubation is required of all newly accepted projects until a further review
-indicates that the infrastructure, communications, and decision making process
-have stabilized in a manner consistent with other successful ASF projects.
-
-While incubation status is not necessarily a reflection of the completeness
-or stability of the code, it does indicate that the project has yet to be
-fully endorsed by the ASF.

NOTICE

@@ -1,4 +1,4 @@
-Apache HertzBeat (incubating)
+Apache HertzBeat
 Copyright 2024-2025 The Apache Software Foundation
 
 This product includes software developed at

README.md

@@ -28,7 +28,7 @@
 
 ## 🎡 <font color="green">Introduction</font>
 
-[Apache HertzBeat](https://github.com/apache/hertzbeat) (incubating) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.   
+[Apache HertzBeat](https://github.com/apache/hertzbeat) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.   
 
 ### Features
 

README_CN.md

@@ -28,7 +28,7 @@
 
 ## 🎡 <font color="green">介绍</font>
 
-[Apache HertzBeat](https://github.com/apache/hertzbeat) （incubating）是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。     
+[Apache HertzBeat](https://github.com/apache/hertzbeat) 是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。     
 
 ### 特点
 

hertzbeat-manager/pom.xml

@@ -293,6 +293,21 @@
                                     </descriptors>
                                 </configuration>
                             </execution>
+                            <execution>
+                                <id>make-docker-zip</id>
+                                <!--Bound maven operation-->
+                                <phase>package</phase>
+                                <!--Run once-->
+                                <goals>
+                                    <goal>single</goal>
+                                </goals>
+                                <configuration>
+                                    <outputDirectory>../dist</outputDirectory>
+                                    <descriptors>
+                                        <descriptor>../script/assembly/server/assembly-docker.xml</descriptor>
+                                    </descriptors>
+                                </configuration>
+                            </execution>
                             <execution>
                                 <id>make-docker-compose-script</id>
                                 <!--Bound maven operation-->

hertzbeat-manager/src/main/resources/db/migration/h2/V173__update_column.sql

@@ -0,0 +1,21 @@
+-- Licensed to the Apache Software Foundation (ASF) under one
+-- or more contributor license agreements.  See the NOTICE file
+-- distributed with this work for additional information
+-- regarding copyright ownership.  The ASF licenses this file
+-- to you under the Apache License, Version 2.0 (the
+-- "License"); you may not use this file except in compliance
+-- with the License.  You may obtain a copy of the License at
+--
+--   http://www.apache.org/licenses/LICENSE-2.0
+--
+-- Unless required by applicable law or agreed to in writing,
+-- software distributed under the License is distributed on an
+-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+-- KIND, either express or implied.  See the License for the
+-- specific language governing permissions and limitations
+-- under the License.
+
+-- ensure every sql can rerun without error
+
+-- Modify message column to TEXT (H2 TEXT is equivalent to CLOB)
+ALTER TABLE HZB_STATUS_PAGE_INCIDENT_CONTENT ALTER COLUMN message CLOB;

hertzbeat-manager/src/main/resources/db/migration/mysql/V173__update_column.sql

@@ -0,0 +1,52 @@
+-- Licensed to the Apache Software Foundation (ASF) under one
+-- or more contributor license agreements.  See the NOTICE file
+-- distributed with this work for additional information
+-- regarding copyright ownership.  The ASF licenses this file
+-- to you under the Apache License, Version 2.0 (the
+-- "License"); you may not use this file except in compliance
+-- with the License.  You may obtain a copy of the License at
+--
+--   http://www.apache.org/licenses/LICENSE-2.0
+--
+-- Unless required by applicable law or agreed to in writing,
+-- software distributed under the License is distributed on an
+-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+-- KIND, either express or implied.  See the License for the
+-- specific language governing permissions and limitations
+-- under the License.
+
+-- ensure every sql can rerun without error
+
+-- Modify hzb_status_page_incident_content table columns to TEXT type to resolve MySQL row size limit issue
+
+DELIMITER //
+CREATE PROCEDURE ModifyStatusIncidentContentColumns()
+BEGIN
+    DECLARE table_exists INT;
+    DECLARE col_exists INT;
+
+    -- Check if the table exists
+    SELECT COUNT(*) INTO table_exists 
+    FROM INFORMATION_SCHEMA.TABLES 
+    WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'HZB_STATUS_PAGE_INCIDENT_CONTENT';
+    
+    IF table_exists = 1 THEN
+        -- Check and modify message column to TEXT
+        SELECT COUNT(*) INTO col_exists 
+        FROM INFORMATION_SCHEMA.COLUMNS 
+        WHERE TABLE_SCHEMA = DATABASE() 
+        AND TABLE_NAME = 'HZB_STATUS_PAGE_INCIDENT_CONTENT'
+        AND COLUMN_NAME = 'message'
+        AND DATA_TYPE != 'text';
+        
+        IF col_exists = 1 THEN
+            ALTER TABLE HZB_STATUS_PAGE_INCIDENT_CONTENT MODIFY COLUMN message TEXT;
+        END IF;
+    END IF;
+END //
+
+DELIMITER ;
+
+CALL ModifyStatusIncidentContentColumns();
+DROP PROCEDURE IF EXISTS ModifyStatusIncidentContentColumns;
+COMMIT;

hertzbeat-manager/src/main/resources/db/migration/postgresql/V173__update_column.sql

@@ -0,0 +1,23 @@
+-- Licensed to the Apache Software Foundation (ASF) under one
+-- or more contributor license agreements.  See the NOTICE file
+-- distributed with this work for additional information
+-- regarding copyright ownership.  The ASF licenses this file
+-- to you under the Apache License, Version 2.0 (the
+-- "License"); you may not use this file except in compliance
+-- with the License.  You may obtain a copy of the License at
+--
+--   http://www.apache.org/licenses/LICENSE-2.0
+--
+-- Unless required by applicable law or agreed to in writing,
+-- software distributed under the License is distributed on an
+-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+-- KIND, either express or implied.  See the License for the
+-- specific language governing permissions and limitations
+-- under the License.
+
+-- ensure every sql can rerun without error
+
+-- Modify message column to TEXT
+ALTER TABLE HZB_STATUS_PAGE_INCIDENT_CONTENT ALTER COLUMN message TYPE TEXT;
+
+commit;

hertzbeat-manager/src/main/resources/define/app-dolphinscheduler.yml

@@ -21,10 +21,12 @@ app: dolphinscheduler
 name:
   zh-CN: Apache DolphinScheduler
   en-US: Apache DolphinScheduler
+  ja-JP: Apache DolphinScheduler
 # The description and help of this monitoring type
 help:
   zh-CN: Hertzbeat 对 Apache DolphinScheduler (支持v3.3.0或更高版本)通用指标进行测量监控。<br>您可以点击 “<i>新建 Apache DolphinScheduler</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
   en-US: Hertzbeat measures and monitors the general metrics of Apache DolphinScheduler (support v3.3.0 or later).<br>You can click on “<i>Create New Apache DolphinScheduler</i>” to configure it, or select “<i>More Actions</i>” to import an existing configuration.
+  ja-JP: Hertzbeat は Apache DolphinScheduler（v3.3.0+）の一般的なメトリクスを監視します。<br>「<i>新規 Apache DolphinScheduler</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/dolphinscheduler
   en-US: https://hertzbeat.apache.org/docs/help/dolphinscheduler
@@ -36,6 +38,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
@@ -46,6 +49,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
@@ -60,6 +64,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
@@ -74,6 +79,7 @@ params:
     name:
       zh-CN: 启用HTTPS
       en-US: SSL
+      ja-JP: SSL
     # type-param field type(boolean mapping the html h tag)
     type: boolean
     # required-true or false
@@ -83,6 +89,7 @@ params:
     name:
       zh-CN: 令牌
       en-US: Token
+      ja-JP: トークン
     type: text
     limit: 100
     required: true
@@ -93,6 +100,7 @@ metrics:
     i18n:
       zh-CN: Master
       en-US: Master
+      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
@@ -104,76 +112,90 @@ metrics:
         i18n:
           zh-CN: 主机地址
           en-US: Host
+          ja-JP: ホスト
       - field: port
         type: 1
         i18n:
           zh-CN: 端口
           en-US: Port
+          ja-JP: ポート
       - field: serverStatus
         type: 1
         i18n:
           zh-CN: 状态
           en-US: Server Status
+          ja-JP: サーバーステータス
       - field: processId
         type: 1
         i18n:
           zh-CN: 进程 ID
           en-US: Process Id
+          ja-JP: プロセスID
       - field: runningTime
         type: 0
         i18n:
           zh-CN: 运行时间
-          en-US: Running Time
+          en-US: Up Time
+          ja-JP: アップタイム
       - field: cpuUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 处理器使用量
           en-US: CPU Usage
+          ja-JP: CPU使用率
       - field: memoryUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 内存使用量
           en-US: Memory Usage
+          ja-JP: メモリ使用率
       - field: diskUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 磁盘使用量
           en-US: Disk Usage
+          ja-JP: ディスク使用率
       - field: jvmCpuUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: JVM CPU 使用量
           en-US: JVM CPU Usage
+          ja-JP: Java仮想マシンのCPU使用率
       - field: jvmMemoryUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: JVM 内存 使用量
           en-US: JVM Memory Usage
+          ja-JP: Java仮想マシンのメモリ使用率
       - field: jvmHeapUsed
         type: 0
         i18n:
           zh-CN: JVM 已使用的堆内存大小
           en-US: JVM Heap Used
+          ja-JP: Java仮想マシンが使用したヒープメモリのサイズ
       - field: jvmNonHeapUsed
         type: 0
         i18n:
           zh-CN: JVM 已使用的非堆内存大小
           en-US: JVM NonHeap Used
+          ja-JP: Java仮想マシンが使用したノンヒープメモリのサイズ
       - field: jvmHeapMax
         type: 0
         i18n:
           zh-CN: JVM 配置的最大堆内存大小
           en-US: JVM Heap Max
+          ja-JP: Java仮想マシンのヒープメモリの最大値
       - field: jvmNonHeapMax
         type: 0
         i18n:
           zh-CN: JVM 配置的最大非堆内存大小
           en-US: JVM NonHeap Max
+          ja-JP: Java仮想マシンのノンヒープメモリの最大値
     # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
     aliasFields:
       - $.heartBeatInfo
@@ -219,6 +241,7 @@ metrics:
     i18n:
       zh-CN: Worker
       en-US: Worker
+      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: 1
@@ -230,92 +253,109 @@ metrics:
         i18n:
           zh-CN: 主机地址
           en-US: Host
+          ja-JP: ホスト
       - field: port
         type: 1
         i18n:
           zh-CN: 端口
           en-US: Port
+          ja-JP: ポート
       - field: serverStatus
         type: 1
         i18n:
           zh-CN: 状态
           en-US: Server Status
+          ja-JP: サーバーステータス
       - field: processId
         type: 1
         i18n:
           zh-CN: 进程 ID
           en-US: Process Id
+          ja-JP: プロセスID
       - field: runningTime
         type: 0
         i18n:
           zh-CN: 运行时间
-          en-US: Running Time
+          en-US: Up Time
+          ja-JP: アップタイム
       - field: cpuUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 处理器使用量
           en-US: CPU Usage
+          ja-JP: CPU使用率
       - field: memoryUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 内存使用量
           en-US: Memory Usage
+          ja-JP: メモリ使用率
       - field: diskUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 磁盘使用量
           en-US: Disk Usage
+          ja-JP: ディスク使用率
       - field: jvmCpuUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: JVM CPU 使用量
           en-US: JVM CPU Usage
+          ja-JP: Java仮想マシンのCPU使用率
       - field: jvmMemoryUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: JVM 内存 使用量
           en-US: JVM Memory Usage
+          ja-JP: Java仮想マシンのメモリ使用率
       - field: jvmHeapUsed
         type: 0
         i18n:
           zh-CN: JVM 已使用的堆内存大小
           en-US: JVM Heap Used
+          ja-JP: Java仮想マシンが使用したヒープメモリのサイズ
       - field: jvmNonHeapUsed
         type: 0
         i18n:
           zh-CN: JVM 已使用的非堆内存大小
           en-US: JVM NonHeap Used
+          ja-JP: Java仮想マシンが使用したノンヒープメモリのサイズ
       - field: jvmHeapMax
         type: 0
         i18n:
           zh-CN: JVM 配置的最大堆内存大小
           en-US: JVM Heap Max
+          ja-JP: Java仮想マシンのヒープメモリの最大値
       - field: jvmNonHeapMax
         type: 0
         i18n:
           zh-CN: JVM 配置的最大非堆内存大小
           en-US: JVM NonHeap Max
+          ja-JP: Java仮想マシンのノンヒープメモリの最大値
       - field: workerHostWeight
         type: 0
         i18n:
           zh-CN: 权重
           en-US: Weight
+          ja-JP: ウェイト
       - field: threadPoolUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 线程池使用量
-          en-US:  Thread Pool Usage
+          en-US: Thread Pool Usage
+          ja-JP: スレッドプールの使用率
       - field: workerGroup
         type: 1
         i18n:
           zh-CN: Worker 组
           en-US: Worker Group
+          ja-JP: ワーカーグループ
     # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
     aliasFields:
       - $.heartBeatInfo
@@ -364,6 +404,7 @@ metrics:
     i18n:
       zh-CN: Alert Server
       en-US: Alert Server
+      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
@@ -375,76 +416,90 @@ metrics:
         i18n:
           zh-CN: 主机地址
           en-US: Host
+          ja-JP: ホスト
       - field: port
         type: 1
         i18n:
           zh-CN: 端口
           en-US: Port
+          ja-JP: ポート
       - field: serverStatus
         type: 1
         i18n:
           zh-CN: 状态
           en-US: Server Status
+          ja-JP: サーバーステータス
       - field: processId
         type: 1
         i18n:
           zh-CN: 进程 ID
           en-US: Process Id
+          ja-JP: プロセスID
       - field: runningTime
         type: 0
         i18n:
           zh-CN: 运行时间
-          en-US: Running Time
+          en-US: Up Time
+          ja-JP: アップタイム
       - field: cpuUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 处理器使用量
           en-US: CPU Usage
+          ja-JP: CPU使用率
       - field: memoryUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 内存使用量
           en-US: Memory Usage
+          ja-JP: メモリ使用率
       - field: diskUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 磁盘使用量
           en-US: Disk Usage
+          ja-JP: ディスク使用率
       - field: jvmCpuUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: JVM CPU 使用量
           en-US: JVM CPU Usage
+          ja-JP: Java仮想マシンのCPU使用率
       - field: jvmMemoryUsage
         type: 0
         unit: '%'
         i18n:
           zh-CN: JVM 内存 使用量
           en-US: JVM Memory Usage
+          ja-JP: Java仮想マシンのメモリ使用率
       - field: jvmHeapUsed
         type: 0
         i18n:
           zh-CN: JVM 已使用的堆内存大小
           en-US: JVM Heap Used
+          ja-JP: Java仮想マシンが使用したヒープメモリのサイズ
       - field: jvmNonHeapUsed
         type: 0
         i18n:
           zh-CN: JVM 已使用的非堆内存大小
           en-US: JVM NonHeap Used
+          ja-JP: Java仮想マシンが使用したノンヒープメモリのサイズ
       - field: jvmHeapMax
         type: 0
         i18n:
           zh-CN: JVM 配置的最大堆内存大小
           en-US: JVM Heap Max
+          ja-JP: Java仮想マシンのヒープメモリの最大値
       - field: jvmNonHeapMax
         type: 0
         i18n:
           zh-CN: JVM 配置的最大非堆内存大小
           en-US: JVM NonHeap Max
+          ja-JP: Java仮想マシンのノンヒープメモリの最大値
     # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
     aliasFields:
       - $.heartBeatInfo
@@ -490,6 +545,7 @@ metrics:
     i18n:
       zh-CN: 数据库
       en-US: Database
+      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
@@ -501,26 +557,31 @@ metrics:
         i18n:
           zh-CN: 数据库类型
           en-US: Database Type
+          ja-JP: データベースのタイプ
       - field: state
         type: 1
         i18n:
           zh-CN: 状态
           en-US: State
+          ja-JP: 状態
       - field: maxConnections
         type: 0
         i18n:
           zh-CN: 最大连接数
           en-US: Max Connections
+          ja-JP: 最大接続数
       - field: threadsConnections
         type: 0
         i18n:
           zh-CN: 当前连接数
           en-US: Threads Connections
+          ja-JP: 現在接続数
       - field: threadsRunningConnections
         type: 0
         i18n:
           zh-CN: 当前活跃连接数
           en-US: Threads Running Connections
+          ja-JP: 現在のアクティブな接続数
     # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
     aliasFields:
       - dbType

hertzbeat-manager/src/main/resources/define/app-hertzbeat.yml

@@ -62,6 +62,7 @@ params:
     type: number
     required: false
     hide: true
+    defaultValue: 6000
   - field: authType
     name:
       zh-CN: 认证方式
@@ -125,7 +126,7 @@ metrics:
           zh-CN: 状态
           en-US: Status
           ja-JP: ステータス
-      - field: size
+      - field: Size
         type: 0
         i18n:
           zh-CN: 数量
@@ -137,6 +138,18 @@ metrics:
           zh-CN: 可用数量
           en-US: Available Size
           ja-JP: 利用可能なサイズ
+    aliasFields:
+      - $.app
+      - $.category
+      - $.status
+      - $.size
+      - $.availableSize
+    calculates:
+      - app=$.app
+      - category=$.category
+      - status=$.status
+      - Size=$.size
+      - availableSize=$.availableSize
     #  the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk, we use HTTP protocol here
     protocol: http
     # the config content when protocol is http
@@ -228,7 +241,7 @@ metrics:
     priority: 1
     fields:
       - field: state
-        type: 2
+        type: 1
         i18n:
           zh-CN: 状态
           en-US: State

hertzbeat-manager/src/main/resources/define/app-hertzbeat_token.yml

@@ -160,7 +160,7 @@ metrics:
           zh-CN: 状态
           en-US: Status
           ja-JP: ステータス
-      - field: size
+      - field: Size
         type: 0
         i18n:
           zh-CN: 数量
@@ -172,6 +172,18 @@ metrics:
           zh-CN: 可用数量
           en-US: Available Size
           ja-JP: 利用可能なサイズ
+    aliasFields:
+      - $.app
+      - $.category
+      - $.status
+      - $.size
+      - $.availableSize
+    calculates:
+      - app=$.app
+      - category=$.category
+      - status=$.status
+      - Size=$.size
+      - availableSize=$.availableSize
     protocol: http
     http:
       host: ^_^host^_^

hertzbeat-manager/src/main/resources/define/app-postgresql.yml

@@ -651,7 +651,7 @@ metrics:
           zh-CN: 次数
           en-US: Num
           ja-JP: 数量
-      - field: size
+      - field: Size
         type: 0
         unit: B
         i18n:

hertzbeat-manager/src/main/resources/define/app-redis_sentinel.yml

@@ -21,11 +21,13 @@ app: redis_sentinel
 name:
   zh-CN: Redis Sentinel
   en-US: Redis Sentinel
+  ja-JP: Redis Sentinel
 # The description and help of this monitoring type
 help:
-  zh-CN: Hertzbeat 对 Redis Sentinel 的通用指标进行采集监控。<br>您可以点击 “<i>新建 Redis Cluster</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
-  en-US: Hertzbeat monitors Redis Database Sentinel's general performance metrics. You could click the "<i>New Redis Cluster</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
-  zh-TW: Hertzbeat 對 Redis Sentinel 的通用指標進行采集監控。<br>您可以點擊 “<i>新建 Redis Cluster</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
+  zh-CN: Hertzbeat 对 Redis Sentinel 的通用指标进行采集监控。<br>您可以点击 “<i>新建 Redis Sentinel</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
+  en-US: Hertzbeat monitors Redis Database Sentinel's general performance metrics. You could click the "<i>New Redis Sentinel</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
+  zh-TW: Hertzbeat 對 Redis Sentinel 的通用指標進行采集監控。<br>您可以點擊 “<i>新建 Redis Sentinel</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
+  ja-JP: Hertzbeat は Redis Sentinel の一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Redis Sentinel</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/influxdb_promql
   en-US: https://hertzbeat.apache.org/docs/help/influxdb_promql
@@ -37,6 +39,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
@@ -46,6 +49,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
@@ -60,6 +64,7 @@ params:
     name:
       zh-CN: 查询超时时间(ms)
       en-US: Query Timeout(ms)
+      ja-JP: クエリタイムアウト（ｍｓ）
     # type-param field type(most mapping the html input type)
     type: number
     # when type is number, range is required
@@ -74,6 +79,7 @@ params:
     name:
       zh-CN: 用户名
       en-US: Username
+      ja-JP: ユーザー名
     # type-param field type(most mapping the html input type)
     type: text
     # when type is text, use limit to limit string length
@@ -86,6 +92,7 @@ params:
     name:
       zh-CN: 密码
       en-US: Password
+      ja-JP: パスワード
     # type-param field type(most mapping the html input tag)
     type: password
     # required-true or false
@@ -96,6 +103,7 @@ params:
     name:
       zh-CN: 模式
       en-US: Pattern
+      ja-JP: パターン
     # type-param field type(most mapping the html input type)
     type: number
     # required-true or false
@@ -108,6 +116,7 @@ params:
     name:
       zh-CN: 是否启用SSH隧道
       en-US: Enable SSH Tunnel
+      ja-JP: SSHトンネルの有効化
     type: boolean
     required: true
     hide: true
@@ -115,6 +124,7 @@ params:
     name:
       zh-CN: SSH Host
       en-US: SSH Host
+      ja-JP: SSHホスト
     type: text
     required: false
     placeholder: 'When Enable SSH Tunnel'
@@ -123,6 +133,7 @@ params:
     name:
       zh-CN: SSH端口
       en-US: SSH Port
+      ja-JP: SSHポート
     type: number
     range: '[0,65535]'
     required: false
@@ -133,6 +144,7 @@ params:
     name:
       zh-CN: SSH超时时间(ms)
       en-US: SSH Timeout(ms)
+      ja-JP: SSHタイムアウト（ｍｓ）
     type: number
     required: false
     range: '[400,200000]'
@@ -142,6 +154,7 @@ params:
     name:
       zh-CN: SSH用户名
       en-US: SSH Username
+      ja-JP: SSHユーザー名
     type: text
     required: false
     placeholder: 'When Enable SSH tunnel'
@@ -150,6 +163,7 @@ params:
     name:
       zh-CN: SSH密码
       en-US: SSH Password
+      ja-JP: SSHパスワード
     type: password
     required: false
     hide: true
@@ -157,6 +171,7 @@ params:
     name:
       zh-CN: 是否共享SSH连接
       en-US: Share SSH Connection
+      ja-JP: SSH接続共有
     type: boolean
     required: true
     defaultValue: true
@@ -165,6 +180,7 @@ params:
     name:
       zh-CN: SSH私钥
       en-US: SSH PrivateKey
+      ja-JP: SSH秘密鍵
     type: textarea
     placeholder: -----BEGIN RSA PRIVATE KEY-----
     required: false
@@ -173,6 +189,7 @@ params:
     name:
       zh-CN: SSH密钥短语
       en-US: SSH PrivateKey PassPhrase
+      ja-JP: SSH秘密鍵フレーズ
     type: password
     required: false
     hide: true
@@ -181,6 +198,7 @@ metrics:
     i18n:
       zh-CN: 服务器
       en-US: Server
+      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
@@ -191,121 +209,145 @@ metrics:
         i18n:
           zh-CN: 标识
           en-US: Identity
+          ja-JP: ID
       - field: redis_version
         type: 1
         i18n:
           zh-CN: Redis 版本
           en-US: Redis Version
+          ja-JP: Redisバージョン
       - field: redis_git_sha1
         type: 0
         i18n:
           zh-CN: Redis Git SHA1
           en-US: Redis Git SHA1
+          ja-JP: Redis Git SHA1
       - field: redis_git_dirty
         type: 0
         i18n:
           zh-CN: Redis Git Dirty
           en-US: Redis Git Dirty
+          ja-JP: RedisサーバーのGitリポジトリ状態
       - field: redis_build_id
         type: 1
         i18n:
           zh-CN: Redis Build ID
           en-US: Redis Build ID
+          ja-JP: Redis ビルド Id
       - field: redis_mode
         type: 1
         i18n:
           zh-CN: Redis 模式
           en-US: Redis Mode
+          ja-JP: Redis モード
       - field: os
         type: 1
         i18n:
           zh-CN: 操作系统
           en-US: Operating System
+          ja-JP: オーエス
       - field: arch_bits
         type: 0
         i18n:
           zh-CN: 架构位数
           en-US: Architecture Bits
+          ja-JP: アーキテクチャ
       - field: multiplexing_api
         type: 1
         i18n:
           zh-CN: 多路复用 API
           en-US: Multiplexing API
+          ja-JP: IO多重化API
       - field: atomicvar_api
         type: 1
         i18n:
           zh-CN: 原子变量 API
           en-US: Atomicvar API
+          ja-JP: 原子操作API
       - field: gcc_version
         type: 1
         i18n:
           zh-CN: GCC 版本
           en-US: GCC Version
+          ja-JP: GCC バージョン
       - field: process_id
         type: 0
         i18n:
           zh-CN: 进程 ID
           en-US: Process ID
+          ja-JP: プロセスID
       - field: process_supervised
         type: 1
         i18n:
           zh-CN: 进程监控
           en-US: Process Supervised
+          ja-JP: プロセスの監視方法
       - field: run_id
         type: 1
         i18n:
           zh-CN: 运行 ID
           en-US: Run ID
+          ja-JP: Run ID
       - field: tcp_port
         type: 0
         i18n:
           zh-CN: TCP 端口
           en-US: TCP Port
+          ja-JP: TCP ポート
       - field: server_time_usec
         type: 0
         i18n:
           zh-CN: 基于纪元的系统时间
           en-US: Server Time Usec
+          ja-JP: サーバーのタイムスタンプ
       - field: uptime_in_seconds
         type: 0
         i18n:
           zh-CN: 运行时间(秒)
           en-US: Uptime In Seconds
+          ja-JP: アップタイム（秒）
       - field: uptime_in_days
         type: 0
         i18n:
           zh-CN: 运行时间(天)
           en-US: Uptime In Days
+          ja-JP: アップタイム（日）
       - field: hz
         type: 0
         i18n:
           zh-CN: 定时器频率
           en-US: Hz
+          ja-JP: イベントの実行頻度
       - field: configured_hz
         type: 0
         i18n:
           zh-CN: 配置定时器频率
           en-US: Configured Hz
+          ja-JP: 設定されたイベントの実行頻度
       - field: lru_clock
         type: 0
         i18n:
           zh-CN: LRU 时钟
           en-US: LRU Clock
+          ja-JP: LRU クロック
       - field: executable
         type: 1
         i18n:
           zh-CN: 可执行文件
           en-US: Executable
+          ja-JP: サーバーの実行パス
       - field: config_file
         type: 1
         i18n:
           zh-CN: 配置文件
           en-US: Config File
+          ja-JP: 設定されたサーバーの実行ファイル
       - field: io_threads_active
         type: 0
         i18n:
           zh-CN: 活动 IO 线程
           en-US: IO Threads Active
+          ja-JP: 活動中のスレッド数
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: redis
     # the config content when protocol is redis
@@ -336,6 +378,7 @@ metrics:
     i18n:
       zh-CN: 客户端
       en-US: Clients
+      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: 1
@@ -346,41 +389,49 @@ metrics:
         i18n:
           zh-CN: 已连接客户端
           en-US: Connected Clients
+          ja-JP: 現在接続されているクライアントの数
       - field: cluster_connections
         type: 0
         i18n:
           zh-CN: 集群连接
           en-US: Cluster Connections
+          ja-JP: クラスター内の接続数
       - field: maxclients
         type: 0
         i18n:
           zh-CN: 最大客户端数
           en-US: Maxclients
+          ja-JP: 最大クライアント数
       - field: client_recent_max_input_buffer
         type: 0
         i18n:
           zh-CN: 客户端最近最大输入缓冲区
           en-US: Client Recent Max Input Buffer
+          ja-JP: クライアントの最近の最大入力バッファサイズ
       - field: client_recent_max_output_buffer
         type: 0
         i18n:
           zh-CN: 客户端最近最大输出缓冲区
           en-US: Client Recent Max Output Buffer
+          ja-JP: クライアントの最近の最大出力バッファサイズ
       - field: blocked_clients
         type: 0
         i18n:
           zh-CN: 阻塞客户端
           en-US: Blocked Clients
+          ja-JP: ブロックされたクライアント数
       - field: tracking_clients
         type: 0
         i18n:
           zh-CN: 跟踪客户端
           en-US: Tracking Clients
+          ja-JP: トラッキングを使用するクライアントの数
       - field: clients_in_timeout_table
         type: 0
         i18n:
           zh-CN: 超时表中的客户端
           en-US: Clients In Timeout Table
+          ja-JP: タイムアウトテーブル内のクライアント数
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: redis
     # the config content when protocol is redis
@@ -411,6 +462,7 @@ metrics:
     i18n:
       zh-CN: 统计
       en-US: Stats
+      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
@@ -421,191 +473,229 @@ metrics:
         i18n:
           zh-CN: 收到总连接数
           en-US: Total Connections Received
+          ja-JP: サーバーの起動後に受信された合計接続数
       - field: total_commands_processed
         type: 0
         i18n:
           zh-CN: 处理总命令数
           en-US: Total Commands Processed
+          ja-JP: サーバーの起動後に処理した総コマンド数
       - field: instantaneous_ops_per_sec
         type: 0
         i18n:
           zh-CN: 瞬时每秒操作数
           en-US: Instantaneous Ops Per Sec
+          ja-JP: 1秒当たりに処理されたコマンドの数
       - field: total_net_input_bytes
         type: 0
         i18n:
           zh-CN: 总网络输入字节
           en-US: Total Net Input Bytes
+          ja-JP: 受信されたネットワークバイトの合計数
       - field: total_net_output_bytes
         type: 0
         i18n:
           zh-CN: 总网络输出字节
           en-US: Total Net Output Bytes
+          ja-JP: 転送されたネットワークバイトの合計数
       - field: instantaneous_input_kbps
         type: 0
         i18n:
           zh-CN: 瞬时的输入 kbps
           en-US: Instantaneous Input Kbps
+          ja-JP: 瞬間入力速度(kbps)
       - field: instantaneous_output_kbps
         type: 0
         i18n:
           zh-CN: 瞬时输出 kbps
           en-US: Instantaneous Output Kbps
+          ja-JP: 瞬間出力速度(kbps)
       - field: rejected_connections
         type: 0
         i18n:
           zh-CN: 拒绝连接数
           en-US: Rejected Connections
+          ja-JP: maxclients制限で拒否された接続数
       - field: sync_full
         type: 0
         i18n:
           zh-CN: 全量同步
           en-US: Sync Full
+          ja-JP: 完全同期の回数
       - field: sync_partial_ok
         type: 0
         i18n:
           zh-CN: 部分同步成功
           en-US: Sync Partial Ok
+          ja-JP: 部分同期の回数
       - field: sync_partial_err
         type: 0
         i18n:
           zh-CN: 部分同步失败
           en-US: Sync Partial Err
+          ja-JP: 部分同期のエラー回数
       - field: expired_keys
         type: 0
         i18n:
           zh-CN: 过期键
           en-US: Expired Keys
+          ja-JP: expireコマンドで削除されたキーの数
       - field: expired_stale_perc
         type: 0
         i18n:
           zh-CN: 过期key占比
           en-US: Expired Stale Perc
+          ja-JP: 期限切れのステイルキーの比率
       - field: expired_time_cap_reached_count
         type: 0
         i18n:
           zh-CN: 达到过期时间上限计数
           en-US: Expired Time Cap Reached Count
+          ja-JP: 満了時間の制限に達した回数
       - field: expire_cycle_cpu_milliseconds
         type: 0
         i18n:
           zh-CN: 过期周期 CPU 毫秒
           en-US: Expire Cycle CPU Milliseconds
+          ja-JP: 満了サイクルでかかったCPU時間(ms)
       - field: evicted_keys
         type: 0
         i18n:
           zh-CN: 逐出键
           en-US: Evicted Keys
+          ja-JP: メモリ不足で追放されたキーの数
       - field: keyspace_hits
         type: 0
         i18n:
           zh-CN: 命中键
           en-US: Keyspace Hits
+          ja-JP: キースペースのヒット数
       - field: keyspace_misses
         type: 0
         i18n:
           zh-CN: 未命中键
           en-US: Keyspace Misses
+          ja-JP: キースペースのミス数
       - field: pubsub_channels
         type: 0
         i18n:
           zh-CN: 发布订阅频道
           en-US: Pubsub Channels
+          ja-JP: 有効になっているPub/Subチャネルに接続されているチャネルの数
       - field: pubsub_patterns
         type: 0
         i18n:
           zh-CN: 发布订阅模式
           en-US: Pubsub Patterns
+          ja-JP: 有効になっているPub/Subパターンで接続されたパターンチャネルの数
       - field: latest_fork_usec
         type: 0
         i18n:
           zh-CN: 最新 fork 毫秒
           en-US: Latest Fork Usec
+          ja-JP: 最後のフォーク作業にかかった時間
       - field: total_forks
         type: 0
         i18n:
           zh-CN: 总 fork 数
           en-US: Total Forks
+          ja-JP: 実行されたフォーク作業の合計数
       - field: migrate_cached_sockets
         type: 0
         i18n:
           zh-CN: 迁移缓存套接字
           en-US: Migrate Cached Sockets
+          ja-JP: マイグレーションされたソケット数
       - field: slave_expires_tracked_keys
         type: 0
         i18n:
           zh-CN: 从节点过期跟踪键
           en-US: Slave Expires Tracked Keys
+          ja-JP: スレーブで満了した、トラッキングされたキーの数
       - field: active_defrag_hits
         type: 0
         i18n:
           zh-CN: 活跃碎片整理命中
           en-US: Active Defrag Hits
+          ja-JP: アクティブなデフラグ操作中に発生したヒットの数
       - field: active_defrag_misses
         type: 0
         i18n:
           zh-CN: 活跃碎片整理未命中
           en-US: Active Defrag Misses
+          ja-JP: アクティブなデフラグ操作中に見逃したヒットの数
       - field: active_defrag_key_hits
         type: 0
         i18n:
           zh-CN: 活跃碎片整理键命中
           en-US: Active Defrag Key Hits
+          ja-JP: デフラグ操作でヒットしたキーの数
       - field: active_defrag_key_misses
         type: 0
         i18n:
           zh-CN: 活跃碎片整理键未命中
           en-US: Active Defrag Key Misses
+          ja-JP: デフラグ操作で見逃したキーの数
       - field: tracking_total_keys
         type: 0
         i18n:
           zh-CN: 跟踪键总数
           en-US: Tracking Total Keys
+          ja-JP: トラッキングされたキーの合計数
       - field: tracking_total_items
         type: 0
         i18n:
           zh-CN: 跟踪项总数
           en-US: Tracking Total Items
+          ja-JP: トラッキングされたアイテムの合計数
       - field: tracking_total_prefixes
         type: 0
         i18n:
           zh-CN: 跟踪前缀总数
           en-US: Tracking Total Prefixes
+          ja-JP: トラッキングされたプレフィックスの合計数
       - field: unexpected_error_replies
         type: 0
         i18n:
           zh-CN: 意外错误回复
           en-US: Unexpected Error Replies
+          ja-JP: 予期しないエラー応答の数
       - field: total_error_replies
         type: 0
         i18n:
           zh-CN: 总错误回复
           en-US: Total Error Replies
+          ja-JP: 発生したエラーの合計応答の数
       - field: dump_payload_sanitizations
         type: 0
         i18n:
           zh-CN: 转储有效负载深度完整性验证的总数
           en-US: Dump Payload Sanitizations
+          ja-JP: ダンプペイロードで実行された整理作業の数
       - field: total_reads_processed
         type: 0
         i18n:
           zh-CN: 总读取处理
           en-US: Total Reads Processed
+          ja-JP: 処理された読み取り作業の合計数
       - field: total_writes_processed
         type: 0
         i18n:
           zh-CN: 总写入处理
           en-US: Total Writes Processed
+          ja-JP: 処理された書き込み作業の合計数
       - field: io_threaded_reads_processed
         type: 0
         i18n:
           zh-CN: IO 线程读取处理
           en-US: Io Threaded Reads Processed
+          ja-JP: I/Oスレッドで処理された読み取り作業の数
       - field: io_threaded_writes_processed
         type: 0
         i18n:
           zh-CN: IO 线程写入处理
           en-US: Io Threaded Writes Processed
+          ja-JP: I/Oスレッドで処理された書き込み作業の数
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: redis
     # the config content when protocol is redis
@@ -636,6 +726,7 @@ metrics:
     i18n:
       zh-CN: CPU
       en-US: CPU
+      ja-JP: CPU情報
     # 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: 3
@@ -646,31 +737,37 @@ metrics:
         i18n:
           zh-CN: 系统已使用 CPU
           en-US: Sys CPU Used
+          ja-JP: システムモードで使用されたCPUの合計時間
       - field: used_cpu_user
         type: 0
         i18n:
           zh-CN: 用户已使用 CPU
           en-US: User CPU Used
+          ja-JP: ユーザーモードで使用されたCPUの合計時間
       - field: used_cpu_sys_children
         type: 0
         i18n:
           zh-CN: Sys 子进程已使用 CPU
           en-US: Sys Children CPU Used
+          ja-JP: 子プロセスがシステムモードで使用したCPU時間
       - field: used_cpu_user_children
         type: 0
         i18n:
           zh-CN: 用户子进程已使用 CPU
           en-US: User Children CPU Used
+          ja-JP: 子プロセスがユーザーモードで使用したCPU時間
       - field: used_cpu_sys_main_thread
         type: 0
         i18n:
           zh-CN: 系统主线程已使用 CPU
           en-US: Sys Main Thread CPU Used
+          ja-JP: プロセスがシステムモードで使用したCPU時間
       - field: used_cpu_user_main_thread
         type: 0
         i18n:
           zh-CN: 用户主线程已使用 CPU
           en-US: User Main Thread CPU Used
+          ja-JP: プロセスがユーザーモードで使用したCPU時間
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: redis
     # the config content when protocol is redis
@@ -701,6 +798,7 @@ metrics:
     i18n:
       zh-CN: 哨兵
       en-US: Sentinel
+      ja-JP: Sentinel
     # 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: 4
@@ -711,26 +809,31 @@ metrics:
         i18n:
           zh-CN: 主节点
           en-US: Masters
+          ja-JP: マスターノード
       - field: sentinel_tilt
         type: 1
         i18n:
           zh-CN: 倾斜
           en-US: Tilt
+          ja-JP: マスターをダウン状態としてマークする前の待機時間
       - field: sentinel_running_scripts
         type: 1
         i18n:
           zh-CN: 运行脚本
           en-US: Running Scripts
+          ja-JP: 実行するスクリプト
       - field: sentinel_scripts_queue_length
         type: 1
         i18n:
           zh-CN: 脚本队列长度
           en-US: Scripts Queue Length
+          ja-JP: 実行するスクリプトのキューの長さ
       - field: sentinel_simulate_failure_flags
         type: 1
         i18n:
           zh-CN: 模拟失败标志
           en-US: Simulate Failure Flags
+          ja-JP: フェイルオーバー機能をテスト用のフラグ
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: redis
     # the config content when protocol is redis

hertzbeat-manager/src/main/resources/define/app-rockylinux.yml

@@ -21,11 +21,13 @@ app: rockylinux
 name:
   zh-CN: Rocky Linux
   en-US: Rocky Linux
+  ja-JP: Rocky Linux
 # The description and help of this monitoring type
 help:
   zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 Rocky 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 Rocky</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
   en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors Rocky operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New Rocky</i>" and config host port and other related params to add, auth support password or secretKey. 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-ssh'> SSH 协议</a> 對 Rocky 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 Rocky</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Rockyオーエスの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Rocky</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/rockylinux
   en-US: https://hertzbeat.apache.org/docs/help/rockylinux
@@ -37,6 +39,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
@@ -47,6 +50,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
@@ -61,6 +65,7 @@ params:
     name:
       zh-CN: 超时时间(ms)
       en-US: Timeout(ms)
+      ja-JP: タイムアウト（ｍｓ）
     # type-param field type(most mapping the html input type)
     type: number
     # when type is number, range is required
@@ -75,6 +80,7 @@ params:
     name:
       zh-CN: 复用连接
       en-US: Reuse Connection
+      ja-JP: 接続再利用
     # type-param field type(most mapping the html input type)
     type: boolean
     # required-true or false
@@ -86,6 +92,7 @@ params:
     name:
       zh-CN: 使用代理
       en-US: Use Proxy Connection
+      ja-JP: プロキシ接続利用
     # type-param field type(most mapping the html input type)
     type: boolean
     # required-true or false
@@ -97,6 +104,7 @@ params:
     name:
       zh-CN: 用户名
       en-US: Username
+      ja-JP: ユーザー名
     # type-param field type(most mapping the html input type)
     type: text
     # when type is text, use limit to limit string length
@@ -109,6 +117,7 @@ params:
     name:
       zh-CN: 密码
       en-US: Password
+      ja-JP: パスワード
     # type-param field type(most mapping the html input tag)
     type: password
     # required-true or false
@@ -119,6 +128,7 @@ params:
     name:
       zh-CN: 私钥
       en-US: PrivateKey
+      ja-JP: 秘密鍵
     # type-param field type(most mapping the html input type)
     type: textarea
     placeholder: -----BEGIN RSA PRIVATE KEY-----
@@ -132,6 +142,7 @@ params:
     name:
       zh-CN: 密钥短语
       en-US: PrivateKey PassPhrase
+      ja-JP: 秘密鍵フレーズ
     # type-param field type(most mapping the html input type)
     type: password
     # required-true or false
@@ -144,6 +155,7 @@ params:
     name:
       zh-CN: 代理主机
       en-US: Proxy Host
+      ja-JP: プロキシホスト
     # type-param field type(most mapping the html input type)
     type: text
     # required-true or false
@@ -155,6 +167,7 @@ params:
     name:
       zh-CN: 代理端口
       en-US: Proxy Port
+      ja-JP: プロキシポート
     # type-param field type(most mapping the html input type)
     type: number
     # when type is number, range is required
@@ -171,6 +184,7 @@ params:
     name:
       zh-CN: 代理用户名
       en-US: Proxy Username
+      ja-JP: プロキシユーザー名
     # type-param field type(most mapping the html input type)
     type: text
     # when type is text, use limit to limit string length
@@ -185,6 +199,7 @@ params:
     name:
       zh-CN: 代理密码
       en-US: Proxy Password
+      ja-JP: プロキシパスワード
     # type-param field type(most mapping the html input tag)
     type: password
     # required-true or false
@@ -197,6 +212,7 @@ params:
     name:
       zh-CN: 代理主机私钥
       en-US: proxyPrivateKey
+      ja-JP: プロキシ秘密鍵
     # type-param field type(most mapping the html input type)
     type: textarea
     placeholder: -----BEGIN RSA PRIVATE KEY-----
@@ -211,6 +227,7 @@ metrics:
     i18n:
       zh-CN: 系统基本信息
       en-US: Basic Info
+      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
@@ -223,16 +240,19 @@ metrics:
         i18n:
           zh-CN: 主机名称
           en-US: Host Name
+          ja-JP: ホスト名
       - field: version
         type: 1
         i18n:
           zh-CN: 操作系统版本
           en-US: System Version
+          ja-JP: システムバージョン
       - field: uptime
         type: 1
         i18n:
           zh-CN: 启动时间
           en-US: Uptime
+          ja-JP: アップタイム
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: ssh
     # the config content when protocol is ssh
@@ -272,6 +292,7 @@ metrics:
     i18n:
       zh-CN: CPU 信息
       en-US: CPU Info
+      ja-JP: CPU情報
     priority: 1
     fields:
       - field: info
@@ -279,32 +300,38 @@ metrics:
         i18n:
           zh-CN: 型号
           en-US: Info
+          ja-JP: バージョン
       - field: cores
         type: 1
         i18n:
           zh-CN: 核数
           en-US: Cores
+          ja-JP: コア数
       - field: interrupt
         type: 0
         i18n:
           zh-CN: 中断数
           en-US: Interrupt
+          ja-JP: 割り込み数
       - field: load
         type: 1
         i18n:
           zh-CN: 负载
           en-US: Load
+          ja-JP: ロード
       - field: context_switch
         type: 0
         i18n:
           zh-CN: 上下文切换
           en-US: Context Switch
+          ja-JP: コンテキストスイッチ
       - field: usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 使用率
           en-US: Usage
+          ja-JP: 使用率
     # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
     aliasFields:
       - info
@@ -351,6 +378,7 @@ metrics:
     i18n:
       zh-CN: 内存信息
       en-US: Memory Info
+      ja-JP: メモリ情報
     priority: 2
     fields:
       - field: total
@@ -359,36 +387,42 @@ metrics:
         i18n:
           zh-CN: 总内存容量
           en-US: Total Memory
+          ja-JP: メモリ容量
       - field: used
         type: 0
         unit: Mb
         i18n:
           zh-CN: 用户程序内存量
           en-US: User Program Memory
+          ja-JP: ユーザープログラムメモリ
       - field: free
         type: 0
         unit: Mb
         i18n:
           zh-CN: 空闲内存容量
           en-US: Free Memory
+          ja-JP: 空きメモリ
       - field: buff_cache
         type: 0
         unit: Mb
         i18n:
           zh-CN: 缓存占用内存
           en-US: Buff Cache Memory
+          ja-JP: バッファメモリ
       - field: available
         type: 0
         unit: Mb
         i18n:
           zh-CN: 剩余可用内存
           en-US: Available Memory
+          ja-JP: 使用可能のメモリ
       - field: usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 内存使用率
           en-US: Memory Usage
+          ja-JP: メモリ使用率
     aliasFields:
       - total
       - used
@@ -431,6 +465,7 @@ metrics:
     i18n:
       zh-CN: 磁盘信息
       en-US: Disk Info
+      ja-JP: ディスク情報
     priority: 3
     fields:
       - field: disk_num
@@ -438,27 +473,32 @@ metrics:
         i18n:
           zh-CN: 磁盘总数
           en-US: Disk Num
+          ja-JP: ディスク番号
       - field: partition_num
         type: 1
         i18n:
           zh-CN: 分区总数
           en-US: Partition Num
+          ja-JP: パーティション
       - field: block_write
         type: 0
         i18n:
           zh-CN: 写磁盘块数
           en-US: Block Write
+          ja-JP: 書き込みディスクブロック数
       - field: block_read
         type: 0
         i18n:
           zh-CN: 读磁盘块数
           en-US: Block Read
+          ja-JP: 読み取りブロック数
       - field: write_rate
         type: 0
         unit: iops
         i18n:
           zh-CN: 磁盘写速率
           en-US: Write Rate
+          ja-JP: ディスク書き込み速度
     protocol: ssh
     ssh:
       host: ^_^host^_^
@@ -488,6 +528,7 @@ metrics:
     i18n:
       zh-CN: 网卡信息
       en-US: Interface Info
+      ja-JP: ネットワークカード情報
     priority: 4
     fields:
       - field: interface_name
@@ -496,18 +537,21 @@ metrics:
         i18n:
           zh-CN: 网卡名称
           en-US: Interface Name
+          ja-JP: ネットワークカード名
       - field: receive_bytes
         type: 0
         unit: Mb
         i18n:
           zh-CN: 入站数据流量
           en-US: Receive Bytes
+          ja-JP: 受信されたバイト数
       - field: transmit_bytes
         type: 0
         unit: Mb
         i18n:
           zh-CN: 出站数据流量
           en-US: Transmit Bytes
+          ja-JP: 転送されたバイト数
     units:
       - receive_bytes=B->MB
       - transmit_bytes=B->MB
@@ -540,6 +584,7 @@ metrics:
     i18n:
       zh-CN: 文件系统
       en-US: Disk Free
+      ja-JP: ファイルシステム
     priority: 5
     fields:
       - field: filesystem
@@ -547,30 +592,35 @@ metrics:
         i18n:
           zh-CN: 文件系统
           en-US: Filesystem
+          ja-JP: ファイルシステム
       - field: used
         type: 0
         unit: Mb
         i18n:
           zh-CN: 已使用量
           en-US: Used
+          ja-JP: 使用済み
       - field: available
         type: 0
         unit: Mb
         i18n:
           zh-CN: 可用量
           en-US: Available
+          ja-JP: 使用可能
       - field: usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 使用率
           en-US: Usage
+          ja-JP: 使用率
       - field: mounted
         type: 1
         label: true
         i18n:
           zh-CN: 挂载点
           en-US: Mounted
+          ja-JP: マウント
     protocol: ssh
     ssh:
       host: ^_^host^_^
@@ -600,6 +650,7 @@ metrics:
     i18n:
       zh-CN: Top10 CPU 进程
       en-US: Top10 CPU Process
+      ja-JP: トップ10 CPUプロセス
     priority: 6
     fields:
       - field: pid
@@ -608,23 +659,27 @@ metrics:
         i18n:
           zh-CN: 进程ID
           en-US: PID
+          ja-JP: プロセスID
       - field: cpu_usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: CPU占用率
           en-US: CPU Usage
+          ja-JP: CPU使用率
       - field: mem_usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 内存占用率
           en-US: Memory Usage
+          ja-JP: メモリ使用率
       - field: command
         type: 1
         i18n:
           zh-CN: 执行命令
           en-US: Command
+          ja-JP: コマンド
     protocol: ssh
     ssh:
       host: ^_^host^_^
@@ -654,6 +709,7 @@ metrics:
     i18n:
       zh-CN: Top10 内存进程
       en-US: Top10 Memory Process
+      ja-JP: トップ10 メモリプロセス
     priority: 7
     fields:
       - field: pid
@@ -662,23 +718,27 @@ metrics:
         i18n:
           zh-CN: 进程ID
           en-US: PID
+          ja-JP: プロセスID
       - field: mem_usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: 内存占用率
           en-US: Memory Usage
+          ja-JP: メモリ使用率
       - field: cpu_usage
         type: 0
         unit: '%'
         i18n:
           zh-CN: CPU占用率
           en-US: CPU Usage
+          ja-JP: CPU使用率
       - field: command
         type: 1
         i18n:
           zh-CN: 执行命令
           en-US: Command
+          ja-JP: コマンド
     protocol: ssh
     ssh:
       host: ^_^host^_^

hertzbeat-manager/src/main/resources/define/app-seatunnel.yml

@@ -21,11 +21,13 @@ app: seatunnel
 name:
   zh-CN: Seatunnel
   en-US: Seatunnel
+  ja-JP: Seatunnel
 # The description and help of this monitoring type
 help:
   zh-CN: Hertzbeat 对 Seatunnel 通用指标进行测量监控。<br>您可以点击 “<i>新建 Seatunnel</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
   en-US: Hertzbeat measures and monitors the general metrics of Seatunnel.<br>You can click on “<i>Create New Seatunnel</i>” to configure it, or select “<i>More Actions</i>” to import an existing configuration.
   zh-TW: Hertzbeat 對 Seatunnel 通用指標進行測量監控。<br>您可以點擊 “<i>新建 Seatunnel</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
+  ja-JP: Hertzbeat は Seatunnelの一般的なメトリクスを監視します。<br>「<i>新規 Seatunnel</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/seatunnel
   en-US: https://hertzbeat.apache.org/docs/help/seatunnel
@@ -37,6 +39,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
@@ -47,6 +50,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
@@ -61,6 +65,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
@@ -75,6 +80,7 @@ params:
     name:
       zh-CN: 启用HTTPS
       en-US: SSL
+      ja-JP: SSL
     # type-param field type(boolean mapping the html h tag)
     type: boolean
     # required-true or false
@@ -86,6 +92,7 @@ metrics:
     i18n:
       zh-CN: 集群概览
       en-US: Cluster Overview
+      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
@@ -97,48 +104,56 @@ metrics:
         i18n:
           zh-CN: 项目版本
           en-US: Project Version
+          ja-JP: プロジェクトバージョン
       - field: gitCommitAbbrev
         type: 1
         i18n:
           zh-CN: Git提交编号
           en-US: Git Commit Abbrev
+          ja-JP: GitコミットID
       - field: totalSlot
         type: 0
         i18n:
           zh-CN: 总槽位数
           en-US: Total Slot
+          ja-JP: スロット数
       - field: unassignedSlot
         type: 0
         i18n:
           zh-CN: 未分配槽位数
           en-US: Unassigned Slot
+          ja-JP: 未割り当てのスロット数
       - field: runningJobs
         type: 0
         i18n:
           zh-CN: 运行中任务数
           en-US: Running Jobs
+          ja-JP: 実行中のタスク数
       - field: finishedJobs
         type: 0
         i18n:
           zh-CN: 已完成任务数
           en-US: Finished Jobs
+          ja-JP: 完了したタスク数
       - field: failedJobs
         type: 0
         i18n:
           zh-CN: 失败任务数
           en-US: Failed Jobs
+          ja-JP: 失敗したタスク数
       - field: cancelledJobs
         type: 0
         i18n:
           zh-CN: 取消任务数
           en-US: Cancelled Jobs
+          ja-JP: キャンセルされたタスク数
       - field: workers
         type: 0
         i18n:
           zh-CN: Worker数
           en-US: Workers
+          ja-JP: ワーカー数
     # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
-    # (可选)监控指标别名, 做为中间字段与采集数据字段和指标字段映射转换
     aliasFields:
       - projectVersion
       - gitCommitAbbrev
@@ -182,6 +197,7 @@ metrics:
     i18n:
       zh-CN: 线程信息
       en-US: Thread Info
+      ja-JP: スレッド情報
     priority: 1
     fields:
       - field: threadName
@@ -190,21 +206,25 @@ metrics:
         i18n:
           zh-CN: 线程名称
           en-US: Thread Name
+          ja-JP: スレッド名
       - field: threadId
         type: 0
         i18n:
           zh-CN: 线程ID
           en-US: Thread ID
+          ja-JP: スレッドID
       - field: threadState
         type: 1
         i18n:
           zh-CN: 线程状态
           en-US: Thread State
+          ja-JP: スレッド状態
       - field: stackTrace
         type: 1
         i18n:
           zh-CN: 堆栈信息
           en-US: Stack Trace
+          ja-JP: スタックトレース
     protocol: http
     http:
       host: ^_^host^_^
@@ -227,6 +247,7 @@ metrics:
     i18n:
       zh-CN: 节点监控
       en-US: Node Monitor
+      ja-JP: ノード情報
     priority: 1
     fields:
       - field: isMaster
@@ -235,241 +256,289 @@ metrics:
         i18n:
           zh-CN: 是否主节点
           en-US: Is Master
+          ja-JP: マスターノード
       - field: host
         type: 1
         i18n:
           zh-CN: IP地址
           en-US: IP Address
+          ja-JP: IPアドレス
       - field: port
         type: 1
         i18n:
           zh-CN: 端口
           en-US: Port
+          ja-JP: ポート
       - field: processors
         type: 1
         i18n:
           zh-CN: 处理器数
           en-US: Processors
+          ja-JP: プロセッサ数
       - field: physical.memory.total
         type: 1
         i18n:
           zh-CN: 物理内存总量
           en-US: Physical Memory Total
+          ja-JP: 物理メモリ容量
       - field: physical.memory.free
         type: 1
         i18n:
           zh-CN: 物理内存可用
           en-US: Physical Memory Free
+          ja-JP: 利用可能な物理メモリ
       - field: swap.space.total
         type: 1
         i18n:
           zh-CN: 交换空间总量
           en-US: Swap Space Total
+          ja-JP: スワップ領域容量
       - field: swap.space.free
         type: 1
         i18n:
           zh-CN: 交换空间可用
           en-US: Swap Space Free
+          ja-JP: 利用可能なスワップ領域
       - field: heap.memory.used
         type: 1
         i18n:
           zh-CN: 堆内存已用
           en-US: Heap Memory Used
+          ja-JP: 使用したヒープメモリ
       - field: heap.memory.free
         type: 1
         i18n:
           zh-CN: 堆内存可用
           en-US: Heap Memory Free
+          ja-JP: 利用可能なヒープメモリ
       - field: heap.memory.total
         type: 1
         i18n:
           zh-CN: 堆内存总量
           en-US: Heap Memory Total
+          ja-JP: ヒープメモリ容量
       - field: heap.memory.max
         type: 1
         i18n:
           zh-CN: 堆内存最大
           en-US: Heap Memory Max
+          ja-JP: ヒープメモリの最大値
       - field: heap.memory.used/total
         type: 1
         i18n:
           zh-CN: 堆内存使用率
           en-US: Heap Memory Used/Total
+          ja-JP: ヒープメモリの使用率
       - field: heap.memory.used/max
         type: 1
         i18n:
           zh-CN: 堆内存使用率最大
           en-US: Heap Memory Used/Max
+          ja-JP: ヒープメモリの使用率の最大値
       - field: minor.gc.count
         type: 1
         i18n:
           zh-CN: 小垃圾回收次数
           en-US: Minor GC Count
+          ja-JP: 若い領域GC回数
       - field: minor.gc.time
         type: 1
         i18n:
           zh-CN: 小垃圾回收时间
           en-US: Minor GC Time
+          ja-JP: 若い領域GC時間
       - field: major.gc.count
         type: 1
         i18n:
           zh-CN: 大垃圾回收次数
           en-US: Major GC Count
+          ja-JP: 古い領域GC回数
       - field: major.gc.time
         type: 1
         i18n:
           zh-CN: 大垃圾回收时间
           en-US: Major GC Time
+          ja-JP: 古い領域GC時間
       - field: load.process
         type: 1
         i18n:
           zh-CN: 进程负载
           en-US: Load Process
+          ja-JP: プロセスロード
       - field: load.system
         type: 1
         i18n:
           zh-CN: 系统负载
           en-US: Load System
+          ja-JP: システムロード
       - field: load.systemAverage
         type: 1
         i18n:
           zh-CN: 系统平均负载
           en-US: Load System Average
+          ja-JP: システムの平均ロード
       - field: thread.count
         type: 1
         i18n:
           zh-CN: 线程数
           en-US: Thread Count
+          ja-JP: スレッド数
       - field: thread.peakCount
         type: 1
         i18n:
           zh-CN: 线程峰值
           en-US: Thread Peak Count
+          ja-JP: 最大スレッド数
       - field: cluster.timeDiff
         type: 1
         i18n:
           zh-CN: 集群时间差
           en-US: Cluster Time Diff
+          ja-JP: クラスター間の時差
       - field: event.q.size
         type: 1
         i18n:
           zh-CN: 事件队列大小
           en-US: Event Queue Size
+          ja-JP: イベントキューのサイズ
       - field: executor.q.async.size
         type: 1
         i18n:
           zh-CN: 异步执行队列大小
           en-US: Executor Queue Async Size
+          ja-JP: 非同期実行キューのサイズ
       - field: executor.q.client.size
         type: 1
         i18n:
           zh-CN: 客户端执行队列大小
           en-US: Executor Queue Client Size
+          ja-JP: クライアントが実行するキューのサイズ
       - field: executor.q.client.query.size
         type: 1
         i18n:
           zh-CN: 客户端查询队列大小
           en-US: Executor Queue Client Query Size
+          ja-JP: クライアントが実行するクエリキューのサイズ
       - field: executor.q.client.blocking.size
         type: 1
         i18n:
           zh-CN: 客户端阻塞队列大小
           en-US: Executor Queue Client Blocking Size
+          ja-JP: クライアントが実行するブロッキングキューのサイズ
       - field: executor.q.query.size
         type: 1
         i18n:
           zh-CN: 查询队列大小
           en-US: Executor Queue Query Size
+          ja-JP: クエリキューのサイズ
       - field: executor.q.scheduled.size
         type: 1
         i18n:
           zh-CN: 定时执行队列大小
           en-US: Executor Queue Scheduled Size
+          ja-JP: スケジュールされたキューのサイズ
       - field: executor.q.io.size
         type: 1
         i18n:
           zh-CN: IO队列大小
           en-US: Executor Queue IO Size
+          ja-JP: IOキューのサイズ
       - field: executor.q.system.size
         type: 1
         i18n:
           zh-CN: 系统执行队列大小
           en-US: Executor Queue System Size
+          ja-JP: システムキューのサイズ
       - field: executor.q.operations.size
         type: 1
         i18n:
           zh-CN: 操作队列大小
           en-US: Executor Queue Operations Size
+          ja-JP: 操作キューのサイズ
       - field: executor.q.priorityOperation.size
         type: 1
         i18n:
           zh-CN: 优先操作队列大小
           en-US: Executor Queue Priority Operation Size
+          ja-JP: 優先操作キューのサイズ
       - field: operations.completed.count
         type: 1
         i18n:
           zh-CN: 完成操作次数
           en-US: Operations Completed Count
+          ja-JP: 操作完了の回数
       - field: executor.q.mapLoad.size
         type: 1
         i18n:
           zh-CN: 映射加载队列大小
           en-US: Executor Queue Map Load Size
+          ja-JP: Mapからロードするキューのサイズ
       - field: executor.q.mapLoadAllKeys.size
         type: 1
         i18n:
           zh-CN: 映射加载所有键大小
           en-US: Executor Queue Map Load All Keys Size
+          ja-JP: Mapから全てのキーをロードするキューのサイズ
       - field: executor.q.cluster.size
         type: 1
         i18n:
           zh-CN: 集群执行队列大小
           en-US: Executor Queue Cluster Size
+          ja-JP: クラスターキューのサイズ
       - field: executor.q.response.size
         type: 1
         i18n:
           zh-CN: 响应队列大小
           en-US: Executor Queue Response Size
+          ja-JP: 応答キューのサイズ
       - field: operations.running.count
         type: 1
         i18n:
           zh-CN: 正在运行的操作数量
           en-US: Operations Running Count
+          ja-JP: 実行中のキューのサイズ
       - field: operations.pending.invocations.percentage
         type: 1
         i18n:
           zh-CN: 待处理调用百分比
           en-US: Operations Pending Invocations Percentage
+          ja-JP: 待機中の操作の比率
       - field: operations.pending.invocations.count
         type: 1
         i18n:
           zh-CN: 待处理调用数量
           en-US: Operations Pending Invocations Count
+          ja-JP: 待機中の操作数
       - field: proxy.count
         type: 1
         i18n:
           zh-CN: 代理数量
           en-US: Proxy Count
+          ja-JP: プロキシ数
       - field: clientEndpoint.count
         type: 1
         i18n:
           zh-CN: 客户端端点数量
           en-US: Client Endpoint Count
+          ja-JP: クライアントエンドポイントの数
       - field: connection.active.count
         type: 1
         i18n:
           zh-CN: 活动连接数
           en-US: Connection Active Count
+          ja-JP: アクティブな接続数
       - field: client.connection.count
         type: 1
         i18n:
           zh-CN: 客户端连接数
           en-US: Client Connection Count
+          ja-JP: クライアント接続数
       - field: connection.count
         type: 1
         i18n:
           zh-CN: 总连接数
           en-US: Connection Count
+          ja-JP: 接続総数
     protocol: http
     http:
       host: ^_^host^_^

hertzbeat-manager/src/main/resources/define/app-spring_gateway.yml

@@ -19,15 +19,15 @@ category: mid
 app: spring_gateway
 # The monitoring i18n name
 name:
-  zh-CN: SpringGateway
-  en-US: SpringGateway
-  ja-JP: SpringGateway
+  zh-CN: Spring Cloud Gateway
+  en-US: Spring Cloud Gateway
+  ja-JP: Spring Cloud Gateway
 # The description and help of this monitoring type
 help:
-  zh-CN: HertzBeat 对 <a class='help_module_content' href='https://www.tutorialspoint.com/spring_boot/spring_boot_actuator.htm'> SpringBoot Actuator </a> 暴露的通用性能指标(globalfilters、routefilters、refresh、routes)进行采集监控。<span class='help_module_span'>注意⚠️：如果要监控 SpringGateway 中的信息，需要您的 SpringGateway 应用集成并开启 SpringBoot Actuator, <a class='help_module_content'  href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>点击查看具体步骤</a>。</span>
-  en-US: HertzBeat collect and monitors SpringGateway through general performance metric that exposed by the SpringBoot Actuator. <br><span class='help_module_span'><br>Note⚠️:You should make sure that your SpringGateway application have already integrated and enabled the SpringBoot Actuator, <a class='help_module_content'  href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>click here to see the specific steps.</a></span>
-  zh-TW: HertzBeat 對 <a class='help_module_content' href='https://www.tutorialspoint.com/spring_boot/spring_boot_actuator.htm'> SpringBoot Actuator </a>暴露的通用性能指標（globalfilters、routefilters、refresh、routes）進行採集監控。<span class='help_module_span'>注意⚠️：如果要監控SpringGateway中的指標，需要您的SpringGateway應用集成並開啟SpringBoot Actuator，<a class='help_module_content' href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>點擊查看具體步驟</a>。</span>
-  ja-JP: HertzBeat は <a class='help_module_content' href='https://www.tutorialspoint.com/spring_boot/spring_boot_actuator.htm'> SpringBoot Actuator </a> の一般的なパフォーマンスのメトリクスを監視します。<span class='help_module_span'>⚠️注意：SpringGateway で SpringBoot Actuatorを有効にする必要があります。<a class='help_module_content' href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>クリックしてガイドを見ます</a>。</span>
+  zh-CN: HertzBeat 对 <a class='help_module_content' href='https://www.tutorialspoint.com/spring_boot/spring_boot_actuator.htm'> SpringBoot Actuator </a> 暴露的通用性能指标(globalfilters、routefilters、refresh、routes)进行采集监控。<span class='help_module_span'>注意⚠️：如果要监控 Spring Cloud Gateway  中的信息，需要您的 Spring Cloud Gateway  应用集成并开启 SpringBoot Actuator, <a class='help_module_content'  href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>点击查看具体步骤</a>。</span>
+  en-US: HertzBeat collect and monitors SpringGateway through general performance metric that exposed by the SpringBoot Actuator. <br><span class='help_module_span'><br>Note⚠️:You should make sure that your Spring Cloud Gateway  application have already integrated and enabled the SpringBoot Actuator, <a class='help_module_content'  href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>click here to see the specific steps.</a></span>
+  zh-TW: HertzBeat 對 <a class='help_module_content' href='https://www.tutorialspoint.com/spring_boot/spring_boot_actuator.htm'> SpringBoot Actuator </a>暴露的通用性能指標（globalfilters、routefilters、refresh、routes）進行採集監控。<span class='help_module_span'>注意⚠️：如果要監控 Spring Cloud Gateway  中的指標，需要您的 Spring Cloud Gateway  應用集成並開啟SpringBoot Actuator，<a class='help_module_content' href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>點擊查看具體步驟</a>。</span>
+  ja-JP: HertzBeat は <a class='help_module_content' href='https://www.tutorialspoint.com/spring_boot/spring_boot_actuator.htm'> SpringBoot Actuator </a> の一般的なパフォーマンスのメトリクスを監視します。<span class='help_module_span'>⚠️注意：Spring Cloud Gateway  で SpringBoot Actuatorを有効にする必要があります。<a class='help_module_content' href='https://cloud.spring.io/spring-cloud-gateway/multi/multi__actuator_api.html'>クリックしてガイドを見ます</a>。</span>
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/spring_gateway
   en-US: https://hertzbeat.apache.org/docs/help/spring_gateway
@@ -284,7 +284,7 @@ metrics:
           en-US: State
           ja-JP: 状態
         label: true
-      - field: size
+      - field: Size
         type: 0
         i18n:
           zh-CN: 数量
@@ -294,7 +294,7 @@ metrics:
       - $.measurements[?(@.statistic == "VALUE")].value
     calculates:
       - state='^o^state^o^'
-      - size=$.measurements[?(@.statistic == "VALUE")].value
+      - Size=$.measurements[?(@.statistic == "VALUE")].value
     protocol: http
     http:
       host: ^_^host^_^

hertzbeat-manager/src/main/resources/define/app-tomcat.yml

@@ -21,11 +21,13 @@ app: tomcat
 name:
   zh-CN: Tomcat应用服务器
   en-US: Tomcat WebServer
+  ja-JP: Tomcat WebServer
 # The description and help of this monitoring type
 help:
   zh-CN: HertzBeat 使用 <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx">JMX 协议</a> 对 Tomcat 的通用性能指标(基础信息，内存池，类加载，线程信息等)进行采集监控。<br>⚠️注意：您需要在 Tomcat 应用中开启 JMX 服务，应用启动时添加 JMX 参数, 可自定义暴露端口,对外IP。<a href="https://hertzbeat.apache.org/zh-cn/docs/help/tomcat">点击查看开启步骤</a>。
   en-US: HertzBeat uses <a href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'>JMX Protocol</a> to monitoring and collect general performance metric of Tomcat. <br>⚠️Note:You need to enable JMX services in Tomcat application, and add the JXM parameters when the application start. You can also customize external IP address and exposed port.<a href='https://hertzbeat.apache.org/docs/help/tomcat'>Click here to view the activation steps.</a>"
   zh-TW: HertzBeat 使用 <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx">JMX 協議</a> 對 Tomcat 的通用性能指標(基礎信息，內存池，類加載，線程信息等)進行采集監控。<br>⚠️注意：您需要在 Tomcat 應用中開啓 JMX 服務，應用啓動時添加 JMX 參數, 可自定義暴露端口,對外IP。<a href="https://hertzbeat.apache.org/zh-cn/docs/help/tomcat">點擊查看開啓步驟</a>。
+  ja-JP: HertzBeat は <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx"> JMXプロトコルを介して</a> Tomcat の一般的なパフォーマンスのメトリクスを監視します。⚠️注意：Tomcat応用 で JMXサービス を有効にする必要があります。<a href="https://hertzbeat.apache.org/docs/help/tomcat">クリックしてガイドを見ます</a>。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/tomcat
   en-US: https://hertzbeat.apache.org/docs/help/tomcat
@@ -37,6 +39,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
@@ -47,6 +50,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
@@ -61,6 +65,7 @@ params:
     name:
       zh-CN: JMX URL
       en-US: JMX URL
+      ja-JP: JMX URL
     # type-param field type(most mapping the html input type)
     type: text
     # required-true or false
@@ -75,6 +80,7 @@ params:
     name:
       zh-CN: 用户名
       en-US: Username
+      ja-JP: ユーザー名
     # type-param field type(most mapping the html input type)
     type: text
     # when type is text, use limit to limit string length
@@ -89,6 +95,7 @@ params:
     name:
       zh-CN: 密码
       en-US: Password
+      ja-JP: パスワード
     # type-param field type(most mapping the html input tag)
     type: password
     # required-true or false
@@ -102,6 +109,7 @@ metrics:
     i18n:
       zh-CN: Tomcat 信息
       en-US: Tomcat Server
+      ja-JP: Tomcatサーバー
     # 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
@@ -113,26 +121,31 @@ metrics:
         i18n:
           zh-CN: 服务信息
           en-US: Server Info
+          ja-JP: サーバー情報
       - field: serverNumber
         type: 1
         i18n:
           zh-CN: 服务版本
           en-US: Server Number
+          ja-JP: サーバーバージョン
       - field: serverBuilt
         type: 1
         i18n:
           zh-CN: Server Built
           en-US: Server Built
+          ja-JP: サーバービルド
       - field: port
         type: 1
         i18n:
           zh-CN: 端口
           en-US: Port
+          ja-JP: ポート
       - field: address
         type: 1
         i18n:
           zh-CN: 地址
           en-US: Address
+          ja-JP: アドレス
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
     protocol: jmx
     # the config content when protocol is http
@@ -155,6 +168,7 @@ metrics:
     i18n:
       zh-CN: 内存池
       en-US: Memory Pool
+      ja-JP: メモリプール
     fields:
       - field: name
         type: 1
@@ -162,30 +176,35 @@ metrics:
         i18n:
           zh-CN: 指标名称
           en-US: Name
+          ja-JP: 名前
       - field: committed
         type: 0
         unit: MB
         i18n:
           zh-CN: 已分配内存
           en-US: Committed
+          ja-JP: コミットされたメモリ
       - field: init
         type: 0
         unit: MB
         i18n:
           zh-CN: 初始化内存
           en-US: Init
+          ja-JP: イニシャルメモリ
       - field: max
         type: 0
         unit: MB
         i18n:
           zh-CN: 最大内存
           en-US: Max
+          ja-JP: 最大メモリ
       - field: used
         type: 0
         unit: MB
         i18n:
           zh-CN: 已使用内存
           en-US: Used
+          ja-JP: 使用したメモリ
     units:
       - committed=B->MB
       - init=B->MB
@@ -222,6 +241,7 @@ metrics:
     i18n:
       zh-CN: 类加载信息
       en-US: Class Loading
+      ja-JP: クラスローディング情報
     # 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
@@ -230,16 +250,19 @@ metrics:
         i18n:
           zh-CN: 当前已加载类数量
           en-US: Loaded Class Count
+          ja-JP: ロードされたクラス数
       - field: TotalLoadedClassCount
         type: 0
         i18n:
           zh-CN: 已加载类总数量
           en-US: Total Loaded Class Count
+          ja-JP: ロードされたクラス総数
       - field: UnloadedClassCount
         type: 0
         i18n:
           zh-CN: 未加载类总数量
           en-US: Unloaded Class Count
+          ja-JP: アンロードされたクラス総数
     protocol: jmx
     jmx:
       host: ^_^host^_^
@@ -254,6 +277,7 @@ metrics:
     i18n:
       zh-CN: 线程信息
       en-US: Thread
+      ja-JP: スレッド情報
     # 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
@@ -262,33 +286,39 @@ metrics:
         i18n:
           zh-CN: 已启动线程总数
           en-US: Total Started Thread Count
+          ja-JP: スレッド総数
       - field: ThreadCount
         type: 0
         i18n:
           zh-CN: 活跃线程数
           en-US: Thread Count
+          ja-JP: 活躍スレッド数
       - field: PeakThreadCount
         type: 0
         i18n:
           zh-CN: 最大峰值线程数
           en-US: Peak Thread Count
+          ja-JP: 最大スレッド数
       - field: DaemonThreadCount
         type: 0
         i18n:
           zh-CN: 活跃守护线程数
           en-US: Daemon Thread Count
+          ja-JP: デーモンスレッド数
       - field: CurrentThreadUserTime
         type: 0
         unit: s
         i18n:
           zh-CN: 线程占用的CPU时间(用户态)
           en-US: Current Thread User Time
+          ja-JP: 現在のスレッドユーザー時間
       - field: CurrentThreadCpuTime
         type: 0
         unit: s
         i18n:
           zh-CN: 线程占用的CPU时间
           en-US: Current Thread CPU Time
+          ja-JP: 現在のスレッドシステム時間
     units:
       - CurrentThreadUserTime=NS->S
       - CurrentThreadCpuTime=NS->S
@@ -305,6 +335,7 @@ metrics:
     i18n:
       zh-CN: 应用信息
       en-US: Application
+      ja-JP: 応用情報
     priority: 4
     fields:
       - field: name
@@ -313,83 +344,99 @@ metrics:
         i18n:
           zh-CN: 名称
           en-US: Name
+          ja-JP: 名前
       - field: acceptCount
         type: 0
         i18n:
           zh-CN: 接收请求数
           en-US: Accept Count
+          ja-JP: 受け入れたリクエスト数
       - field: acceptorThreadCount
         type: 0
         i18n:
           zh-CN: 接收处理线程数
           en-US: Acceptor Thread Count
+          ja-JP: アクセプタスレッド数
       - field: acceptorThreadPriority
         type : 0
         i18n:
           zh-CN: 接收线程级别
           en-US: Acceptor Thread Priority
+          ja-JP: アクセプタスレッド優先度
       - field: connectionTimeout
         type: 0
         unit: ms
         i18n:
           zh-CN: 链接超时时间
           en-US: Connection Timeout
+          ja-JP: 接続のタイムアウト
       - field: currentThreadCount
         type: 0
         i18n:
           zh-CN: 当前线程数
           en-US: Current Thread Count
+          ja-JP: 現在のスレッド数
       - field: currentThreadsBusy
         type: 0
         i18n:
           zh-CN: 繁忙线程数
           en-US: Current Threads Busy
+          ja-JP: 現在の忙しいスレッド数
       - field: keepAliveCount
         type: 0
         i18n:
           zh-CN: 心跳保持链接数量
           en-US: Keep Alive Count
+          ja-JP: ハートビート数量
       - field: keepAliveTimeout
         type: 0
         unit: ms
         i18n:
           zh-CN: 心跳超时时间
           en-US: Keep Alive Timeout
+          ja-JP: ハートビートのタイムアウト
       - field: maxConnections
         type: 0
         i18n:
           zh-CN: 最大链接数
           en-US: Max Connections
+          ja-JP: 最大接続数
       - field: maxKeepAliveRequests
         type: 0
         i18n:
           zh-CN: 最大链接保持请求
           en-US: Max KeepAlive Requests
+          ja-JP: 最大KeepAliveリクエスト数
       - field: maxThreads
         type: 0
         i18n:
           zh-CN: 最大线程数
           en-US: Max Threads
+          ja-JP: 最大スレッド数
       - field: minSpareThreads
         type: 0
         i18n:
           zh-CN: 最小备用线程数
           en-US: Min Spare Threads
+          ja-JP: 最小予備スレッド数
       - field: pollerThreadCount
         type: 0
         i18n:
           zh-CN: 轮询线程数
           en-US: Poller Thread Count
+          ja-JP: ポーラースレッド数
       - field: pollerThreadPriority
         type: 0
         i18n:
           zh-CN: 轮询线程级别
           en-US: Poller Thread Priority
+          ja-JP: ポーラースレッド優先度
       - field: running
         type: 1
         i18n:
           zh-CN: 运行中
           en-US: Running
+          ja-JP: 実行中
     protocol: jmx
     jmx:
       host: ^_^host^_^

hertzbeat-manager/src/main/resources/define/app-windows.yml

@@ -316,7 +316,7 @@ metrics:
         type: 0
         i18n:
           zh-CN: 编号
-          en-US: 编号
+          en-US: Index
       - field: hrSWInstalledName
         type: 1
         i18n:
@@ -357,14 +357,14 @@ metrics:
         type: 0
         i18n:
           zh-CN: 编号
-          en-US: 编号
+          en-US: Index
       - field: descr
         type: 1
         i18n:
           zh-CN: 存储描述
           en-US: Storage Description
         label: true
-      - field: size
+      - field: Size
         i18n:
           zh-CN: 存储大小
           en-US: Storage Size
@@ -400,7 +400,7 @@ metrics:
     calculates:
       - index=hrStorageIndex
       - descr=hrStorageDescr
-      - size=hrStorageSize * hrStorageAllocationUnits
+      - Size=hrStorageSize * hrStorageAllocationUnits
       - free=(hrStorageSize - hrStorageUsed) * hrStorageAllocationUnits
       - used=hrStorageUsed * hrStorageAllocationUnits
       - usage= hrStorageUsed / hrStorageSize * 100

hertzbeat-manager/src/main/resources/sureness.yml

@@ -72,7 +72,6 @@ resourceRole:
 # rule: api===method 
 # eg: /api/v1/source3===get means /api/v1/source3===get can be access by anyone, no need auth.
 excludedResource:
-  - /api/alerts/report/**===*
   - /api/alert/sse/**===*
   - /api/account/auth/**===*
   - /api/i18n/**===get

home/blog/2022-06-01-hertzbeat-v1.0.md

@@ -3,7 +3,6 @@ title: Cloud Monitoring System HertzBeat v1.0 Officially Released
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-06-19-hertzbeat-v1.1.0.md

@@ -3,7 +3,6 @@ title: Cloud Monitoring System HertzBeat v1.1.0 Released! Start Your Monitoring
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-06-22-one-step-up.md

@@ -3,7 +3,6 @@ title: HertzBeat Monitoring System v1.1.0 Released! Start Your Monitoring Journe
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource]
 ---
 

home/blog/2022-07-10-hertzbeat-v1.1.1.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.1.1 is Publish！
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-09-04-hertzbeat-v1.1.3.md

@@ -3,7 +3,6 @@ title: Cloud monitoring system HertzBeat v1.1.3 released!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-09-10-ssl-practice.md

@@ -3,7 +3,6 @@ title: Best Practices for SSL Certificate Expiration Monitoring
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 ---
 

home/blog/2022-10-08-hertzbeat-v1.2.0.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.2.0 Released! Easy-to-use and friendly open source real-time
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-11-28-hertzbeat-v1.2.2.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.2.2！Support K8S Monitor And More.
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-12-19-new-committer.md

@@ -3,7 +3,6 @@ title: 恭喜 HertzBeat 迎来了两位新晋社区Committer
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2022-12-28-hertzbeat-v1.2.3.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.2.3！Support Prometheus,ShenYu and IotDb
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2023-01-05-monitor-iotdb.md

@@ -3,7 +3,6 @@ title: Use HertzBeat Monitoring IoTDB
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 ---
 

home/blog/2023-01-08-monitor-shenyu.md

@@ -3,7 +3,6 @@ title: HertzBeat's Monitoring Practice for API Gateway Apache ShenYu
 author: tom
 author_title: tom
 author_url: https://github.com/tomsun28
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource, practice]
 ---
 

home/blog/2023-02-02-monitor-dynamic-tp.md

@@ -3,7 +3,6 @@ title: Monitoring Practices for DynamicTp Thread Pooling Framework with HertzBea
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 ---
 

home/blog/2023-02-10-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome two new Committers from HertzBeat
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource]
 ---
 

home/blog/2023-02-11-monitor-mysql.md

@@ -3,7 +3,6 @@ title: Use the open source real-time monitoring tool HertzBeat to monitor and al
 author: tom
 author_title: tom
 author_url: https://github.com/tomsun28
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource, practice]
 Keywords: [Open source monitoring tool, open source database monitoring, Mysql database monitoring]
 ---

home/blog/2023-02-15-monitor-linux.md

@@ -3,7 +3,6 @@ title: Monitoring Linux Operating Systems Using Open Source Real-Time Monitoring
 author: tom
 author_title: tom
 author_url: https://github.com/tomsun28
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource, practice]
 keywords: [Open source monitoring tool, operating system monitoring, Linux monitoring]
 ---

home/blog/2023-03-15-hertzbeat-v1.3.0.md

@@ -3,7 +3,6 @@ title: Open source real-time monitoring tool HertzBeat v1.3.0 released, online c
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Linux monitoring]
 ---

home/blog/2023-03-22-monitor-springboot2.md

@@ -3,7 +3,6 @@ title: Monitoring SpringBoot2 Metrics with HertzBeat in 5 minutes
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [opensource monitoring, SpringBoot monitoring, alert]
 ---

home/blog/2023-05-09-hertzbeat-v1.3.1.md

@@ -3,7 +3,6 @@ title: Open source real-time monitoring tool HertzBeat v1.3.1 released
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Linux monitoring]
 ---

home/blog/2023-05-11-greptimedb-store.md

@@ -3,7 +3,6 @@ title: GreptimeDB & HertzBeat, using the open source temporal database GreptimeD
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, open source temporal database, HertzBeat, GreptimeDB]
 ---

home/blog/2023-07-05-hertzbeat-v1.3.2.md

@@ -3,7 +3,6 @@ title: Open source monitoring HertzBeat v1.3.2 released, Easier to use
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Linux monitoring]
 ---

home/blog/2023-08-14-hertzbeat-v1.4.0.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.4.0 released, cluster is coming!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Linux monitoring]
 ---

home/blog/2023-08-28-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2023-09-26-hertzbeat-v1.4.1.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.4.1 released, better experience!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Linux monitoring]
 ---

home/blog/2023-11-12-hertzbeat-v1.4.2.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.4.2 released, custom notice template!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Linux monitoring]
 ---

home/blog/2023-12-11-hertzbeat-v1.4.3.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.4.3 released, prometheus-compatible!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-01-11-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-01-18-hertzbeat-v1.4.4.md

@@ -3,7 +3,6 @@ title: HertzBeat v1.4.4 released now!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-04-17-to-apache.md

@@ -3,7 +3,6 @@ title: The open-source real-time monitoring HertzBeat is donated to the Apache I
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---
@@ -22,7 +21,7 @@ We warmly welcome everyone to join the HertzBeat community. The community accept
 
 ## What is HertzBeat
 
-[Apache HertzBeat](https://github.com/apache/hertzbeat) (incubating) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.
+[Apache HertzBeat](https://github.com/apache/hertzbeat) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.
 
 ### Features
 

home/blog/2024-06-15-hertzbeat-v1.6.0.md

@@ -3,14 +3,13 @@ title: HertzBeat First Apache version v1.6.0 released now!
 author: tom  
 author_title: tom   
 author_url: https://github.com/tomsun28  
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4  
 tags: [opensource, practice]
 keywords: [open source, monitoring, alerting]
 ---
 
-**Hi guys, We are excited to announce that Apache HertzBeat (incubating) has released its first Apache version v1.6.0! 🎉.**
+**Hi guys, We are excited to announce that Apache HertzBeat has released its first Apache version v1.6.0! 🎉.**
 
-Through nearly five months of community development iteration and two months of Apache Incubator incubation process, Apache HertzBeat (incubating) v1.6.0 is finally out.  
+Through nearly five months of community development iteration and two months of Apache Incubator incubation process, Apache HertzBeat v1.6.0 is finally out.  
 In this version, we added monitoring for OpenAi, Redfish protocol servers, plugin mechanism, and support for NebulaGraph, Apache Yarn, HDFS, Hbase, Storm, and more functional features.  
 Due to license compatibility issues, we replaced multiple dependencies at the bottom layer, Hibernate -> EclipseLink, which is also a rare migration pitfall practice in the JPA ecosystem.  
 At the same time, some bugs were fixed and some functions were optimized, and more complete documents. Welcome everyone to try to use, put forward valuable opinions and suggestions, and promote the development of HertzBeat together.
@@ -23,7 +22,7 @@ Upgrade Guide: <https://hertzbeat.apache.org/blog/2024/06/11/hertzbeat-v1.6.0-up
 
 ## What is HertzBeat?
 
-[Apache HertzBeat](https://github.com/apache/hertzbeat) (incubating) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.
+[Apache HertzBeat](https://github.com/apache/hertzbeat) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.
 
 ## Features
 

home/blog/2024-07-07-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: crossoverJie
 author_title: crossoverJie
 author_url: https://github.com/crossoverjie
-author_image_url: https://avatars.githubusercontent.com/u/15684156?s=400&v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-07-08-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: zhangshenghang
 author_title: zhangshenghang
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/29418975?s=400&v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-07-15-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: LiuTianyou
 author_title: LiuTianyou
 author_url: https://github.com/LiuTianyou
-author_image_url: https://avatars.githubusercontent.com/u/30208283?v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-07-27-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: Calvin979
 author_title: Calvin979
 author_url: https://github.com/Calvin979
-author_image_url: https://avatars.githubusercontent.com/u/131688897?v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-07-28-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: linDong
 author_title: linDong
 author_url: https://github.com/Yanshuming1
-author_image_url: https://avatars.githubusercontent.com/u/118667222?v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-07-29-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: kerwin612
 author_title: Le Zhang
 author_url: https://github.com/kerwin612
-author_image_url: https://avatars.githubusercontent.com/u/3371163?v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-08-18-new-committer.md

@@ -3,7 +3,6 @@ title: Becoming an Apache Committer is a recognition of my participation in open
 author: yuluo-yx
 author_title: Shown Ji
 author_url: https://github.com/yuluo-yx
-author_image_url: https://avatars.githubusercontent.com/u/77964041
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Apache, Apache Committer, Hertzbeat]
 ---

home/blog/2024-08-31-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome to HertzBeat Community Committer!
 author: aias00
 author_title: Hongyu Liu
 author_url: https://github.com/Aias00
-author_image_url: https://avatars.githubusercontent.com/u/25810623
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system, Apache, Apache Committer, Hertzbeat]
 ---

home/blog/2024-09-10-new-committer.md

@@ -3,7 +3,6 @@ title: Warmly Welcome HertzBeat's New Community Committer!
 author: zuobiao-zhou
 author_title: Yuxuan Zhang
 author_url: https://github.com/zuobiao-zhou
-author_image_url: https://avatars.githubusercontent.com/u/61108539
 tags: [opensource, practice]
 keywords:
   [

home/blog/2024-11-09-hertzbeat-v1.6.1.md

@@ -3,7 +3,6 @@ title: Announcement of Apache Hertzbeat 1.6.1 Release
 author: zhangshenghang
 author_title: zhangshenghang
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/29418975?s=400&v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2024-11-24-custom-development.md

@@ -3,7 +3,6 @@ title: How to Participate in Developing Custom Collectors
 author: zhangshenghang
 author_title: zhangshenghang
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/29418975?s=400&v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2025-03-03-gsoc-2025.md

@@ -3,7 +3,6 @@ title: GSOC Google Summer of Code 2025 Recruitment is Underway | We Look Forward
 author: zhangshenghang
 author_title: zhangshenghang
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/29418975?s=400&v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2025-03-10-new-committer.md

@@ -3,7 +3,6 @@ title: Warmly Welcome HertzBeat's New Community Committer!
 author: yunfan24
 author_title: Lixin Diao
 author_url: https://github.com/yunfan24
-author_image_url: https://avatars.githubusercontent.com/u/91836599?v=4
 tags: [opensource, practice]
 keywords:
   [

home/blog/2025-04-06-new-pmc.md

@@ -3,7 +3,6 @@ title: From Commiter to PMC： The Journey of Growth at Apache Hertzbeat
 author: zhangshenghang
 author_title: zhangshenghang
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/29418975?s=400&v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/blog/2025-04-10-hertzbeat-v1.7.0.md

@@ -3,7 +3,6 @@ title: Announcement of Apache Hertzbeat 1.7.0 Release
 author: tomsun28
 author_title: tomsun28
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource, release]
 keywords: [open source monitoring system, alerting system, Hertzbeat, release]
 ---

home/blog/2025-05-22-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome HertzBeat's New Community Committer!
 author: pwallk
 author_title: Kang Li
 author_url: https://github.com/pwallk
-author_image_url: https://avatars.githubusercontent.com/u/69385076
 tags: [opensource, practice]
 keywords:
   [

home/blog/2025-06-10-hertzbeat-v1.7.1.md

@@ -3,7 +3,6 @@ title: Announcement of Apache Hertzbeat 1.7.1 Release
 author: tomsun28
 author_title: tomsun28
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource, release]
 keywords: [open source monitoring system, alerting system, Hertzbeat, release]
 ---

home/blog/2025-06-29-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome HertzBeat's New Community Committer!
 author: MasamiYui
 author_title: Yijun Yin
 author_url: https://github.com/MasamiYui
-author_image_url: https://avatars.githubusercontent.com/u/22274133
 tags: [opensource, practice]
 keywords:
   [

home/blog/2025-07-07-hertzbeat-v1.7.2.md

@@ -3,7 +3,6 @@ title: Announcement of Apache Hertzbeat 1.7.2 Release
 author: tomsun28
 author_title: tomsun28
 author_url: https://github.com/zhangshenghang
-author_image_url: https://avatars.githubusercontent.com/u/24788200?s=400&v=4
 tags: [opensource, release]
 keywords: [open source monitoring system, alerting system, Hertzbeat, release]
 ---

home/blog/2025-07-11-new-committer.md

@@ -3,7 +3,6 @@ title: Welcome HertzBeat's New Community Committer!
 author: bigcyy
 author_title: Yang Chen
 author_url: https://github.com/bigcyy
-author_image_url: https://avatars.githubusercontent.com/u/73413979
 tags: [opensource, practice]
 keywords:
   [

home/blog/2025-5-19-new-pmc.md

@@ -3,7 +3,6 @@ title: "From User to PPMC Member: Contributing to Open Source with Passion at Ap
 author: liutianyou
 author_title: liutianyou
 author_url: https://github.com/Liutianyou
-author_image_url: https://avatars.githubusercontent.com/u/30208283?v=4
 tags: [opensource, practice]
 keywords: [open source monitoring system, alerting system]
 ---

home/docs/advanced/extend-tutorial.md

@@ -4,7 +4,7 @@ title: Quick Tutorial Customize and adapt a monitoring based on HTTP protocol
 sidebar_label: Tutorial Case
 ---
 
-Through this tutorial, we describe step by step how to customize and adapt a monitoring type based on the http protocol under the Apache HertzBeat (incubating).
+Through this tutorial, we describe step by step how to customize and adapt a monitoring type based on the http protocol under the Apache HertzBeat.
 
 Before reading this tutorial, we hope that you are familiar with how to customize types, metrics, protocols, etc. from [Custom Monitoring](extend-point) and [Http Protocol Customization](extend-http).
 

home/docs/community/how-to-release.md

@@ -213,9 +213,9 @@ mvn clean package -Pcluster
 
 The release package are here:
 
-- `dist/apache-hertzbeat-{version}-incubating-bin.tar.gz`
-- `dist/apache-hertzbeat-collector-{version}-incubating-bin.tar.gz`
-- `dist/apache-hertzbeat-{version}-incubating-docker-compose.tar.gz`
+- `dist/apache-hertzbeat-{version}-bin.tar.gz`
+- `dist/apache-hertzbeat-collector-{version}-bin.tar.gz`
+- `dist/apache-hertzbeat-{version}-docker-compose.tar.gz`
 
 #### 3.4 Package the source code
 
@@ -224,12 +224,12 @@ The release package are here:
 ```shell
 git archive \
 --format=tar.gz \
---output="dist/apache-hertzbeat-1.6.0-incubating-src.tar.gz" \
---prefix=apache-hertzbeat-1.6.0-incubating-src/ \
+--output="dist/apache-hertzbeat-1.6.0-src.tar.gz" \
+--prefix=apache-hertzbeat-1.6.0-src/ \
 release-1.6.0-rc1
 ```
 
-The archive package is here `dist/apache-hertzbeat-1.6.0-incubating-src.tar.gz`
+The archive package is here `dist/apache-hertzbeat-1.6.0-src.tar.gz`
 
 ### Sign package
 
@@ -252,18 +252,18 @@ for i in *.tar.gz; do echo $i; sha512sum $i > $i.sha512 ; done
 > The final file list is as follows
 
 ```text
-apache-hertzbeat-1.6.0-incubating-src.tar.gz
-apache-hertzbeat-1.6.0-incubating-src.tar.gz.asc
-apache-hertzbeat-1.6.0-incubating-src.tar.gz.sha512
-apache-hertzbeat-1.6.0-incubating-bin.tar.gz
-apache-hertzbeat-1.6.0-incubating-bin.tar.gz.asc
-apache-hertzbeat-1.6.0-incubating-bin.tar.gz.sha512
-apache-hertzbeat-1.6.0-incubating-docker-compose.tar.gz
-apache-hertzbeat-1.6.0-incubating-docker-compose.tar.gz.asc
-apache-hertzbeat-1.6.0-incubating-docker-compose.tar.gz.sha512
-apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz
-apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz.asc
-apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz.sha512
+apache-hertzbeat-1.6.0-src.tar.gz
+apache-hertzbeat-1.6.0-src.tar.gz.asc
+apache-hertzbeat-1.6.0-src.tar.gz.sha512
+apache-hertzbeat-1.6.0-bin.tar.gz
+apache-hertzbeat-1.6.0-bin.tar.gz.asc
+apache-hertzbeat-1.6.0-bin.tar.gz.sha512
+apache-hertzbeat-1.6.0-docker-compose.tar.gz
+apache-hertzbeat-1.6.0-docker-compose.tar.gz.asc
+apache-hertzbeat-1.6.0-docker-compose.tar.gz.sha512
+apache-hertzbeat-collector-1.6.0-bin.tar.gz
+apache-hertzbeat-collector-1.6.0-bin.tar.gz.asc
+apache-hertzbeat-collector-1.6.0-bin.tar.gz.sha512
 ```
 
 #### 3.6 Verify signature
@@ -274,15 +274,15 @@ $ cd dist
 # Verify signature
 $ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
 
-apache-hertzbeat-1.6.0-incubating-src.tar.gz
+apache-hertzbeat-1.6.0-src.tar.gz
 gpg: Signature made Tue May  2 12:16:35 2023 CST
 gpg:                using RSA key 85778A4CE4DD04B7E07813ABACFB69E705016886
 gpg: Good signature from "muchunjin (apache key) <muchunjin@apache.org>" [ultimate]
-apache-hertzbeat_2.11-1.6.0-incubating-bin.tar.gz
+apache-hertzbeat_2.11-1.6.0-bin.tar.gz
 gpg: Signature made Tue May  2 12:16:36 2023 CST
 gpg:                using RSA key 85778A4CE4DD04B7E07813ABACFB69E705016886
 gpg: Good signature from "muchunjin (apache key) <muchunjin@apache.org>" [ultimate]
-apache-hertzbeat_2.12-1.6.0-incubating-bin.tar.gz
+apache-hertzbeat_2.12-1.6.0-bin.tar.gz
 gpg: Signature made Tue May  2 12:16:37 2023 CST
 gpg:                using RSA key 85778A4CE4DD04B7E07813ABACFB69E705016886
 gpg: BAD signature from "muchunjin (apache key) <muchunjin@apache.org>" [ultimate]
@@ -290,14 +290,14 @@ gpg: BAD signature from "muchunjin (apache key) <muchunjin@apache.org>" [ultimat
 # Verify SHA512
 $ for i in *.tar.gz; do echo $i; sha512sum --check $i.sha512; done
 
-apache-hertzbeat-1.6.0-incubating-src.tar.gz
-apache-hertzbeat-1.6.0-incubating-src.tar.gz: OK
-apache-hertzbeat-1.6.0-incubating-bin.tar.gz
-apache-hertzbeat-1.6.0-incubating-bin.tar.gz: OK
-apache-hertzbeat-1.6.0-incubating-docker-compose.tar.gz
-apache-hertzbeat-1.6.0-incubating-docker-compose.tar.gz: OK
-apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz
-apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz: OK
+apache-hertzbeat-1.6.0-src.tar.gz
+apache-hertzbeat-1.6.0-src.tar.gz: OK
+apache-hertzbeat-1.6.0-bin.tar.gz
+apache-hertzbeat-1.6.0-bin.tar.gz: OK
+apache-hertzbeat-1.6.0-docker-compose.tar.gz
+apache-hertzbeat-1.6.0-docker-compose.tar.gz: OK
+apache-hertzbeat-collector-1.6.0-bin.tar.gz
+apache-hertzbeat-collector-1.6.0-bin.tar.gz: OK
 ```
 
 #### 3.7 Publish the dev directory of the Apache SVN material package
@@ -350,13 +350,13 @@ svn commit -m "release for HertzBeat 1.6.0"
 Send a voting email in the community requires at least three `+1` and no `-1`.
 
 > `Send to`: <dev@hertzbeat.apache.org> <br />
-> `Title`: [VOTE] Release Apache HertzBeat (incubating) 1.6.0 rc1 <br />
+> `Title`: [VOTE] Release Apache HertzBeat 1.6.0 rc1 <br />
 > `Body`:
 
 ```text
 Hello HertzBeat Community:
 
-This is a call for vote to release Apache HertzBeat (incubating) version release-1.6.0-RC1.
+This is a call for vote to release Apache HertzBeat version release-1.6.0-RC1.
 
 Apache HertzBeat - a real-time monitoring system with agentless, performance cluster, prometheus-compatible, custom monitoring and status page building capabilities.
 
@@ -406,13 +406,13 @@ Thanks!
 After 72 hours, the voting results will be counted, and the voting result email will be sent, as follows.
 
 > `Send to`: <dev@hertzbeat.apache.org> <br />
-> `Title`: [RESULT]\[VOTE\] Release Apache HertzBeat (incubating) 1.6.0-rc1 <br />
+> `Title`: [RESULT]\[VOTE\] Release Apache HertzBeat 1.6.0-rc1 <br />
 > `Body`:
 
 ```text
 Dear HertzBeat community,
 
-Thanks for your review and vote for "Release Apache HertzBeat (incubating) 1.6.0-rc1"
+Thanks for your review and vote for "Release Apache HertzBeat 1.6.0-rc1"
 I'm happy to announce the vote has passed:
 ---
 4 binding +1, from:
@@ -441,14 +441,14 @@ One item of the email content is `Vote thread`, and the link is obtained here: <
 Send a voting email in the incubator community requires at least three `+1` and no `-1`.
 
 > `Send to`: <general@incubator.apache.org> <br />
-> `Title`: [VOTE] Release Apache HertzBeat (incubating) 1.6.0-rc1 <br />
+> `Title`: [VOTE] Release Apache HertzBeat 1.6.0-rc1 <br />
 > `Body`:
 
 ```text
 Hello Incubator Community:
 
-This is a call for a vote to release Apache HertzBeat (incubating) version 1.6.0-RC1.
-The Apache HertzBeat community has voted on and approved a proposal to release Apache HertzBeat (incubating) version 1.6.0-RC1.
+This is a call for a vote to release Apache HertzBeat version 1.6.0-RC1.
+The Apache HertzBeat community has voted on and approved a proposal to release Apache HertzBeat version 1.6.0-RC1.
 We now kindly request the Incubator PPMC members review and vote on this incubator release.
 Apache HertzBeat, a real-time monitoring system with agentless, performance cluster, prometheus-compatible, custom monitoring and status page building capabilities.
 
@@ -486,7 +486,7 @@ https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-
 ---
 Thanks,
 
-On behalf of Apache HertzBeat (incubating) community
+On behalf of Apache HertzBeat community
 ---
 Best,
 ChunJin Mu
@@ -507,13 +507,13 @@ Chunjin Mu
 Then the voting results will be counted, and the voting result email will be sent, as follows.
 
 > `Send to`: <general@incubator.apache.org> <br />
-> `Title`: [RESULT]\[VOTE\] Release Apache HertzBeat (incubating) 1.6.0-rc1 <br />
+> `Title`: [RESULT]\[VOTE\] Release Apache HertzBeat 1.6.0-rc1 <br />
 > `Body`:
 
 ```text
 Hi Incubator Community,
 
-The vote to release Apache HertzBeat (incubating) 1.6.0-rc4 has passed with 3 +1 binding and no +0 or -1 votes.
+The vote to release Apache HertzBeat 1.6.0-rc4 has passed with 3 +1 binding and no +0 or -1 votes.
 
 3 binding votes, no +0 or -1 votes.
 
@@ -584,13 +584,13 @@ The rename the release-1.6.0-rc1 branch to release-1.6.0.
 
 > `Send to`: <general@incubator.apache.org> <br />
 > `cc`: <dev@hertzbeat.apache.org> <br />
-> `Title`: [ANNOUNCE] Apache HertzBeat (incubating) 1.6.0 released <br />
+> `Title`: [ANNOUNCE] Apache HertzBeat 1.6.0 released <br />
 > `Body`:
 
 ```text
 Hi Community,
 
-We are glad to announce the release of Apache HertzBeat (incubating) 1.6.0.
+We are glad to announce the release of Apache HertzBeat 1.6.0.
 Thanks again for your help. 
 
 Apache HertzBeat (https://hertzbeat.apache.org/) - a real-time monitoring system with agentless, performance cluster, prometheus-compatible, custom monitoring and status page building capabilities.

home/docs/community/how-to-verify.md

@@ -91,7 +91,7 @@ check result
 > If something like the following appears, it means the signature is correct. Keyword: **`Good signature`**
 
 ```shell
-apache-hertzbeat-xxx-incubating-src.tar.gz
+apache-hertzbeat-xxx-src.tar.gz
 gpg: Signature made XXXX
 gpg: using RSA key XXXXX
 gpg: Good signature from "xxx @apache.org>"
@@ -105,18 +105,16 @@ for i in *.tar.gz; do echo $i; sha512sum --check  $i.sha512; done
 
 #### 2.4 Check the binary package
 
-unzip  `apache-hertzbeat-${release.version}-incubating-bin.tar.gz`
+unzip  `apache-hertzbeat-${release.version}-bin.tar.gz`
 
 ```shell
-tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz
+tar -xzvf apache-hertzbeat-${release.version}-bin.tar.gz
 ```
 
 check as follows:
 
 - [ ] Check whether the source package contains unnecessary files, which makes the tar package too large
-- [ ] Folder contains the word `incubating`
 - [ ] There are `LICENSE` and `NOTICE` files
-- [ ] There is a `DISCLAIMER` or `DISCLAIMER-WIP` file
 - [ ] The year in the `NOTICE` file is correct
 - [ ] Only text files exist, not binary files
 - [ ] All files have ASF license at the beginning
@@ -127,10 +125,10 @@ check as follows:
 
 > If the binary/web-binary package is uploaded, check the binary package.
 
-Unzip `apache-hertzbeat-${release_version}-incubating-src.tar.gz`
+Unzip `apache-hertzbeat-${release_version}-src.tar.gz`
 
 ```shell
-cd apache-hertzbeat-${release_version}-incubating-src
+cd apache-hertzbeat-${release_version}-src
 ```
 
 compile the source code: [Build HertzBeat Binary Package](https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package)
@@ -138,7 +136,6 @@ compile the source code: [Build HertzBeat Binary Package](https://hertzbeat.apac
 and check as follows:
 
 - [ ] There are `LICENSE` and `NOTICE` files
-- [ ] There is a `DISCLAIMER` or `DISCLAIMER-WIP` file
 - [ ] The year in the `NOTICE` file is correct
 - [ ] All text files have ASF license at the beginning
 - [ ] Check the third-party dependent license:

home/docs/community/new_committer_process.md

@@ -273,7 +273,7 @@ Subject: [ANNOUNCE] New committer: ${NEW_COMMITTER_NAME}
 ```text
 Hello Community,
 
-The Podling Project Management Committee (PPMC) for Apache HertzBeat (incubating)
+The Podling Project Management Committee (PPMC) for Apache HertzBeat
 has invited ${NEW_COMMITTER_NAME} to become a committer and we are pleased to
 announce that he has accepted.
 

home/docs/community/new_pmc_member_process.md

@@ -280,5 +280,5 @@ submission process. This should enable better productivity.
 A PPMC member helps manage and guide the direction of the project.
 
 Thanks,
-On behalf of the Apache HertzBeat (incubating) PPMC
+On behalf of the Apache HertzBeat PPMC
 ```

home/docs/download.md

@@ -1,10 +1,10 @@
 ---
 id: download
-title: Download Apache HertzBeat (incubating)
+title: Download Apache HertzBeat
 sidebar_label: Download
 ---
 
-> **Here is the Apache HertzBeat (incubating) official download page.**
+> **Here is the Apache HertzBeat official download page.**
 > **Please choose version to download from the following tables. It is recommended use the latest.**
 
 :::tip

home/docs/help/collector.md

@@ -5,7 +5,7 @@ sidebar_label: Collector
 keywords: [monitoring, observability, collector, metrics]
 ---
 
-> HertzBeat Collector is a lightweight data collection module that enables metrics collection, high availability deployments, and cloud-edge collaboration in Apache HertzBeat (incubating).
+> HertzBeat Collector is a lightweight data collection module that enables metrics collection, high availability deployments, and cloud-edge collaboration in Apache HertzBeat.
 
 ## Introduction
 

home/docs/help/mcp_sse_server.md

@@ -15,6 +15,7 @@ This page explains how connect to the HertzBeat MCP SSE server. The MCP server a
 ### Connect to the MCP server
 
 Make sure that hertzbeat server is up and running. If you are using any other port than 1157, replace the following accordingly
+
 - URL: `http://localhost:1157/api/sse`
 
 ### Authentication
@@ -23,10 +24,10 @@ You must authenticate each request using one of the following methods:
 
 - JWT bearer token
 
-     - Header: `Authorization: Bearer <your-jwt-token>`
+  - Header: `Authorization: Bearer <your-jwt-token>`
 
 - Basic authentication
-     - Header: `Authorization: Basic <base64(username:password)>`
+  - Header: `Authorization: Basic <base64(username:password)>`
 
 ### Cursor MCP configuration
 

home/docs/help/spring_gateway.md

@@ -1,15 +1,15 @@
 ---
 id: spring_gateway 
-Title: Monitoring Spring Gateway   
-sidebar_label: Spring Gateway
-keywords: [open source monitoring tool, open source spring gateway monitoring tool, monitoring spring gateway metrics]
+Title: Monitoring Spring Cloud Gateway
+sidebar_label: Spring Cloud Gateway
+keywords: [open source monitoring tool, open source Spring Cloud Gateway monitoring tool, monitoring Spring Cloud Gateway metrics]
 ---
 
 > Collect and monitor the general performance metrics exposed by the SpringBoot actuator.
 
 ## Pre-monitoring operations
 
-If you want to monitor information in 'Spring Gateway' with this monitoring type, you need to integrate your SpringBoot application and enable the SpringBoot Actuator.
+If you want to monitor information in `Spring Cloud Gateway` with this monitoring type, you need to integrate your `Spring Cloud Gateway` application and enable the SpringBoot Actuator.
 
 **1、Add POM .XML dependencies:**
 
@@ -26,25 +26,26 @@ If you want to monitor information in 'Spring Gateway' with this monitoring type
 management:
   endpoint:
     gateway:
-      enabled: true # default value
+      enabled: true
+    env:
+      show-values: ALWAYS
   endpoints:
     web:
       exposure:
-        include: '*'
-    enabled-by-default: on
+        include: "*"
 ```
 
 ### Configure parameters
 
-|       Parameter name        |                                                    Parameter Help describes the                                                     |
-|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
-| Monitor Host                | THE MONITORED PEER IPV4, IPV6 OR DOMAIN NAME. Note ⚠️ that there are no protocol headers (eg: https://, http://).                   |
-| Monitoring Name             | A name that identifies this monitoring that needs to be unique.                                                                     |
-| Port                        | The default port provided by the database is 8080.                                                                                  |
-| Enable HTTPS                | Whether to access the website through HTTPS, please note that ⚠️ when HTTPS is enabled, the default port needs to be changed to 443 |
-| The acquisition interval is | Monitor the periodic data acquisition interval, in seconds, and the minimum interval that can be set is 30 seconds                  |
-| Whether to probe the        | Whether to check the availability of the monitoring before adding a monitoring is successful, and the new modification operation    | will continue only if the probe is successful |
-| Description Comment         | For more information identifying and describing the remarks for this monitoring, users can remark the information here              |
+| Parameter name              | Parameter Help describes the                                                                                                                                                   |
+|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Monitor Host                | THE MONITORED PEER IPV4, IPV6 OR DOMAIN NAME. Note ⚠️ that there are no protocol headers (eg: https://, http://).                                                              |
+| Monitoring Name             | A name that identifies this monitoring that needs to be unique.                                                                                                                |
+| Port                        | The default port provided by the database is 8080.                                                                                                                             |
+| Enable HTTPS                | Whether to access the website through HTTPS, please note that ⚠️ when HTTPS is enabled, the default port needs to be changed to 443                                            |
+| The acquisition interval is | Monitor the periodic data acquisition interval, in seconds, and the minimum interval that can be set is 30 seconds                                                             |
+| Whether to probe the        | Whether to check the availability of the monitoring before adding a monitoring is successful, and the new modification operation will continue only if the probe is successful |
+| Description Comment         | For more information identifying and describing the remarks for this monitoring, users can remark the information here                                                         |
 
 ### Collect metrics
 

home/docs/help/status.md

@@ -16,7 +16,7 @@ The fields that need to be filled in are as follows:
 |        Field Name        |                                Field Description                                 |                                                                                                                                   Example                                                                                                                                    |
 |--------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Organization Name        | Name of the organization                                                         | HertzBeat                                                                                                                                                                                                                                                                    |
-| Organization Description | Detailed description of the organization                                         | Apache HertzBeat (incubating) is an easy-to-use and user-friendly open-source real-time monitoring and alerting system, no agent required, high-performance cluster, compatible with Prometheus, providing powerful custom monitoring and status page building capabilities. |
+| Organization Description | Detailed description of the organization                                         | Apache HertzBeat is an easy-to-use and user-friendly open-source real-time monitoring and alerting system, no agent required, high-performance cluster, compatible with Prometheus, providing powerful custom monitoring and status page building capabilities. |
 | Website Link             | URL of the organization's website for more information                           | <https://hertzbeat.apache.org/>                                                                                                                                                                                                                                                |
 | Logo Image               | Path or URL of the organization's official logo image, preferably in .svg format | <https://hertzbeat.apache.org/zh-cn/img/hertzbeat-logo.svg>                                                                                                                                                                                                                    |
 | Feedback Address         | Address to receive feedback                                                      | <https://github.com/apache/hertzbeat/issues>                                                                                                                                                                                                                                   |

home/docs/introduce.md

@@ -1,6 +1,6 @@
 ---
 id: introduce
-title: Apache HertzBeat (incubating)
+title: Apache HertzBeat
 sidebar_label: Introduce
 slug: /
 ---
@@ -11,7 +11,7 @@ slug: /
 
 ## 🎡 <font color="green">Introduction</font>
 
-[Apache HertzBeat](https://github.com/apache/hertzbeat) (incubating) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.
+[Apache HertzBeat](https://github.com/apache/hertzbeat) is an easy-to-use, open source, real-time monitoring system with agentless, high performance cluster, prometheus-compatible, offers powerful custom monitoring and status page building capabilities.
 
 ### Features
 

home/docs/start/account-modify.md

@@ -6,7 +6,7 @@ sidebar_label: Update Account Secret
 
 ## Update Account
 
-Apache HertzBeat (incubating) default built-in three user accounts, respectively admin/hertzbeat tom/hertzbeat guest/hertzbeat
+Apache HertzBeat default built-in three user accounts, respectively admin/hertzbeat tom/hertzbeat guest/hertzbeat
 If you need add, delete or modify account or password, configure `sureness.yml`. Ignore this step without this demand.
 Modify the following **part parameters** in sureness.yml：**[Note⚠️Other default sureness configuration parameters should be retained]**
 
@@ -56,7 +56,6 @@ resourceRole:
 # rule: api===method 
 # eg: /api/v1/source3===get means /api/v1/source3===get can be access by anyone, no need auth.
 excludedResource:
-  - /api/alerts/report/**===*
   - /api/account/auth/**===*
   - /api/i18n/**===get
   - /api/apps/hierarchy===get

home/docs/start/baota-deploy.md

@@ -4,7 +4,7 @@ title: Use aaPanel Deploy HertzBeat
 sidebar_label: Install via aaPanel
 ---
 
-Apache HertzBeat (incubating) supports one-click deployment in the `Docker` application store of the aaPanel.
+Apache HertzBeat supports one-click deployment in the `Docker` application store of the aaPanel.
 
 ## Prerequisites
 

home/docs/start/docker-compose-deploy.md

@@ -15,13 +15,13 @@ Run the `docker compose version` command to check if you have a Docker Compose e
 
 1. Download the startup script package
 
-   Download the installation script package `apache-hertzbeat-xxx-incubating-docker-compose.tar.gz` from the [download](/docs/download)
+   Download the installation script package `apache-hertzbeat-xxx-docker-compose.tar.gz` from the [download](/docs/download)
 
 2. Choose to use the HertzBeat + PostgreSQL + VictoriaMetrics solution
 
    :::tip
 
-   - `apache-hertzbeat-xxx-incubating-docker-compose.tar.gz` contains multiple deployment solutions after decompression. Here we recommend choosing the `hertzbeat-postgresql-victoria-metrics` solution.
+   - `apache-hertzbeat-xxx-docker-compose.tar.gz` contains multiple deployment solutions after decompression. Here we recommend choosing the `hertzbeat-postgresql-victoria-metrics` solution.
    - Other deployment methods, please read the README.md file of each deployment solution in detail. The MySQL solution requires you to prepare the MySQL driver package yourself.
 
    :::
@@ -29,13 +29,13 @@ Run the `docker compose version` command to check if you have a Docker Compose e
    - Unzip the script package
 
    ```shell
-   tar zxvf apache-hertzbeat-1.6.0-incubating-docker-compose.tar.gz
+   tar zxvf apache-hertzbeat-1.6.0-docker-compose.tar.gz
    ```
 
    - Enter the decompression directory and select `HertzBeat + PostgreSQL + VictoriaMetrics` for one-click deployment
 
    ```shell
-   cd apache-hertzbeat-1.6.0-incubating-docker-compose    
+   cd apache-hertzbeat-1.6.0-docker-compose    
    cd hertzbeat-postgresql-victoria-metrics
    ```
 

home/docs/start/greptime-init.md

@@ -4,7 +4,7 @@ title: Use Time Series Database Greptime to Store Metrics Data (Recommended)
 sidebar_label: Metrics Store Greptime (Recommended)
 ---
 
-Apache HertzBeat (incubating)'s historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
+Apache HertzBeat's historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
 
 > It is recommended to use Greptime as metrics storage.
 

home/docs/start/influxdb-init.md

@@ -4,7 +4,7 @@ title: Use Time Series Database InfluxDB to Store Metrics Data (Optional)
 sidebar_label: Metrics Store InfluxDB
 ---
 
-Apache HertzBeat (incubating)'s historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
+Apache HertzBeat's historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
 
 > It is recommended to use VictoriaMetrics as metrics storage.
 

home/docs/start/iotdb-init.md

@@ -4,7 +4,7 @@ title: Use Time Series Database IoTDB to Store Metrics Data (Optional)
 sidebar_label: Metrics Store IoTDB
 ---
 
-Apache HertzBeat (incubating)'s historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
+Apache HertzBeat's historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
 
 > It is recommended to use VictoriaMetrics as metrics storage.
 

home/docs/start/mysql-change.md

@@ -4,7 +4,7 @@ title: Use MYSQL Replace H2 Database to Store Metadata(Optional)
 sidebar_label: Meta Store MYSQL
 ---
 
-MYSQL is a reliable relational database. In addition to default built-in H2 database, Apache HertzBeat (incubating) allow you to use MYSQL to store structured relational data such as monitoring information, alarm information and configuration information.
+MYSQL is a reliable relational database. In addition to default built-in H2 database, Apache HertzBeat allow you to use MYSQL to store structured relational data such as monitoring information, alarm information and configuration information.
 
 > If you already have a MySQL environment and the MySQL version meets the requirements, you can skip directly to the database creation step.
 

home/docs/start/package-deploy.md

@@ -5,7 +5,7 @@ sidebar_label: Install via Package
 ---
 
 :::tip
-You can install and run Apache HertzBeat (incubating) on Linux Windows Mac system, and CPU supports X86/ARM64.
+You can install and run Apache HertzBeat on Linux Windows Mac system, and CPU supports X86/ARM64.
 Since version 1.6.0 uses `Java 17` and the installation package no longer provides a built-in JDK version, use the new Hertzbeat according to the following situations:
 
 - When the default environment variable on your server is `Java 17`, you do not need to take any action for this step.
@@ -18,7 +18,7 @@ Since version 1.6.0 uses `Java 17` and the installation package no longer provid
 
 1. Download installation package
 
-   Download installation package `apache-hertzbeat-xxx-incubating-bin.tar.gz` corresponding to your system environment
+   Download installation package `apache-hertzbeat-xxx-bin.tar.gz` corresponding to your system environment
    - [Download Page](/docs/download)
 
 2. Configure HertzBeat's configuration file(optional)
@@ -26,7 +26,7 @@ Since version 1.6.0 uses `Java 17` and the installation package no longer provid
    Unzip the installation package to the host eg: /opt/hertzbeat
 
    ```shell
-   tar zxvf apache-hertzbeat-xxx-incubating-bin.tar.gz
+   tar zxvf apache-hertzbeat-xxx-bin.tar.gz
    ```
 
    :::tip
@@ -68,7 +68,7 @@ Deploying multiple HertzBeat Collectors can achieve high availability, load bala
 
 1. Download installation package
 
-   Download installation package `apache-hertzbeat-collector-xxx-incubating-bin.tar.gz` corresponding to your system environment
+   Download installation package `apache-hertzbeat-collector-xxx-bin.tar.gz` corresponding to your system environment
    - [Download Page](/docs/download)
 
 2. Configure the collector configuration file
@@ -76,7 +76,7 @@ Deploying multiple HertzBeat Collectors can achieve high availability, load bala
    Unzip the installation package to the host eg: /opt/hertzbeat-collector
 
    ```shell
-   tar zxvf apache-hertzbeat-collector-xxx-incubating-bin.tar.gz
+   tar zxvf apache-hertzbeat-collector-xxx-bin.tar.gz
    ```
 
    Configure the collector configuration yml file `config/application.yml`: unique `identity` name, running `mode` (public or private), hertzbeat `manager-host`, hertzbeat `manager-port`

home/docs/start/postgresql-change.md

@@ -4,7 +4,7 @@ title: Use PostgreSQL Replace H2 Database to Store Metadata(Recommended)
 sidebar_label: Meta Store PostgreSQL (Recommended)
 ---
 
-PostgreSQL is a RDBMS emphasizing extensibility and SQL compliance. In addition to default built-in H2 database, Apache HertzBeat (incubating) allow you to use PostgreSQL to store structured relational data such as monitoring information, alarm information and configuration information.
+PostgreSQL is a RDBMS emphasizing extensibility and SQL compliance. In addition to default built-in H2 database, Apache HertzBeat allow you to use PostgreSQL to store structured relational data such as monitoring information, alarm information and configuration information.
 
 > If you have the PostgreSQL environment, can be directly to database creation step.
 

home/docs/start/quickstart.md

@@ -6,11 +6,11 @@ sidebar_label: Quick Start
 
 ### 🐕 Quick Start
 
-- If you wish to deploy Apache HertzBeat (incubating) locally, please refer to the following Deployment Documentation for instructions.
+- If you wish to deploy Apache HertzBeat locally, please refer to the following Deployment Documentation for instructions.
 
 #### 🍞 Install HertzBeat
 
-> Apache HertzBeat (incubating) supports installation through source code, docker or package, cpu support X86/ARM64.
+> Apache HertzBeat supports installation through source code, docker or package, cpu support X86/ARM64.
 
 ##### 1：Install quickly via docker
 

home/docs/start/rainbond-deploy.md

@@ -4,7 +4,7 @@ title: Use Rainbond Deploy HertzBeat
 sidebar_label: Install via Rainbond
 ---
 
-If you are unfamiliar with Kubernetes, and want to install Apache HertzBeat (incubating) in Kubernetes, you can use Rainbond to deploy. Rainbond is a cloud-native application management platform built on Kubernetes and simplifies the application deployment to Kubernetes.
+If you are unfamiliar with Kubernetes, and want to install Apache HertzBeat in Kubernetes, you can use Rainbond to deploy. Rainbond is a cloud-native application management platform built on Kubernetes and simplifies the application deployment to Kubernetes.
 
 ## Rainbond Cloud deployment
 

home/docs/start/tdengine-init.md

@@ -4,7 +4,7 @@ title: Use Time Series Database TDengine to Store Metrics Data (Optional)
 sidebar_label: Metrics Store TDengine
 ---
 
-Apache HertzBeat (incubating)'s historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
+Apache HertzBeat's historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
 
 > It is recommended to use VictoriaMetrics as metrics storage.
 

home/docs/start/upgrade.md

@@ -10,7 +10,7 @@ sidebar_label: Version Upgrade Guide
 - [Github Release](https://github.com/apache/hertzbeat/releases)
 - [DockerHub Release](https://hub.docker.com/r/apache/hertzbeat/tags)
 
-Apache HertzBeat (incubating)'s metadata information is stored in H2 or Mysql, PostgreSQL relational databases, and the collected metric data is stored in time series databases such as TDengine and IotDB.
+Apache HertzBeat's metadata information is stored in H2 or Mysql, PostgreSQL relational databases, and the collected metric data is stored in time series databases such as TDengine and IotDB.
 
 **You need to save and back up the data files of the database and monitoring templates yml files before upgrading**
 

home/docs/start/usecase/linux-os-practice.md

@@ -30,7 +30,7 @@ The production environment recommends a complete deployment method, refer [Insta
 
 ### 1. Click Add Linux Operating System Monitor
 
-> HertzBeat Page -> Monitors Menu -> New Monitor -> OS Monitor -> Add OS Linux
+> HertzBeat Page -> Monitors -> New Monitor -> OS Monitor -> Add OS Linux
 
 ![HertzBeat](/img/docs/start/linux-os-practice-1.png)
 

home/docs/start/usecase/springboot-auto-practice.md

@@ -14,7 +14,7 @@ This article introduces an integrated solution using the HertzBeat monitoring sy
 
 ## What is HertzBeat
 
-Apache HertzBeat (incubating) is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, PING connectivity, port availability, database, operating system, middleware, API monitoring, threshold alarms, alarm notification (email, WeChat, Ding Ding Feishu).
+Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, PING connectivity, port availability, database, operating system, middleware, API monitoring, threshold alarms, alarm notification (email, WeChat, Ding Ding Feishu).
 
 **github: <https://github.com/apache/hertzbeat>**
 

home/docs/start/usecase/sslcert-practice.md

@@ -12,7 +12,7 @@ This article introduces how to use the hertzbeat monitoring tool to detect the v
 
 ## What is HertzBeat
 
-Apache HertzBeat (incubating) is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, PING connectivity, port availability, database, operating system, middleware, API monitoring, threshold alarms, alarm notification (email, WeChat, Ding Ding Feishu).
+Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, PING connectivity, port availability, database, operating system, middleware, API monitoring, threshold alarms, alarm notification (email, WeChat, Ding Ding Feishu).
 
 github: <https://github.com/apache/hertzbeat>
 
@@ -32,7 +32,7 @@ The production environment recommends a complete deployment method, refer <https
 
 1. Click Add SSL Certificate Monitor
 
-    > HertzBeat Page -> Monitors Menu -> New Monitor -> Service Monitor -> Add SSL Certificate
+    > HertzBeat Page -> Monitors -> New Monitor -> Service Monitor -> Add SSL Certificate
 
     ![HertzBeat](/img/docs/start/ssl_1.png)
 

home/docs/start/victoria-metrics-init.md

@@ -4,7 +4,7 @@ title: Use Time Series Database VictoriaMetrics to Store Metrics Data (Recommend
 sidebar_label: Metrics Store VictoriaMetrics (Recommended)
 ---
 
-Apache HertzBeat (incubating)'s historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
+Apache HertzBeat's historical data storage relies on the time series database, you can choose one of them to install and initialize, or not to install (note ⚠️ but it is strongly recommended to configure in the production environment)
 
 > It is recommended to use VictoriaMetrics as metrics storage.