This is an automated email from the ASF dual-hosted git repository.

gongchao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git


The following commit(s) were added to refs/heads/master by this push:
     new db90f29cd0 [doc] add japanese i18n in app-qq_mailbox.yml and 
app-redfish.yml (#3635)
db90f29cd0 is described below

commit db90f29cd0c49b4a03f59bb3a73acfc207e5a7ee
Author: Calvin <[email protected]>
AuthorDate: Sat Aug 9 14:21:28 2025 +0800

    [doc] add japanese i18n in app-qq_mailbox.yml and app-redfish.yml (#3635)
    
    Co-authored-by: tomsun28 <[email protected]>
---
 .../src/main/resources/define/app-qq_mailbox.yml   | 38 +++++++++++--
 .../src/main/resources/define/app-redfish.yml      | 66 +++++++++-------------
 2 files changed, 59 insertions(+), 45 deletions(-)

diff --git a/hertzbeat-manager/src/main/resources/define/app-qq_mailbox.yml 
b/hertzbeat-manager/src/main/resources/define/app-qq_mailbox.yml
index da4c6feaee..e777c67583 100644
--- a/hertzbeat-manager/src/main/resources/define/app-qq_mailbox.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-qq_mailbox.yml
@@ -21,11 +21,13 @@ app: qq_mailbox
 name:
   zh-CN: QQ 邮箱监控
   en-US: QQ Mailbox
+  ja-JP: QQ電子メール
 # The description and help of this monitoring type
 help:
-  zh-CN: HertzBeat 使用 IMAP 协议对 QQ 邮箱的详细信息进行采集监控。<br>您可以点击“<i>新建 
POP3</i>”并进行配置,或者选择“<i>更多操作</i>”,导入已有配置。
-  en-US: HertzBeat uses IMAP protocol to collect detailed metrics of QQ 
mailbox. <br>You can click "<i>New POP3</i>" and configure it, or select 
"<i>More Operations</i>" to import the existing configuration.
-  zh-TW: HertzBeat 使用 IMAP 協議對 QQ 郵箱的詳細信息進行採集監控。<br>您可以點擊“<i>新建 
POP3</i>”並進行配置,或者選擇“<i>更多操作</i>”,導入已有配置。
+  zh-CN: HertzBeat 使用 IMAP 协议对 QQ 邮箱的详细信息进行采集监控。<br>您可以点击“<i>新建 QQ 
邮箱</i>”并进行配置,或者选择“<i>更多操作</i>”,导入已有配置。
+  en-US: HertzBeat uses IMAP protocol to collect detailed metrics of QQ 
mailbox. <br>You can click "<i>New QQ Mailbox</i>" and configure it, or select 
"<i>More Operations</i>" to import the existing configuration.
+  zh-TW: HertzBeat 使用 IMAP 協議對 QQ 郵箱的詳細信息進行採集監控。<br>您可以點擊“<i>新建 QQ 
邮箱</i>”並進行配置,或者選擇“<i>更多操作</i>”,導入已有配置。
+  ja-JP: HertzBeat は IMAP プロトコルを介してQQ電子メールの詳細情報を監視します。<br>「<i>新規 
QQ電子メール</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/imap
   en-US: https://hertzbeat.apache.org/docs/help/imap
@@ -37,6 +39,7 @@ params:
     name:
       zh-CN: 目标Host
       en-US: Target Host
+      ja-JP: 目標ホスト
     # type-param field type(most mapping the html input type)
     type: host
     # required-true or false
@@ -47,6 +50,7 @@ params:
     name:
       zh-CN: 启动SSL
       en-US: SSL
+      ja-JP: SSL
     # When the type is boolean, the frontend will display a switch for it.
     type: boolean
     # required-true or false
@@ -56,6 +60,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
@@ -68,6 +73,7 @@ params:
     name:
       zh-CN: 连接超时时间(ms)
       en-US: Connect Timeout(ms)
+      ja-JP: 接続タイムアウト(ms)
     # type-param field type(most mapping the html input type)
     type: number
     # when type is number, range is required
@@ -81,7 +87,8 @@ params:
     # name-param field display i18n name
     name:
       zh-CN: IMAP 邮箱地址
-      en-US: Email
+      en-US: IMAP Address
+      ja-JP: IMAPアドレス
     # type-param field type(most mapping the html input type) The type "text" 
belongs to a text input field.
     type: text
     # required-true or false
@@ -92,6 +99,7 @@ params:
     name:
       zh-CN: 授权码
       en-US: Authorize Code
+      ja-JP: 認証コード
     # type-param field type(most mapping the html input type) The type "text" 
belongs to a text input field.
     type: text
     # required-true or false
@@ -104,6 +112,7 @@ metrics:
     i18n:
       zh-CN: 可用性
       en-US: Available
+      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
@@ -116,6 +125,7 @@ metrics:
         i18n:
           zh-CN: 响应时间
           en-US: Response Time
+          ja-JP: 応答時間
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, 
sdk
     protocol: imap
     # Specific collection configuration when protocol is http protocol
@@ -139,6 +149,7 @@ metrics:
     i18n:
       zh-CN: 收件箱信息
       en-US: Inbox info
+      ja-JP: 受信箱情報
     # metrics scheduling priority(0->127)->(high->low), metrics with the same 
priority will be scheduled in parallel
     # priority 0's metrics is availability metrics, it will be scheduled 
first, only availability metrics collect success will the scheduling continue
     priority: 1
@@ -150,16 +161,19 @@ metrics:
         i18n:
           zh-CN: 邮件总数
           en-US: Total message count
+          ja-JP: メッセージ総数
       - field: recentMessageCount
         type: 0
         i18n:
           zh-CN: 最近收到邮件总数
           en-US: Recent message count
+          ja-JP: 最新メッセージ総数
       - field: unseenMessageCount
         type: 0
         i18n:
           zh-CN: 未读邮件总数
           en-US: Unseen message count
+          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:
       - INBOXTotalMessageCount
@@ -193,6 +207,7 @@ metrics:
     i18n:
       zh-CN: 已发送信息
       en-US: Sent info
+      ja-JP: 送信情報
     # metrics scheduling priority(0->127)->(high->low), metrics with the same 
priority will be scheduled in parallel
     # priority 0's metrics is availability metrics, it will be scheduled 
first, only availability metrics collect success will the scheduling continue
     priority: 2
@@ -204,6 +219,7 @@ metrics:
         i18n:
           zh-CN: 邮件总数
           en-US: Total message count
+          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:
       - Sent MessagesTotalMessageCount
@@ -233,6 +249,7 @@ metrics:
     i18n:
       zh-CN: 草稿箱信息
       en-US: Drafts info
+      ja-JP: ドラフトボックス情報
     # metrics scheduling priority(0->127)->(high->low), metrics with the same 
priority will be scheduled in parallel
     # priority 0's metrics is availability metrics, it will be scheduled 
first, only availability metrics collect success will the scheduling continue
     priority: 3
@@ -244,6 +261,7 @@ metrics:
         i18n:
           zh-CN: 邮件总数
           en-US: Total message count
+          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:
       - DraftsTotalMessageCount
@@ -273,6 +291,7 @@ metrics:
     i18n:
       zh-CN: 已删除信息
       en-US: Deleted Messages info
+      ja-JP: 削除済みメッセージ情報
     # metrics scheduling priority(0->127)->(high->low), metrics with the same 
priority will be scheduled in parallel
     # priority 0's metrics is availability metrics, it will be scheduled 
first, only availability metrics collect success will the scheduling continue
     priority: 4
@@ -284,6 +303,7 @@ metrics:
         i18n:
           zh-CN: 邮件总数
           en-US: Total message count
+          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:
       - Deleted MessagesTotalMessageCount
@@ -313,6 +333,7 @@ metrics:
     i18n:
       zh-CN: 垃圾箱信息
       en-US: Junk info
+      ja-JP: 迷惑メールボックス情報
     # metrics scheduling priority(0->127)->(high->low), metrics with the same 
priority will be scheduled in parallel
     # priority 0's metrics is availability metrics, it will be scheduled 
first, only availability metrics collect success will the scheduling continue
     priority: 5
@@ -324,16 +345,19 @@ metrics:
         i18n:
           zh-CN: 邮件总数
           en-US: Total message count
+          ja-JP: 迷惑メッセージ総数
       - field: recentMessageCount
         type: 0
         i18n:
           zh-CN: 最近收到邮件总数
           en-US: Recent message count
+          ja-JP: 最新の迷惑メッセージ総数
       - field: unseenMessageCount
         type: 0
         i18n:
           zh-CN: 未读邮件总数
           en-US: Unseen message count
+          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:
       - JunkTotalMessageCount
@@ -367,6 +391,7 @@ metrics:
     i18n:
       zh-CN: QQ邮件订阅信息
       en-US: QQ Mail Subscribe Info
+      ja-JP: QQ電子メールサブスクリプション情報
     # 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: 6
@@ -378,16 +403,19 @@ metrics:
         i18n:
           zh-CN: 邮件总数
           en-US: Total message count
+          ja-JP: メッセージ総数
       - field: recentMessageCount
         type: 0
         i18n:
           zh-CN: 最近收到邮件总数
           en-US: Recent message count
+          ja-JP: 最新のメッセージ総数
       - field: unseenMessageCount
         type: 0
         i18n:
           zh-CN: 未读邮件总数
-          en-US: Unseen message count
+          en-US: Unread message count
+          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:
       - 其他文件夹/QQ邮件订阅TotalMessageCount
diff --git a/hertzbeat-manager/src/main/resources/define/app-redfish.yml 
b/hertzbeat-manager/src/main/resources/define/app-redfish.yml
index 2c38fd8867..1f6987a9fc 100644
--- a/hertzbeat-manager/src/main/resources/define/app-redfish.yml
+++ b/hertzbeat-manager/src/main/resources/define/app-redfish.yml
@@ -14,156 +14,131 @@
 # limitations under the License.
 
 # The monitoring type category:service-application service monitoring 
db-database monitoring custom-custom monitoring os-operating system monitoring
-# 监控类型所属类别:service-应用服务 program-应用程序 db-数据库 custom-自定义 os-操作系统 bigdata-大数据 
mid-中间件 webserver-web服务器 cache-缓存 cn-云原生 network-网络监控等等
 category: server
 # The monitoring type eg: linux windows tomcat mysql aws...
-# 监控类型 eg: linux windows tomcat mysql aws...
 app: redfish
 # The monitoring i18n name
-# 监控类型国际化名称
 name:
   zh-CN: Redfish
   en-US: Redfish
+  ja-JP: Redfish
 # The description and help of this monitoring type
-# 监控类型的帮助描述信息
 help:
   zh-CN: Hertzbeat 对支持 Redfish 服务的服务器进行测量监控。<br>您可以点击 “<i>新建 Redfish</i>” 
并进行配置,或者选择“<i>更多操作</i>”,导入已有配置。
   en-US: Hertzbeat monitoring servers supporting Redfish services. You could 
click the "<i>New Redfish</i>" button and proceed with the configuration or 
import an existing setup through the "<i>More Actions</i>" menu.
   zh-TW: Hertzbeat 對支援 Redfish 
服務的伺服器進行測量監控。<br>您可以點擊“<i>Redfish</i>”並進行配寘,或者選擇“<i>更多操作</i>”,導入已有配寘。
+  ja-JP: Hertzbeat は Redfishをサポートするサーバーの一般的なメトリクスを監視します。<br>「<i>新規 
FTPサーバー</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
   zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/redfish
   en-US: https://hertzbeat.apache.org/docs/help/redfish
-# 监控所需输入参数定义(根据定义渲染页面UI)
 # Input params define for monitoring(render web ui by the definition)
 params:
   # field-param field key
-  # field-变量字段标识符
   - field: host
     # name-param field display i18n name
-    # name-参数字段显示名称
     name:
       zh-CN: 目标Host
       en-US: Target Host
+      ja-JP: 目標ホスト
     # type-param field type(most mapping the html input type)
-    # type-字段类型,样式(大部分映射input标签type属性)
     type: host
     # required-true or false
-    # required-是否是必输项 true-必填 false-可选
     required: true
   # field-param field key
-  # field-变量字段标识符
   - field: port
     # name-param field display i18n name
-    # name-参数字段显示名称
     name:
       zh-CN: 端口
       en-US: Port
+      ja-JP: ポート
     # type-param field type(most mapping the html input type)
-    # type-字段类型,样式(大部分映射input标签type属性)
     type: number
     # when type is number, range is required
-    # 当type为number时,用range表示范围
     range: '[0,65535]'
     # required-true or false
-    # required-是否是必输项 true-必填 false-可选
     required: true
     # default value
-    # 默认值
     defaultValue: 443
   # field-param field key
-  # field-变量字段标识符
   - field: timeout
     # name-param field display i18n name
-    # name-参数字段显示名称
     name:
       zh-CN: 查询超时时间
       en-US: Query Timeout
+      ja-JP: クエリタイムアウト
     # type-param field type(most mapping the html input type)
-    # type-字段类型,样式(大部分映射input标签type属性)
     type: number
     # required-true or false
-    # required-是否是必输项 true-必填 false-可选
     required: false
     # hide param-true or false
-    # 是否隐藏字段 true or false
     hide: true
     # default value
-    # 默认值
     defaultValue: 6000
   # field-param field key
-  # field-变量字段标识符
   - field: username
     # name-param field display i18n name
-    # name-参数字段显示名称
     name:
       zh-CN: 用户名
       en-US: Username
+      ja-JP: ユーザー名
     # type-param field type(most mapping the html input type)
-    # type-字段类型,样式(大部分映射input标签type属性)
     type: text
     # when type is text, use limit to limit string length
-    # 当type为text时,用limit表示字符串限制大小
     limit: 50
     # required-true or false
-    # required-是否是必输项 true-必填 false-可选
     required: false
   # field-param field key
-  # field-变量字段标识符
   - field: password
     # name-param field display i18n name
-    # name-参数字段显示名称
     name:
       zh-CN: 密码
       en-US: Password
+      ja-JP: パスワード
     # type-param field type(most mapping the html input tag)
-    # type-字段类型,样式(大部分映射input标签type属性)
     type: password
     # required-true or false
-    # required-是否是必输项 true-必填 false-可选
     required: false
 # collect metrics config list
-# 采集指标配置列表
 metrics:
   # metrics - cpu
-  # 监控指标 - cpu
   - name: Chassis
     # 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
-    # 指标采集调度优先级(0->127)->(优先级高->低) 优先级低的指标会等优先级高的指标采集完成后才会被调度, 相同优先级的指标会并行调度采集
-    # 优先级为0的指标为可用性指标,即它会被首先调度,采集成功才会继续调度其它指标,采集失败则中断调度
     priority: 0
     # collect metrics content
-    # 具体监控指标列表
     fields:
       # field-metric name, type-metric type(0-number,1-string), unit-metric 
unit('%','ms','MB'), label-whether it is a metrics label field
-      # field-指标名称, type-指标类型(0-number数字,1-string字符串), 
unit-指标单位('%','ms','MB'), label-是否是指标标签字段
       - field: id
         type: 1
         i18n:
           zh-CN: 机箱唯一标识符
           en-US: Chassis Unique Identifier
+          ja-JP: シャーシID
       - field: name
         type: 1
         i18n:
           zh-CN: 机箱名称
           en-US: Chassis Name
+          ja-JP: シャーシ名
       - field: type
         type: 1
         i18n:
           zh-CN: 机箱类型
-          en-US: Chasis Type
+          en-US: Chassis Type
+          ja-JP: シャーシタイプ
       - field: state
         type: 1
         i18n:
           zh-CN: 机箱状态
-          en-US: Chasis State
+          en-US: Chassis State
+          ja-JP: シャーシ状態
       - field: health
         type: 1
         i18n:
           zh-CN: 机箱健康状态
-          en-US: Chasis Health
+          en-US: Chassis Health
+          ja-JP: シャーシ健全状態
     # (optional)metrics field alias name, it is used as an alias field to map 
and convert the collected data and metrics field
-    # (可选)监控指标别名, 做为中间字段与采集数据字段和指标字段映射转换
     # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, 
sdk
     protocol: redfish
     # the config content when protocol is redfish
@@ -193,26 +168,31 @@ metrics:
         i18n:
           zh-CN: 电池唯一标识符
           en-US: Battery Unique Identifier
+          ja-JP: 電池ID
       - field: name
         type: 1
         i18n:
           zh-CN: 电池名称
           en-US: Battery Name
+          ja-JP: 電池名
       - field: state
         type: 1
         i18n:
           zh-CN: 电池状态
           en-US: Battery State
+          ja-JP: 電池状態
       - field: health
         type: 1
         i18n:
           zh-CN: 电池健康状态
           en-US: Battery Health
+          ja-JP: 電池健全状態
       - field: charge_status
         type: 1
         i18n:
           zh-CN: 电池充电状态
           en-US: Battery Charge Status
+          ja-JP: 電池充電状況
     protocol: redfish
     redfish:
       # redfish host: ipv4 ipv6 domain
@@ -240,31 +220,37 @@ metrics:
         i18n:
           zh-CN: 风扇唯一标识符
           en-US: Fan Unique Identifier
+          ja-JP: ファンID
       - field: name
         type: 1
         i18n:
           zh-CN: 风扇名称
           en-US: Fan Name
+          ja-JP: ファン名
       - field: state
         type: 1
         i18n:
           zh-CN: 风扇状态
           en-US: Fan State
+          ja-JP: ファン状態
       - field: health
         type: 1
         i18n:
           zh-CN: 风扇健康状态
           en-US: Fan Health
+          ja-JP: ファン健全状態
       - field: temperature
         type: 0
         i18n:
           zh-CN: 传感器温度
           en-US: Sensor Temperature
+          ja-JP: センサー温度
       - field: speed
         type: 0
         i18n:
           zh-CN: 风扇转速
           en-US: Fan Speed
+          ja-JP: ファンスピード
     protocol: redfish
     redfish:
       # redfish host: ipv4 ipv6 domain


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to