Merge branch 'master' into doc-graduate

[bugfix] fixed jexl keyword issue in spring_gateway monitoring template (#3693 )
2026-09-17 18:19:02 +00:00 · 2025-08-22 01:12:18 +08:00 · 2025-08-22 01:12:04 +08:00 · 2025-08-22 00:41:49 +08:00 · 2025-08-22 00:39:17 +08:00 · 2025-08-22 00:36:09 +08:00
173 changed files with 898 additions and 592 deletions
@@ -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
@@ -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.
@@ -1,4 +1,4 @@
-Apache HertzBeat (incubating)
+Apache HertzBeat
 Copyright 2024-2025 The Apache Software Foundation

 This product includes software developed at
@@ -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

@@ -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，提供强大的自定义监控和状态页构建能力。     

 ### 特点

@@ -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-->
@@ -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
@@ -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
@@ -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^_^
@@ -651,7 +651,7 @@ metrics:
          zh-CN: 次数
          en-US: Num
          ja-JP: 数量
-      - field: size
+      - field: Size
        type: 0
        unit: B
        i18n:
@@ -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
@@ -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^_^
@@ -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
@@ -22,7 +22,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

@@ -8,9 +8,9 @@ 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 +23,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

@@ -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).

@@ -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.
@@ -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:
@@ -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.

@@ -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
 ```
@@ -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
@@ -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

@@ -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

@@ -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>                                                                                                                                                                                                                                   |
@@ -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

@@ -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]**

@@ -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

@@ -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
   ```

@@ -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.

@@ -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.

@@ -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.

@@ -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.

@@ -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`
@@ -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.

@@ -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

@@ -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

@@ -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.

@@ -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**

@@ -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>**

@@ -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>

@@ -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.

@@ -4,7 +4,7 @@ title: Monitoring Template Here
 sidebar_label: Monitoring Template
 ---

-> Apache HertzBeat (incubating) is an open source, real-time monitoring tool with custom-monitor and agentLess.
+> Apache HertzBeat is an open source, real-time monitoring tool with custom-monitor and agentLess.
 >
 > We make protocols such as `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` configurable, and you only need to configure `YML` online to collect any metrics you want.
 > Do you believe that you can immediately adapt a new monitoring type such as K8s or Docker just by configuring online?
@@ -2,7 +2,7 @@ const path = require('path')

 const organizationName = 'apache' // Usually your GitHub name.
 const projectName = 'hertzbeat' // Usually your repo name.
-const deploymentBranch = 'asf-site' 
+const deploymentBranch = 'asf-site'
 const branch = 'master'
 const repoUrl = `https://github.com/apache/${projectName}`
 const cdnUrl = null
@@ -16,8 +16,8 @@ module.exports = {
  onBrokenMarkdownLinks: 'throw',
  favicon: '/img/hertzbeat-logo.svg',
  organizationName,
-  projectName, 
-  deploymentBranch,  
+  projectName,
+  deploymentBranch,
  customFields: {
    repoUrl,
    cdnUrl,
@@ -206,22 +206,22 @@ module.exports = {
        {
          type: 'localeDropdown',
          position: 'right',
-        }, 
+        },
        {
          href: repoUrl,
          position: 'right',
          className: 'header-github-link'
-        }, 
+        },
        {
          href: 'https://x.com/hertzbeat1024',
          position: 'right',
          className: 'header-twitter-link'
-        }, 
+        },
        {
          href: 'https://www.youtube.com/channel/UCri75zfWX0GHqJFPENEbLow',
          position: 'right',
          className: 'header-youtube-link'
-        }, 
+        },
        {
          href: 'https://discord.gg/Fb6M73htGr',
          position: 'right',
@@ -263,13 +263,13 @@
    "message": "Makes protocols such as Http, Jmx, Ssh, Snmp, Jdbc configurable, you can collect any metrics by simply configuring the yml online. {br} High performance, supports horizontal expansion of multi-collector clusters, multi-isolated network monitoring and cloud-edge collaboration. {br} Flexible threshold rules and timely notifications delivered via discord slack email webhook more."
  },
  "opensource-content": {
-    "message": "Apache HertzBeat (incubating) is open source, has an inclusive and open community. Unlimited and anyone who are interested in it are very welcome to contribute. No matter how small the contribution is, whether it is a code document or a typo, respect everyone and grow together. {br} Our code is being deployed on thousands of machines worldwide.{github}"
+    "message": "Apache HertzBeat is open source, has an inclusive and open community. Unlimited and anyone who are interested in it are very welcome to contribute. No matter how small the contribution is, whether it is a code document or a typo, respect everyone and grow together. {br} Our code is being deployed on thousands of machines worldwide.{github}"
  },
  "slogan": {
    "message": "Open Source Real-time Monitoring System"
  },
  "Who uses HertzBeat?": {
-    "message": "Who uses Apache HertzBeat (incubating)?"
+    "message": "Who uses Apache HertzBeat?"
  },
  "theme.admonition.note": {
    "message": "note",
@@ -490,7 +490,7 @@
    "description": "The title of the tag list page"
  },
  "team.name": {
-    "message": "Apache HertzBeat (incubating) Team"
+    "message": "Apache HertzBeat Team"
  },
  "team.desc": {
    "message": "The HertzBeat team is composed of contributors from various fields around the world. We embrace the community philosophy of openness and collaboration, welcoming👏 more people to join us and grow together with the community."
@@ -437,7 +437,7 @@
    "message": "将 Http,Jmx,Ssh,Snmp,Jdbc 等协议规范可配置模板化，只需在线配置YML就可自定义监控指标。{br} 高性能，支持多采集器集群横向扩展，支持多隔离网络监控，云边协同。{br}灵活的告警阈值规则，邮箱，短信，钉钉，企业微信，飞书，Webhook等消息及时送达。{br} 您相信只需配置下就能适配新K8s监控类型吗？"
  },
  "opensource-content": {
-    "message": "Apache HertzBeat (incubating) 是开源的，拥有一个包容开放的社区。{br}欢迎任何对此有兴趣的同学参与其中，无论是代码文档或者错别字，尊重社区的每一位，一起进步成长。{br}我们的代码正被部署到全球成千上万机器上。{github}"
+    "message": "Apache HertzBeat 是开源的，拥有一个包容开放的社区。{br}欢迎任何对此有兴趣的同学参与其中，无论是代码文档或者错别字，尊重社区的每一位，一起进步成长。{br}我们的代码正被部署到全球成千上万机器上。{github}"
  },
  "slogan": {
    "message": "易用友好的开源实时监控系统"
@@ -464,7 +464,7 @@
    "message": "快速开始"
  },
  "Who uses HertzBeat?": {
-    "message": "谁在使用 Apache HertzBeat (incubating)"
+    "message": "谁在使用 Apache HertzBeat"
  },
  "Support HertzBeat": {
    "message": "Support HertzBeat"
@@ -493,7 +493,7 @@
    "description": "The title of the tag list page"
  },
  "team.name": {
-    "message": "Apache HertzBeat (incubating) 团队"
+    "message": "Apache HertzBeat 团队"
  },
  "team.desc": {
    "message": "HertzBeat 团队由来自全球各个领域的贡献者组成。践行 开放，协作 的社区理念，欢迎👏更多的人加入我们，和社区一同成长。"
@@ -8,9 +8,9 @@ tags: [opensource, practice]
 keywords: [open source, monitoring, alerting]
 ---

-**Hi 朋友们，我们很高兴地宣布，Apache HertzBeat (incubating) 的了第一个Apache版本 v1.6.0 发布啦！🎉.**
+**Hi 朋友们，我们很高兴地宣布，Apache HertzBeat 的了第一个Apache版本 v1.6.0 发布啦！🎉.**

-经过近五个月的社区开发迭代贡献和两个月的Apache Incubator孵化过程，Apache HertzBeat (incubating) v1.6.0 终于出来了。
+经过近五个月的社区开发迭代贡献和两个月的Apache Incubator孵化过程，Apache HertzBeat v1.6.0 终于出来了。
 这个版本我们增加了对OpenAi监控，Redfish协议服务器，插件机制，支持了NebulaGraph, Apache Yarn, HDFS, Hbase, Storm等更多功能特性。
 由于License兼容问题，我们在底层替换了ORM框架，计算框架等多个依赖，Hibernate -> EclipseLink, 这也算是JPA生态下为数不多的迁移踩坑实践。
 同时修复了一些bug和优化了一些功能，更完善的文档。欢迎大家尝试使用，提出宝贵意见和建议，共同推动HertzBeat的发展。🎉
@@ -4,7 +4,7 @@ title: HTTP协议系统默认解析方式
 sidebar_label: 系统默认解析方式
 ---

-> HTTP接口调用获取响应数据后，用 Apache HertzBeat (incubating) 默认的解析方式去解析响应数据。
+> HTTP接口调用获取响应数据后，用 Apache HertzBeat 默认的解析方式去解析响应数据。

 **此需接口响应数据结构符合HertzBeat指定的数据结构规则**

@@ -4,7 +4,7 @@ title: 教程一:适配一款基于HTTP协议的监控类型
 sidebar_label: 教程一:适配一款HTTP协议监控
 ---

-通过此教程我们一步一步描述如何在 Apache HertzBeat (incubating) 监控系统下新增适配一款基于http协议的监控类型。
+通过此教程我们一步一步描述如何在 Apache HertzBeat 监控系统下新增适配一款基于http协议的监控类型。

 阅读此教程前我们希望您已经从[自定义监控](extend-point)和[http协议自定义](extend-http)了解熟悉了怎么自定义类型，指标，协议等。

@@ -8,7 +8,7 @@ sidebar_label: JsonPath解析方式

 注意⚠️ 响应数据为JSON格式

-**使用JsonPath脚本将响应数据解析成符合 Apache HertzBeat (incubating) 指定的数据结构规则的数据**
+**使用JsonPath脚本将响应数据解析成符合 Apache HertzBeat 指定的数据结构规则的数据**

 #### JsonPath操作符

@@ -4,7 +4,7 @@ title: 自定义适配一款基于HTTP协议的新监控类型
 sidebar_label: 教程案例
 ---

-通过此教程我们一步一步描述如何在 Apache HertzBeat (incubating) 系统下自定义新增适配一款基于 http 协议的监控类型。
+通过此教程我们一步一步描述如何在 Apache HertzBeat 系统下自定义新增适配一款基于 http 协议的监控类型。

 阅读此教程前我们希望您已经从[自定义监控](extend-point)和[http协议自定义](extend-http)了解熟悉了怎么自定义类型，指标，协议等。

@@ -350,13 +350,13 @@ svn commit -m "release for HertzBeat 1.6.0-RC1"
 发送社区投票邮件需要至少三个`+1`，且无`-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!
 在72小时后，将统计投票结果，并发送投票结果邮件，如下所示。

 > `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 @@ ChunJin Mu
 发送孵化社区投票邮件需要至少三个`+1`，且无`-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
 然后将统计投票结果，并发送投票结果邮件，如下所示。

 > `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 @@ release note: xxx

 > `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.
@@ -110,9 +110,7 @@ tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz

 进行如下检查：

- [ ] 文件夹包含单词`incubating`
 - [ ] 存在`LICENSE`和`NOTICE`文件
- [ ] 存在`DISCLAIMER`或`DISCLAIMER-WIP`文件
 - [ ] `NOTICE`文件中的年份正确
 - [ ] 所有文本文件开头都有ASF许可证
 - [ ] 检查第三方依赖许可证：
@@ -136,9 +134,7 @@ cd apache-hertzbeat-${release_version}-incubating-src
 进行如下检查:

 - [ ] 检查源码包是否包含由于包含不必要文件，致使tar包过于庞大
- [ ] 文件夹包含单词`incubating`
 - [ ] 存在`LICENSE`和`NOTICE`文件
- [ ] 存在`DISCLAIMER`或`DISCLAIMER-WIP`文件
 - [ ] `NOTICE`文件中的年份正确
 - [ ] 只存在文本文件，不存在二进制文件
 - [ ] 所有文件的开头都有ASF许可证
@@ -270,7 +270,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.

@@ -281,5 +281,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
 ```
@@ -1,10 +1,10 @@
 ---
 id: download
-title: 下载 Apache HertzBeat (incubating)
+title: 下载 Apache HertzBeat
 sidebar_label: Download
 ---

-> **这里是 Apache HertzBeat (incubating) 官方下载页面。**
+> **这里是 Apache HertzBeat 官方下载页面。**
 > **请在下方表中选择版本下载，推荐使用最新版本。**

 :::tip
@@ -1,15 +1,15 @@
 ---
 id: spring_gateway
-Title: 监控 Spring Gateway
-sidebar_label: Spring Gateway
-keywords: [开源监控工具, 开源 Spring Gateway 监控工具, 监控 Spring Gateway 指标]
+Title: 监控 Spring Cloud Gateway
+sidebar_label: Spring Cloud Gateway
+keywords: [开源监控工具, 开源 Spring Cloud Gateway 监控工具, 监控 Spring Cloud Gateway 指标]
 ---

 > 收集和监控 SpringBoot Actuator 提供的常规性能指标。

 ## 监控前操作

-如果您想使用此监控类型监控 'Spring Gateway' 的信息，您需要集成您的 SpringBoot 应用程序并启用 SpringBoot Actuator。
+如果您想使用此监控类型监控 `Spring Cloud Gateway` 的信息，您需要集成您的 `Spring Cloud Gateway` 应用程序并启用 SpringBoot Actuator。

 **1、添加 POM .XML 依赖:**

@@ -26,24 +26,25 @@ keywords: [开源监控工具, 开源 Spring Gateway 监控工具, 监控 Spring
 management:
  endpoint:
    gateway:
-      enabled: true # default value
+      enabled: true
+    env:
+      show-values: ALWAYS
  endpoints:
    web:
      exposure:
-        include: '*'
-    enabled-by-default: on
+        include: "*"
 ```

 ### 配置参数

-|   参数名称   |                          参数描述                          |
-|----------|--------------------------------------------------------|-----------------------------------------------|
+| 参数名称     | 参数描述                                                   |
+|----------|--------------------------------------------------------|
 | 监控主机     | 被监控的目标 IPV4、IPV6 或域名。注意⚠️不要包含协议头（例如：https://，http://）。 |
 | 监控名称     | 用于标识此监控的名称，需要保证唯一性。                                    |
 | 端口       | 数据库提供的默认端口为 8080。                                      |
 | 启用 HTTPS | 是否通过 HTTPS 访问网站，请注意⚠️当启用 HTTPS 时，需要将默认端口更改为 443        |
 | 采集间隔     | 监控周期性采集数据的时间间隔，单位为秒，最小间隔为 30 秒。                        |
-| 是否探测     | 在新增监控前是否先进行可用性探测，只有探测成功才会继续新增或修改操作。                    | will continue only if the probe is successful |
+| 是否探测     | 在新增监控前是否先进行可用性探测，只有探测成功才会继续新增或修改操作。                    | 
 | 描述备注     | 用于添加关于监控的额外标识和描述信息。                                    |

 ### 采集指标
@@ -16,7 +16,7 @@ keywords: [开源监控系统, 开源网站监控, 状态页面]
 | 字段名称 |                  字段说明                  |                                                举例                                                 |
 |------|----------------------------------------|---------------------------------------------------------------------------------------------------|
 | 组织名称 | 组织的名称                                  | HertzBeat                                                                                         |
-| 组织介绍 | 组织的详细介绍                                | Apache HertzBeat (incubating) 是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。 |
+| 组织介绍 | 组织的详细介绍                                | Apache HertzBeat 是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。 |
 | 网站链接 | 组织网站的 URL，便于访问者获取更多信息                  | <https://hertzbeat.apache.org/>                                                                     |
 | 标志图片 | 组织官方标志或 Logo 的图片文件路径或 URL，建议使用 .svg 格式 | <https://hertzbeat.apache.org/zh-cn/img/hertzbeat-logo.svg>                                         |
 | 反馈地址 | 接收问题反馈的地址                              | <https://github.com/apache/hertzbeat/issues>                                                        |
@@ -1,6 +1,6 @@
 ---
 id: introduce  
-title: Apache HertzBeat (incubating)     
+title: Apache HertzBeat     
 sidebar_label: 介绍
 slug: /
 ---
@@ -6,7 +6,7 @@ sidebar_label: 更新账户和密钥

 ## 更新账户

-Apache HertzBeat (incubating) 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat
+Apache HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat
 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤
 修改位于安装目录下的 `/hertzbeat/config/sureness.yml` 的配置文件，docker环境目录为`opt/hertzbeat/config/sureness.yml`，建议提前挂载映射
 配置文件内容参考如下
@@ -4,7 +4,7 @@ title: 使用 宝塔面板 部署 HertzBeat
 sidebar_label: 基于宝塔面板部署
 ---

-Apache HertzBeat (incubating) 支持在宝塔面板的 `Docker` 应用商店一键部署。
+Apache HertzBeat 支持在宝塔面板的 `Docker` 应用商店一键部署。

 ## 前提

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务 Greptime 安装初始化 (推荐)
 sidebar_label: 指标数据存储 Greptime (推荐)
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 Greptime 作为存储。

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务InfluxDB安装初始化(可选)
 sidebar_label: 指标数据存储InfluxDB
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务IoTDB安装初始化(可选)
 sidebar_label: 指标数据存储IoTDB
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 关系型数据库使用 Mysql 替换依赖的 H2 存储系统元数据(
 sidebar_label: 元数据存储Mysql
 ---

-MYSQL是一款值得信赖的关系型数据库，Apache HertzBeat (incubating) 除了支持使用默认内置的H2数据库外，还可以切换为使用MYSQL存储监控信息，告警信息，配置信息等结构化关系数据。
+MYSQL是一款值得信赖的关系型数据库，Apache HertzBeat 除了支持使用默认内置的H2数据库外，还可以切换为使用MYSQL存储监控信息，告警信息，配置信息等结构化关系数据。

 注意⚠️ 使用外置MySQL数据库替换内置H2数据库为可选项，但建议生产环境配置，以提供更好的性能

@@ -5,7 +5,7 @@ sidebar_label: 安装包方式安装
 ---

 :::tip
-Apache HertzBeat (incubating) 支持在Linux Windows Mac系统安装运行，CPU支持X86/ARM64。
+Apache HertzBeat 支持在Linux Windows Mac系统安装运行，CPU支持X86/ARM64。
 由于1.6.0及以后版本使用 `Java 17` ，且安装包不再提供内置jdk的版本，参考以下情况使用新版Hertzbeat。

 - 当你的服务器中默认环境变量为 `Java 17` 时，这一步你无需任何操作。
@@ -4,7 +4,7 @@ title: 关系型数据库使用 PostgreSQL 替换依赖的 H2 存储系统元数
 sidebar_label: 元数据存储PostgreSQL(推荐)
 ---

-PostgreSQL 是一个功能强大，开源的关系型数据库管理系统（RDBMS）。Apache HertzBeat (incubating) 除了支持使用默认内置的 H2 数据库外，还可以切换为使用 PostgreSQL 存储监控信息，告警信息，配置信息等结构化关系数据。
+PostgreSQL 是一个功能强大，开源的关系型数据库管理系统（RDBMS）。Apache HertzBeat 除了支持使用默认内置的 H2 数据库外，还可以切换为使用 PostgreSQL 存储监控信息，告警信息，配置信息等结构化关系数据。

 注意⚠️ 使用外置 PostgreSQL 数据库替换内置 H2 数据库为可选项，但建议生产环境配置，以提供更好的性能

@@ -6,7 +6,7 @@ sidebar_label: 快速开始

 ### 🐕 开始使用

- 如果您是想将 Apache HertzBeat (incubating) 部署到本地搭建监控系统，请参考下面的部署文档进行操作。
+- 如果您是想将 Apache HertzBeat 部署到本地搭建监控系统，请参考下面的部署文档进行操作。

 ### 🍞 HertzBeat安装

@@ -4,7 +4,7 @@ title: 使用 Rainbond 部署 HertzBeat
 sidebar_label: 基于Rainbond部署
 ---

-如果你不熟悉 Kubernetes，想在 Kubernetes 中安装 Apache HertzBeat (incubating)，可以使用 Rainbond 来部署。Rainbond 是一个基于 Kubernetes 构建的云原生应用管理平台，可以很简单的将你的应用部署到 Kubernetes中。
+如果你不熟悉 Kubernetes，想在 Kubernetes 中安装 Apache HertzBeat，可以使用 Rainbond 来部署。Rainbond 是一个基于 Kubernetes 构建的云原生应用管理平台，可以很简单的将你的应用部署到 Kubernetes中。

 ## Rainbond Cloud 部署

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务TDengine安装初始化(可选)
 sidebar_label: 指标数据存储TDengine
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: HertzBeat 新版本更新指引
 sidebar_label: 版本更新指引
 ---

-**Apache HertzBeat (incubating) 的发布版本列表**
+**Apache HertzBeat 的发布版本列表**

 - [下载页面](https://hertzbeat.apache.org/docs/download)
 - [Github Release](https://github.com/apache/hertzbeat/releases)
@@ -14,7 +14,7 @@ sidebar_label: SpringBoot Web应用监控案例

 ## HertzBeat 是什么

-Apache HertzBeat (incubating) 一个拥有强大自定义监控能力，无需Agent的实时监控工具。网站监测，PING连通性，端口可用性，数据库，操作系统，中间件，API监控，阈值告警，告警通知(邮件微信钉钉飞书)。
+Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时监控工具。网站监测，PING连通性，端口可用性，数据库，操作系统，中间件，API监控，阈值告警，告警通知(邮件微信钉钉飞书)。

 **github: <https://github.com/apache/hertzbeat>**

@@ -12,7 +12,7 @@ sidebar_label: SSL 证书过期监控案例

 ## HertzBeat 是什么

-Apache HertzBeat (incubating) 一个拥有强大自定义监控能力，无需Agent的实时监控工具。网站监测，PING连通性，端口可用性，数据库，操作系统，中间件，API监控，阈值告警，告警通知(邮件微信钉钉飞书)。
+Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时监控工具。网站监测，PING连通性，端口可用性，数据库，操作系统，中间件，API监控，阈值告警，告警通知(邮件微信钉钉飞书)。

 github: <https://github.com/apache/hertzbeat>

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务VictoriaMetrics安装初始化
 sidebar_label: 指标数据存储VictoriaMetrics(推荐)
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 监控模板中心
 sidebar_label: 监控模板
 ---

-> Apache HertzBeat (incubating) 是一个拥有强大自定义监控能力，无需 Agent 的开源实时监控告警工具。
+> Apache HertzBeat 是一个拥有强大自定义监控能力，无需 Agent 的开源实时监控告警工具。
 >
 > 我们将`Http, Jmx, Ssh, Snmp, Jdbc, Prometheus`等协议规范可配置化，您只需在浏览器配置`YML`就能使用这些协议去自定义采集任何您想要的指标。
 > 您相信只需简单配置即可快速适配一款`K8s`或`Docker`等新的监控类型吗？
@@ -4,7 +4,7 @@ title: HTTP协议系统默认解析方式
 sidebar_label: 系统默认解析方式
 ---

-> HTTP接口调用获取响应数据后，用 Apache HertzBeat (incubating) 默认的解析方式去解析响应数据。
+> HTTP接口调用获取响应数据后，用 Apache HertzBeat 默认的解析方式去解析响应数据。

 **此需接口响应数据结构符合HertzBeat指定的数据结构规则**

@@ -4,7 +4,7 @@ title: 教程一:适配一款基于HTTP协议的监控类型
 sidebar_label: 教程一:适配一款HTTP协议监控
 ---

-通过此教程我们一步一步描述如何在 Apache HertzBeat (incubating) 监控系统下新增适配一款基于http协议的监控类型。
+通过此教程我们一步一步描述如何在 Apache HertzBeat 监控系统下新增适配一款基于http协议的监控类型。

 阅读此教程前我们希望您已经从[自定义监控](extend-point)和[http协议自定义](extend-http)了解熟悉了怎么自定义类型，指标，协议等。

@@ -8,7 +8,7 @@ sidebar_label: JsonPath解析方式

 注意⚠️ 响应数据为JSON格式

-**使用JsonPath脚本将响应数据解析成符合 Apache HertzBeat (incubating) 指定的数据结构规则的数据**
+**使用JsonPath脚本将响应数据解析成符合 Apache HertzBeat 指定的数据结构规则的数据**

 #### JsonPath操作符

@@ -4,7 +4,7 @@ title: 自定义适配一款基于HTTP协议的新监控类型
 sidebar_label: 教程案例
 ---

-通过此教程我们一步一步描述如何在 Apache HertzBeat (incubating) 系统下自定义新增适配一款基于 http 协议的监控类型。
+通过此教程我们一步一步描述如何在 Apache HertzBeat 系统下自定义新增适配一款基于 http 协议的监控类型。

 阅读此教程前我们希望您已经从[自定义监控](extend-point)和[http协议自定义](extend-http)了解熟悉了怎么自定义类型，指标，协议等。

@@ -350,13 +350,13 @@ svn commit -m "release for HertzBeat 1.6.0-RC1"
 发送社区投票邮件需要至少三个`+1`，且无`-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!
 在72小时后，将统计投票结果，并发送投票结果邮件，如下所示。

 > `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:
@@ -442,14 +442,14 @@ ChunJin Mu

 > `Send to`: <general@incubator.apache.org> <br />
 > `cc`: <dev@hertzbeat.apache.org>、<private@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 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.

@@ -487,7 +487,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
@@ -508,13 +508,13 @@ Chunjin Mu
 然后将统计投票结果，并发送投票结果邮件，如下所示。

 > `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.

@@ -585,13 +585,13 @@ release note: xxx

 > `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.
@@ -110,9 +110,7 @@ tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz

 进行如下检查：

- [ ] 文件夹包含单词`incubating`
 - [ ] 存在`LICENSE`和`NOTICE`文件
- [ ] 存在`DISCLAIMER`或`DISCLAIMER-WIP`文件
 - [ ] `NOTICE`文件中的年份正确
 - [ ] 所有文本文件开头都有ASF许可证
 - [ ] 检查第三方依赖许可证：
@@ -136,9 +134,7 @@ cd apache-hertzbeat-${release_version}-incubating-src
 进行如下检查:

 - [ ] 检查源码包是否包含由于包含不必要文件，致使tar包过于庞大
- [ ] 文件夹包含单词`incubating`
 - [ ] 存在`LICENSE`和`NOTICE`文件
- [ ] 存在`DISCLAIMER`或`DISCLAIMER-WIP`文件
 - [ ] `NOTICE`文件中的年份正确
 - [ ] 只存在文本文件，不存在二进制文件
 - [ ] 所有文件的开头都有ASF许可证
@@ -270,7 +270,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.

@@ -281,5 +281,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
 ```
@@ -1,10 +1,10 @@
 ---
 id: download
-title: 下载 Apache HertzBeat (incubating)
+title: 下载 Apache HertzBeat
 sidebar_label: Download
 ---

-> **这里是 Apache HertzBeat (incubating) 官方下载页面。**
+> **这里是 Apache HertzBeat 官方下载页面。**
 > **请在下方表中选择版本下载，推荐使用最新版本。**

 :::tip
@@ -16,7 +16,7 @@ keywords: [开源监控系统, 开源网站监控, 状态页面]
 | 字段名称 |                  字段说明                  |                                                举例                                                 |
 |------|----------------------------------------|---------------------------------------------------------------------------------------------------|
 | 组织名称 | 组织的名称                                  | HertzBeat                                                                                         |
-| 组织介绍 | 组织的详细介绍                                | Apache HertzBeat (incubating) 是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。 |
+| 组织介绍 | 组织的详细介绍                                | Apache HertzBeat 是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。 |
 | 网站链接 | 组织网站的 URL，便于访问者获取更多信息                  | <https://hertzbeat.apache.org/>                                                                     |
 | 标志图片 | 组织官方标志或 Logo 的图片文件路径或 URL，建议使用 .svg 格式 | <https://hertzbeat.apache.org/zh-cn/img/hertzbeat-logo.svg>                                         |
 | 反馈地址 | 接收问题反馈的地址                              | <https://github.com/apache/hertzbeat/issues>                                                        |
@@ -1,6 +1,6 @@
 ---
 id: introduce  
-title: Apache HertzBeat (incubating)     
+title: Apache HertzBeat     
 sidebar_label: 介绍
 slug: /
 ---
@@ -6,7 +6,7 @@ sidebar_label: 更新账户和密钥

 ## 更新账户

-Apache HertzBeat (incubating) 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat
+Apache HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat
 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤
 修改位于安装目录下的 `/hertzbeat/config/sureness.yml` 的配置文件，docker环境目录为`opt/hertzbeat/config/sureness.yml`，建议提前挂载映射
 配置文件内容参考如下
@@ -4,7 +4,7 @@ title: 使用 宝塔面板 部署 HertzBeat
 sidebar_label: 基于宝塔面板部署
 ---

-Apache HertzBeat (incubating) 支持在宝塔面板的 `Docker` 应用商店一键部署。
+Apache HertzBeat 支持在宝塔面板的 `Docker` 应用商店一键部署。

 ## 前提

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务 GreptimeDB 安装初始化（可选）
 sidebar_label: 指标数据存储 GreptimeDB
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务InfluxDB安装初始化(可选)
 sidebar_label: 指标数据存储InfluxDB
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务IoTDB安装初始化(可选)
 sidebar_label: 指标数据存储IoTDB
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 关系型数据库使用 Mysql 替换依赖的 H2 存储系统元数据(
 sidebar_label: 元数据存储Mysql
 ---

-MYSQL是一款值得信赖的关系型数据库，Apache HertzBeat (incubating) 除了支持使用默认内置的H2数据库外，还可以切换为使用MYSQL存储监控信息，告警信息，配置信息等结构化关系数据。
+MYSQL是一款值得信赖的关系型数据库，Apache HertzBeat 除了支持使用默认内置的H2数据库外，还可以切换为使用MYSQL存储监控信息，告警信息，配置信息等结构化关系数据。

 注意⚠️ 使用外置MySQL数据库替换内置H2数据库为可选项，但建议生产环境配置，以提供更好的性能

@@ -5,7 +5,7 @@ sidebar_label: 安装包方式安装
 ---

 :::tip
-Apache HertzBeat (incubating) 支持在Linux Windows Mac系统安装运行，CPU支持X86/ARM64。
+Apache HertzBeat 支持在Linux Windows Mac系统安装运行，CPU支持X86/ARM64。
 由于1.6.0及以后版本使用 `Java 17` ，且安装包不再提供内置jdk的版本，参考以下情况使用新版Hertzbeat。

 - 当你的服务器中默认环境变量为 `Java 17` 时，这一步你无需任何操作。
@@ -4,7 +4,7 @@ title: 关系型数据库使用 PostgreSQL 替换依赖的 H2 存储系统元数
 sidebar_label: 元数据存储PostgreSQL(推荐)
 ---

-PostgreSQL 是一个功能强大，开源的关系型数据库管理系统（RDBMS）。Apache HertzBeat (incubating) 除了支持使用默认内置的 H2 数据库外，还可以切换为使用 PostgreSQL 存储监控信息，告警信息，配置信息等结构化关系数据。
+PostgreSQL 是一个功能强大，开源的关系型数据库管理系统（RDBMS）。Apache HertzBeat 除了支持使用默认内置的 H2 数据库外，还可以切换为使用 PostgreSQL 存储监控信息，告警信息，配置信息等结构化关系数据。

 注意⚠️ 使用外置 PostgreSQL 数据库替换内置 H2 数据库为可选项，但建议生产环境配置，以提供更好的性能

@@ -6,7 +6,7 @@ sidebar_label: 快速开始

 ### 🐕 开始使用

- 如果您是想将 Apache HertzBeat (incubating) 部署到本地搭建监控系统，请参考下面的部署文档进行操作。
+- 如果您是想将 Apache HertzBeat 部署到本地搭建监控系统，请参考下面的部署文档进行操作。

 ### 🍞 HertzBeat安装

@@ -4,7 +4,7 @@ title: 使用 Rainbond 部署 HertzBeat
 sidebar_label: 基于Rainbond部署
 ---

-如果你不熟悉 Kubernetes，想在 Kubernetes 中安装 Apache HertzBeat (incubating)，可以使用 Rainbond 来部署。Rainbond 是一个基于 Kubernetes 构建的云原生应用管理平台，可以很简单的将你的应用部署到 Kubernetes中。
+如果你不熟悉 Kubernetes，想在 Kubernetes 中安装 Apache HertzBeat，可以使用 Rainbond 来部署。Rainbond 是一个基于 Kubernetes 构建的云原生应用管理平台，可以很简单的将你的应用部署到 Kubernetes中。

 ## Rainbond Cloud 部署

@@ -12,7 +12,7 @@ sidebar_label: SSL证书过期监控使用案例

 ## HertzBeat 是什么

-Apache HertzBeat (incubating) 一个拥有强大自定义监控能力，无需Agent的实时监控工具。网站监测，PING连通性，端口可用性，数据库，操作系统，中间件，API监控，阈值告警，告警通知(邮件微信钉钉飞书)。
+Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时监控工具。网站监测，PING连通性，端口可用性，数据库，操作系统，中间件，API监控，阈值告警，告警通知(邮件微信钉钉飞书)。

 github: <https://github.com/apache/hertzbeat>

@@ -4,7 +4,7 @@ title: 依赖时序数据库服务TDengine安装初始化(可选)
 sidebar_label: 指标数据存储TDengine
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: HertzBeat 新版本更新指引
 sidebar_label: 版本更新指引
 ---

-**Apache HertzBeat (incubating) 的发布版本列表**
+**Apache HertzBeat 的发布版本列表**

 - [下载页面](https://hertzbeat.apache.org/docs/download)
 - [Github Release](https://github.com/apache/hertzbeat/releases)
@@ -4,7 +4,7 @@ title: 依赖时序数据库服务VictoriaMetrics安装初始化
 sidebar_label: 指标数据存储VictoriaMetrics(推荐)
 ---

-Apache HertzBeat (incubating) 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)
+Apache HertzBeat 的历史数据存储依赖时序数据库，任选其一安装初始化即可，也可不安装(注意⚠️但强烈建议生产环境配置)

 > 我们推荐使用并长期支持 VictoriaMetrics 作为存储。

@@ -4,7 +4,7 @@ title: 监控模板中心
 sidebar_label: 监控模板
 ---

-> Apache HertzBeat (incubating) 是一个拥有强大自定义监控能力，无需 Agent 的开源实时监控告警工具。
+> Apache HertzBeat 是一个拥有强大自定义监控能力，无需 Agent 的开源实时监控告警工具。
 >
 > 我们将`Http, Jmx, Ssh, Snmp, Jdbc, Prometheus`等协议规范可配置化，您只需在浏览器配置`YML`就能使用这些协议去自定义采集任何您想要的指标。
 > 您相信只需简单配置即可快速适配一款`K8s`或`Docker`等新的监控类型吗？
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Calvin	eb6ea32eae	Merge branch 'master' into doc-graduate	2025-08-22 01:12:18 +08:00
DeleiGuo	7e1873bc10	[bugfix] fixed jexl keyword issue in spring_gateway monitoring template (#3693 )	2025-08-22 01:12:04 +08:00
tomsun28	fea6bf5803	Merge branch 'master' into doc-graduate	2025-08-22 00:41:49 +08:00
tomsun28	8818385d65	[docs] remove incubating Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-22 00:39:17 +08:00
tomsun28	4d072b4417	[doc] update doc	2025-08-22 00:36:09 +08:00
tomsun28	db4e1df92d	[doc] update doc	2025-08-22 00:26:33 +08:00
tomsun28	25749d6fa3	[docs] remove incubating Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-21 23:25:02 +08:00
DeleiGuoandCalvin	8eb60210a3	[bugfix] fixed jexl keyword issue in windows monitoring template (#3687 ) Co-authored-by: Calvin <zhengqiwei@apache.org>	2025-08-21 22:38:49 +08:00
DeleiGuoandCalvin	d608f732f7	[bugfix] fixed jexl keyword issue in hertzbeat monitoring template (#3686 ) Co-authored-by: Calvin <zhengqiwei@apache.org>	2025-08-21 22:36:53 +08:00
DeleiGuoandCalvin	2d9a2955ef	[bugfix] fixed jexl keyword issue in postgresql monitoring template (#3685 ) Co-authored-by: Calvin <zhengqiwei@apache.org>	2025-08-21 22:19:28 +08:00
tomsun28	6c2281ad09	[docs] remove incubating Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-21 22:06:45 +08:00
tomsun28	a4bedb2b5d	[docs] remove incubating Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-21 22:02:19 +08:00
tomsun28	cc1808187d	[docs] remove incubating Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-21 21:52:51 +08:00
tomsun28	c88b0b50ce	[docs] remove incubating Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-21 21:40:14 +08:00
tomsun28	8033e81e2e	[docs] remove DISCLAIMER Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-08-21 21:31:23 +08:00
VampireAchao Calvin 淞筱 aias00 shown	cae4423f30	[doc] graduate and remove incubating (#3584 ) Co-authored-by: Calvin <zhengqiwei@apache.org> Co-authored-by: 淞筱 <2030509072@qq.com> Co-authored-by: aias00 <liuhongyu@apache.org> Co-authored-by: shown <yuluo08290126@gmail.com>	2025-08-21 21:22:49 +08:00
Calvin liutianyou tomsun28	f0e53a9fb3	[doc] add japanese i18n in app-redis_sentinel.yml (#3681 ) Co-authored-by: liutianyou <tianyou.liu@qq.com> Co-authored-by: tomsun28 <tomsun28@outlook.com>	2025-08-20 00:21:51 +08:00
DeleiGuo Calvin tomsun28	79da1a198b	[improve] optimize status page layout and UI (#3680 ) Co-authored-by: Calvin <zhengqiwei@apache.org> Co-authored-by: tomsun28 <tomsun28@outlook.com>	2025-08-20 00:17:03 +08:00
Calvin liutianyou tomsun28	64cb804147	[doc] add japanese i18n in app-dolphinscheduler.yml (#3677 ) Co-authored-by: liutianyou <tianyou.liu@qq.com> Co-authored-by: tomsun28 <tomsun28@outlook.com>	2025-08-20 00:03:12 +08:00