Merge branch 'master' into jackson-prop

[refactor] AlarmCacheManager refactoring processing logic (#3525 )
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> Co-authored-by: Sherlock Yin <sherlock.yin1994@gmail.com> Co-authored-by: kangli <likang@apache.org>
2026-09-17 18:19:02 +00:00 · 2025-07-06 22:54:14 +08:00 · 2025-07-06 22:06:30 +08:00 · 2025-07-06 20:57:39 +08:00 · 2025-07-06 19:06:19 +08:00 · 2025-07-06 15:12:57 +08:00
137 changed files with 2356 additions and 584 deletions
@@ -52,6 +52,9 @@ github:
      required_pull_request_reviews:
        dismiss_stale_reviews: true
        required_approving_review_count: 1
+  # enable GitHub Dependabot to create PRs for security alerts but not for every dependency update
+  dependabot_alerts:  true
+  dependabot_updates: false
 notifications:
  commits: notifications@hertzbeat.apache.org
  issues: notifications@hertzbeat.apache.org
@@ -49,11 +49,9 @@ jobs:
      - name: Dead Link Check
        run: |
          sudo npm install -g markdown-link-check@3.8.7
-          for file in $(find ./home -name "*.md"); do
-            if ! grep -Fxq "$file" ./script/ci/exclude_files.txt; then
-              markdown-link-check -c ./script/ci/link_check.json -q "$file"
-            fi
-          done
+          find ./home -name "*.md" > all_md_files.txt
+          grep -vFf ./script/ci/exclude_files.txt all_md_files.txt > to_check.txt
+          xargs -P 8 -a to_check.txt -I{} markdown-link-check -c ./script/ci/link_check.json -q "{}"

      - name: NPM INSTALL
        working-directory: home
@@ -33,8 +33,8 @@
 ### 特点

 - 集 **监控+告警+通知** 为一体，支持对应用服务，应用程序，数据库，缓存，操作系统，大数据，中间件，Web 服务器，云原生，网络，自定义等监控阈值告警通知一步到位。
- 易用友好，无需 `Agent`，全 `WEB` 页面操作，鼠标点一点就能监控告警，零上手学习成本。    
- 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需配置下就能立刻适配一款 `K8s` 或 `Docker` 等新的监控类型吗？  
+- 易用友好，无需 `Agent`，全 `WEB` 页面操作，鼠标点一点就能监控告警，无需学习成本。    
+- 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需简单配置即可快速适配一款 `K8s` 或 `Docker` 等新的监控类型吗？  
 - 兼容 `Prometheus` 的系统生态并且更多，只需页面操作就可以监控 `Prometheus` 所能监控的。
 - 高性能，支持多采集器集群横向扩展，支持多隔离网络监控，云边协同。
 - 自由的告警阈值规则，`邮件` `Discord` `Slack` `Telegram` `钉钉` `微信` `飞书` `短信` `Webhook` `Server酱` 等方式消息及时送达。
@@ -17,6 +17,9 @@

 package org.apache.hertzbeat.alert.calculate;

+import com.google.common.collect.Table;
+import com.google.common.collect.Tables;
+import org.apache.commons.lang3.StringUtils;
 import org.apache.hertzbeat.alert.dao.SingleAlertDao;
 import org.apache.hertzbeat.alert.util.AlertUtil;
 import org.apache.hertzbeat.common.constants.CommonConstants;
@@ -24,7 +27,6 @@ import org.apache.hertzbeat.common.entity.alerter.SingleAlert;
 import org.springframework.stereotype.Component;

 import java.util.List;
-import java.util.Map;
 import java.util.concurrent.ConcurrentHashMap;

 /**
@@ -33,49 +35,78 @@ import java.util.concurrent.ConcurrentHashMap;
@Component
 public class AlarmCacheManager {

+    private static final String CUSTOM_FIRING_ROW_KEY = "CUSTOM_FIRING_";
+
    /**
     * The alarm in the process is triggered
-     * key - labels fingerprint
+     * rowKey - define id
+     * columnKey - labels fingerprint
     */
-    private final Map<String, SingleAlert> pendingAlertMap;
+    private final Table<String, String, SingleAlert> pendingAlertMap;
+
    /**
     * The not recover alert
-     * key - labels fingerprint
+     * rowKey - define id
+     * columnKey - labels fingerprint
     */
-    private final Map<String, SingleAlert> firingAlertMap;
+    private final Table<String, String, SingleAlert> firingAlertMap;

    public AlarmCacheManager(SingleAlertDao singleAlertDao) {
-        this.pendingAlertMap = new ConcurrentHashMap<>(8);
-        this.firingAlertMap = new ConcurrentHashMap<>(8);
+        this.pendingAlertMap = Tables.newCustomTable(new ConcurrentHashMap<>(8), ConcurrentHashMap::new);
+        this.firingAlertMap = Tables.newCustomTable(new ConcurrentHashMap<>(8), ConcurrentHashMap::new);
        List<SingleAlert> singleAlerts = singleAlertDao.querySingleAlertsByStatus(CommonConstants.ALERT_STATUS_FIRING);
        for (SingleAlert singleAlert : singleAlerts) {
            String fingerprint = AlertUtil.calculateFingerprint(singleAlert.getLabels());
+            String defineId = singleAlert.getLabels().get(CommonConstants.LABEL_DEFINE_ID);
+            if (StringUtils.isBlank(defineId)) {
+                defineId = getCustomKey(fingerprint);
+            }
            singleAlert.setId(null);
-            this.firingAlertMap.put(fingerprint, singleAlert);
+            this.firingAlertMap.put(defineId, fingerprint, singleAlert);
        }
    }

-    public void putPending(String fingerPrint, SingleAlert alert) {
-        this.pendingAlertMap.put(fingerPrint, alert);
+    public void putPending(Long defineId, String fingerPrint, SingleAlert alert) {
+        this.pendingAlertMap.put(String.valueOf(defineId), fingerPrint, alert);
    }

-    public SingleAlert getPending(String fingerPrint) {
-        return this.pendingAlertMap.get(fingerPrint);
+    public SingleAlert getPending(Long defineId, String fingerPrint) {
+        return this.pendingAlertMap.get(String.valueOf(defineId), fingerPrint);
    }

-    public SingleAlert removePending(String fingerPrint) {
-        return this.pendingAlertMap.remove(fingerPrint);
+    public void removePending(Long defineId, String fingerPrint) {
+        this.pendingAlertMap.remove(String.valueOf(defineId), fingerPrint);
+    }
+
+    public void putFiring(Long defineId, String fingerPrint, SingleAlert alert) {
+        this.firingAlertMap.put(String.valueOf(defineId), fingerPrint, alert);
    }

    public void putFiring(String fingerPrint, SingleAlert alert) {
-        this.firingAlertMap.put(fingerPrint, alert);
+        this.firingAlertMap.put(getCustomKey(fingerPrint), fingerPrint, alert);
+    }
+
+    public SingleAlert getFiring(Long defineId, String fingerPrint) {
+        SingleAlert singleAlert = this.firingAlertMap.get(String.valueOf(defineId), fingerPrint);
+        if (null != singleAlert) {
+            return singleAlert;
+        }
+        return getFiring(fingerPrint);
+    }
+
+    public SingleAlert removeFiring(Long defineId, String fingerPrint) {
+        SingleAlert singleAlert = this.firingAlertMap.remove(String.valueOf(defineId), fingerPrint);
+        if (null == singleAlert) {
+            return this.firingAlertMap.remove(getCustomKey(fingerPrint), fingerPrint);
+        }
+        return singleAlert;
    }

    public SingleAlert getFiring(String fingerPrint) {
-        return this.firingAlertMap.get(fingerPrint);
+        return this.firingAlertMap.get(getCustomKey(fingerPrint), fingerPrint);
    }

-    public SingleAlert removeFiring(String fingerPrint) {
-        return this.firingAlertMap.remove(fingerPrint);
+    private String getCustomKey(String fingerPrint) {
+        return CUSTOM_FIRING_ROW_KEY + fingerPrint;
    }
 }
@@ -17,8 +17,9 @@

 package org.apache.hertzbeat.alert.calculate;

-import java.util.HashMap;
 import lombok.extern.slf4j.Slf4j;
+import org.apache.commons.collections4.CollectionUtils;
+import org.apache.commons.lang3.StringUtils;
 import org.apache.hertzbeat.alert.reduce.AlarmCommonReduce;
 import org.apache.hertzbeat.alert.service.DataSourceService;
 import org.apache.hertzbeat.alert.util.AlertTemplateUtil;
@@ -26,11 +27,11 @@ import org.apache.hertzbeat.alert.util.AlertUtil;
 import org.apache.hertzbeat.common.constants.CommonConstants;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefine;
 import org.apache.hertzbeat.common.entity.alerter.SingleAlert;
+import org.springframework.stereotype.Component;
+
+import java.util.HashMap;
 import java.util.List;
 import java.util.Map;
-import org.apache.commons.lang3.StringUtils;
-import org.apache.commons.collections4.CollectionUtils;
-import org.springframework.stereotype.Component;

 /**
 * Periodic Alert Calculator
@@ -54,9 +55,9 @@ public class PeriodicAlertCalculator {
        this.alarmCacheManager = alarmCacheManager;
    }
    
-    public void calculate(AlertDefine rule) {
-        if (!rule.isEnable() || StringUtils.isEmpty(rule.getExpr())) {
-            log.error("Periodic rule {} is disabled or expression is empty", rule.getName());
+    public void calculate(AlertDefine define) {
+        if (!define.isEnable() || StringUtils.isEmpty(define.getExpr())) {
+            log.error("Periodic define {} is disabled or expression is empty", define.getName());
            return;
        }
        long currentTimeMilli = System.currentTimeMillis();
@@ -66,8 +67,8 @@ public class PeriodicAlertCalculator {
            // the return result should be matched with threshold
            try {
                List<Map<String, Object>> results = dataSourceService.calculate(
-                        rule.getDatasource(),
-                        rule.getExpr()
+                        define.getDatasource(),
+                        define.getExpr()
                );
                // if no match the expr threshold, the results item map {'value': null} should be null and others field keep
                // if results has multi list, should trigger multi alert
@@ -77,8 +78,9 @@ public class PeriodicAlertCalculator {
                for (Map<String, Object> result : results) {
                    Map<String, String> fingerPrints = new HashMap<>(8);
                    // here use the alert name as finger, not care the alert name may be changed
-                    fingerPrints.put(CommonConstants.LABEL_ALERT_NAME, rule.getName());
-                    fingerPrints.putAll(rule.getLabels());
+                    fingerPrints.put(CommonConstants.LABEL_DEFINE_ID, String.valueOf(define.getId()));
+                    fingerPrints.put(CommonConstants.LABEL_ALERT_NAME, define.getName());
+                    fingerPrints.putAll(define.getLabels());
                    for (Map.Entry<String, Object> entry : result.entrySet()) {
                        if (entry.getValue() != null && !VALUE.equals(entry.getKey())
                                && !TIMESTAMP.equals(entry.getKey())) {
@@ -87,32 +89,33 @@ public class PeriodicAlertCalculator {
                    }
                    if (result.get(VALUE) == null) {
                        // recovery the alert
-                        handleRecoveredAlert(fingerPrints);
+                        handleRecoveredAlert(define.getId(), fingerPrints);
                        continue;
                    }
                    Map<String, Object> fieldValueMap = new HashMap<>(8);
-                    fieldValueMap.putAll(rule.getLabels());
-                    fieldValueMap.put(CommonConstants.LABEL_ALERT_NAME, rule.getName());
+                    fieldValueMap.putAll(define.getLabels());
+                    fieldValueMap.put(CommonConstants.LABEL_ALERT_NAME, define.getName());
                    for (Map.Entry<String, Object> entry : result.entrySet()) {
                        if (entry.getValue() != null) {
                            fieldValueMap.put(entry.getKey(), entry.getValue());
                        }
                    }
-                    afterThresholdRuleMatch(currentTimeMilli, fingerPrints, fieldValueMap, rule);
+                    afterThresholdRuleMatch(currentTimeMilli, fingerPrints, fieldValueMap, define);
                }
            } catch (Exception ignored) {
                // ignore the query exception eg: no result, timeout, etc
                return;
            }
        } catch (Exception e) {
-            log.error("Calculate periodic rule {} failed: {}", rule.getName(), e.getMessage());
+            log.error("Calculate periodic define {} failed: {}", define.getName(), e.getMessage());
        }
    }

    private void afterThresholdRuleMatch(long currentTimeMilli, Map<String, String> fingerPrints,
                                         Map<String, Object> fieldValueMap, AlertDefine define) {
+        Long defineId = define.getId();
        String fingerprint = AlertUtil.calculateFingerprint(fingerPrints);
-        SingleAlert existingAlert = alarmCacheManager.getPending(fingerprint);
+        SingleAlert existingAlert = alarmCacheManager.getPending(defineId, fingerprint);
        Map<String, String> labels = new HashMap<>(8);
        fieldValueMap.putAll(define.getLabels());
        labels.putAll(fingerPrints);
@@ -133,11 +136,11 @@ public class PeriodicAlertCalculator {
            // If required trigger times is 1, set to firing status directly
            if (requiredTimes <= 1) {
                newAlert.setStatus(CommonConstants.ALERT_STATUS_FIRING);
-                alarmCacheManager.putFiring(fingerprint, newAlert);
+                alarmCacheManager.putFiring(defineId, fingerprint, newAlert);
                alarmCommonReduce.reduceAndSendAlarm(newAlert.clone());
            } else {
                // Otherwise put into pending queue first
-                alarmCacheManager.putPending(fingerprint, newAlert);
+                alarmCacheManager.putPending(defineId, fingerprint, newAlert);
            }
        } else {
            // Update existing alert
@@ -147,17 +150,17 @@ public class PeriodicAlertCalculator {
            // Check if required trigger times reached
            if (existingAlert.getStatus().equals(CommonConstants.ALERT_STATUS_PENDING) && existingAlert.getTriggerTimes() >= requiredTimes) {
                // Reached trigger times threshold, change to firing status
-                alarmCacheManager.removePending(fingerprint);
+                alarmCacheManager.removePending(defineId, fingerprint);
                existingAlert.setStatus(CommonConstants.ALERT_STATUS_FIRING);
-                alarmCacheManager.putFiring(fingerprint, existingAlert);
+                alarmCacheManager.putFiring(defineId, fingerprint, existingAlert);
                alarmCommonReduce.reduceAndSendAlarm(existingAlert.clone());
            }
        }
    }

-    private void handleRecoveredAlert(Map<String, String> fingerprints) {
+    private void handleRecoveredAlert(Long defineId, Map<String, String> fingerprints) {
        String fingerprint = AlertUtil.calculateFingerprint(fingerprints);
-        SingleAlert firingAlert = alarmCacheManager.removeFiring(fingerprint);
+        SingleAlert firingAlert = alarmCacheManager.removeFiring(defineId, fingerprint);
        if (firingAlert != null) {
            // todo consider multi times to tig for resolved alert
            firingAlert.setTriggerTimes(1);
@@ -165,7 +168,7 @@ public class PeriodicAlertCalculator {
            firingAlert.setStatus(CommonConstants.ALERT_STATUS_RESOLVED);
            alarmCommonReduce.reduceAndSendAlarm(firingAlert.clone());
        }
-        alarmCacheManager.removePending(fingerprint);
+        alarmCacheManager.removePending(defineId, fingerprint);
    }

 } 
@@ -183,9 +183,11 @@ public class RealTimeAlertCalculator {
            if (StringUtils.isBlank(expr)) {
                continue;
            }
+            Long defineId = define.getId();
            Map<String, String> commonFingerPrints = new HashMap<>(8);
            commonFingerPrints.put(CommonConstants.LABEL_INSTANCE, instance);
            // here use the alert name as finger, not care the alert name may be changed
+            commonFingerPrints.put(CommonConstants.LABEL_DEFINE_ID, String.valueOf(define.getId()));
            commonFingerPrints.put(CommonConstants.LABEL_ALERT_NAME, define.getName());
            commonFingerPrints.put(CommonConstants.LABEL_INSTANCE_NAME, instanceName);
            commonFingerPrints.put(CommonConstants.LABEL_INSTANCE_HOST, instanceHost);
@@ -200,9 +202,9 @@ public class RealTimeAlertCalculator {
                    try {
                        if (match) {
                            // If the threshold rule matches, the number of times the threshold has been triggered is determined and an alarm is triggered
-                            afterThresholdRuleMatch(currentTimeMilli, commonFingerPrints, fieldValueMap, define, annotations);
+                            afterThresholdRuleMatch(defineId, currentTimeMilli, commonFingerPrints, fieldValueMap, define, annotations);
                        } else {
-                            handleRecoveredAlert(commonFingerPrints);
+                            handleRecoveredAlert(defineId, commonFingerPrints);
                        }
                        // if this threshold pre compile success, ignore blew
                        continue;
@@ -254,9 +256,9 @@ public class RealTimeAlertCalculator {
                    boolean match = execAlertExpression(fieldValueMap, expr, false);
                    try {
                        if (match) {
-                            afterThresholdRuleMatch(currentTimeMilli, fingerPrints, fieldValueMap, define, annotations);
+                            afterThresholdRuleMatch(defineId, currentTimeMilli, fingerPrints, fieldValueMap, define, annotations);
                        } else {
-                            handleRecoveredAlert(fingerPrints);
+                            handleRecoveredAlert(defineId, fingerPrints);
                        }
                    } catch (Exception e) {
                        log.error(e.getMessage(), e);
@@ -334,9 +336,9 @@ public class RealTimeAlertCalculator {
                .collect(Collectors.toList());
    }

-    private void handleRecoveredAlert(Map<String, String> fingerprints) {
+    private void handleRecoveredAlert(Long defineId, Map<String, String> fingerprints) {
        String fingerprint = AlertUtil.calculateFingerprint(fingerprints);
-        SingleAlert firingAlert = alarmCacheManager.removeFiring(fingerprint);
+        SingleAlert firingAlert = alarmCacheManager.removeFiring(defineId, fingerprint);
        if (firingAlert != null) {
            // todo consider multi times to tig for resolved alert
            firingAlert.setTriggerTimes(1);
@@ -344,13 +346,14 @@ public class RealTimeAlertCalculator {
            firingAlert.setStatus(CommonConstants.ALERT_STATUS_RESOLVED);
            alarmCommonReduce.reduceAndSendAlarm(firingAlert.clone());
        }
-        alarmCacheManager.removePending(fingerprint);
+        alarmCacheManager.removePending(defineId, fingerprint);
    }

-    private void afterThresholdRuleMatch(long currentTimeMilli, Map<String, String> fingerPrints,
-                                         Map<String, Object> fieldValueMap, AlertDefine define, Map<String, String> annotations) {
+    private void afterThresholdRuleMatch(long defineId, long currentTimeMilli, Map<String, String> fingerPrints,
+                                         Map<String, Object> fieldValueMap, AlertDefine define,
+                                         Map<String, String> annotations) {
        String fingerprint = AlertUtil.calculateFingerprint(fingerPrints);
-        SingleAlert existingAlert = alarmCacheManager.getPending(fingerprint);
+        SingleAlert existingAlert = alarmCacheManager.getPending(defineId, fingerprint);
        fieldValueMap.putAll(define.getLabels());
        int requiredTimes = define.getTimes() == null ? 1 : define.getTimes();
        if (existingAlert == null) {
@@ -382,11 +385,11 @@ public class RealTimeAlertCalculator {
            // If required trigger times is 1, set to firing status directly
            if (requiredTimes <= 1) {
                newAlert.setStatus(CommonConstants.ALERT_STATUS_FIRING);
-                alarmCacheManager.putFiring(fingerprint, newAlert);
+                alarmCacheManager.putFiring(defineId, fingerprint, newAlert);
                alarmCommonReduce.reduceAndSendAlarm(newAlert.clone());
            } else {
                // Otherwise put into pending queue first
-                alarmCacheManager.putPending(fingerprint, newAlert);
+                alarmCacheManager.putPending(define.getId(), fingerprint, newAlert);
            }
        } else {
            // Update existing alert
@@ -396,9 +399,9 @@ public class RealTimeAlertCalculator {
            // Check if required trigger times reached
            if (existingAlert.getStatus().equals(CommonConstants.ALERT_STATUS_PENDING) && existingAlert.getTriggerTimes() >= requiredTimes) {
                // Reached trigger times threshold, change to firing status
-                alarmCacheManager.removePending(fingerprint);
+                alarmCacheManager.removePending(defineId, fingerprint);
                existingAlert.setStatus(CommonConstants.ALERT_STATUS_FIRING);
-                alarmCacheManager.putFiring(fingerprint, existingAlert);
+                alarmCacheManager.putFiring(defineId, fingerprint, existingAlert);
                alarmCommonReduce.reduceAndSendAlarm(existingAlert.clone());
            }
        }
@@ -17,17 +17,16 @@

 package org.apache.hertzbeat.alert.controller;

-import static org.apache.hertzbeat.common.constants.CommonConstants.MONITOR_NOT_EXIST_CODE;
-import static org.springframework.http.MediaType.APPLICATION_JSON_VALUE;
 import io.swagger.v3.oas.annotations.Operation;
 import io.swagger.v3.oas.annotations.Parameter;
 import io.swagger.v3.oas.annotations.tags.Tag;
 import jakarta.validation.Valid;
-import java.util.Objects;
 import org.apache.hertzbeat.alert.service.AlertDefineService;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefine;
 import org.apache.hertzbeat.common.entity.dto.Message;
+import org.apache.hertzbeat.common.support.exception.AlertExpressionException;
 import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.http.HttpStatus;
 import org.springframework.http.ResponseEntity;
 import org.springframework.web.bind.annotation.DeleteMapping;
 import org.springframework.web.bind.annotation.GetMapping;
@@ -36,8 +35,17 @@ import org.springframework.web.bind.annotation.PostMapping;
 import org.springframework.web.bind.annotation.PutMapping;
 import org.springframework.web.bind.annotation.RequestBody;
 import org.springframework.web.bind.annotation.RequestMapping;
+import org.springframework.web.bind.annotation.RequestParam;
 import org.springframework.web.bind.annotation.RestController;

+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+
+import static org.apache.hertzbeat.common.constants.CommonConstants.FAIL_CODE;
+import static org.apache.hertzbeat.common.constants.CommonConstants.MONITOR_NOT_EXIST_CODE;
+import static org.springframework.http.MediaType.APPLICATION_JSON_VALUE;
+
 /**
 * Alarm definition management API
 */
@@ -90,4 +98,18 @@ public class AlertDefineController {
        return ResponseEntity.ok(Message.success("Delete success"));
    }

+    @GetMapping(path = "/preview/{datasource}")
+    @Operation(summary = "Alarm definition expression preview",
+            description = "If the expression is formal, then the result of the query will be returned, otherwise it will respond with an error")
+    public ResponseEntity<Message<List<Map<String, Object>>>> getDefinePreview(
+            @Parameter(description = "Data Source Type", example = "promql") @PathVariable("datasource") String datasource,
+            @Parameter(description = "alert threshold type:realtime,periodic") @RequestParam String type,
+            @Parameter(description = "alert threshold expression") @RequestParam String expr) {
+        try {
+            return ResponseEntity.ok(Message.successWithData(alertDefineService.getDefinePreview(datasource, type, expr)));
+        } catch (AlertExpressionException ae) {
+            return ResponseEntity.status(HttpStatus.BAD_REQUEST).body(Message.fail(FAIL_CODE, ae.getMessage()));
+        }
+    }
+
 }
@@ -18,12 +18,15 @@
 package org.apache.hertzbeat.alert.service;

 import jakarta.servlet.http.HttpServletResponse;
-import java.util.List;
-import java.util.Set;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefine;
+import org.apache.hertzbeat.common.support.exception.AlertExpressionException;
 import org.springframework.data.domain.Page;
 import org.springframework.web.multipart.MultipartFile;

+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
 /**
 * Alarm define manager service
 */
@@ -107,5 +110,11 @@ public interface AlertDefineService {
     * @return Real-time alarm definition list
     */
    List<AlertDefine> getRealTimeAlertDefines();
-    
+
+    /**
+     * Get define preview
+     * @return Data queried based on expressions
+     * @throws AlertExpressionException expression error
+     */
+    List<Map<String, Object>> getDefinePreview(String datasource, String type, String expr);
 }
@@ -28,6 +28,9 @@ import org.apache.hertzbeat.alert.dto.ExportAlertDefineDTO;
 import org.apache.hertzbeat.alert.service.AlertDefineImExportService;
 import org.apache.hertzbeat.alert.service.AlertDefineService;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefine;
+import org.apache.hertzbeat.common.util.LogUtil;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
 import org.springframework.beans.BeanUtils;
 import org.springframework.context.annotation.Lazy;
 import org.springframework.util.CollectionUtils;
@@ -41,12 +44,15 @@ public abstract class AlertDefineAbstractImExportServiceImpl implements AlertDef
    @Lazy
    private AlertDefineService alertDefineService;

+    private static final Logger logger = LoggerFactory.getLogger(AlertDefineAbstractImExportServiceImpl.class);
+
    @Override
    public void importConfig(InputStream is) {
        var formList = parseImport(is)
                .stream()
                .map(this::convert)
                .toList();
+        LogUtil.info(logger, "Importing alert defines from {0}", formList);
        if (!CollectionUtils.isEmpty(formList)) {
            formList.forEach(alertDefine -> {
                alertDefineService.validate(alertDefine, false);
@@ -17,7 +17,6 @@

 package org.apache.hertzbeat.alert.service.impl;

-import static org.apache.hertzbeat.common.constants.CommonConstants.ALERT_THRESHOLD_TYPE_REALTIME;
 import com.fasterxml.jackson.core.JsonProcessingException;
 import com.fasterxml.jackson.core.type.TypeReference;
 import com.fasterxml.jackson.databind.ObjectMapper;
@@ -29,7 +28,9 @@ import org.apache.hertzbeat.alert.calculate.PeriodicAlertRuleScheduler;
 import org.apache.hertzbeat.alert.dao.AlertDefineDao;
 import org.apache.hertzbeat.alert.service.AlertDefineImExportService;
 import org.apache.hertzbeat.alert.service.AlertDefineService;
+import org.apache.hertzbeat.alert.service.DataSourceService;
 import org.apache.hertzbeat.common.cache.CacheFactory;
+import org.apache.hertzbeat.common.constants.CommonConstants;
 import org.apache.hertzbeat.common.constants.ExportFileConstants;
 import org.apache.hertzbeat.common.constants.SignConstants;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefine;
@@ -72,18 +73,21 @@ public class AlertDefineServiceImpl implements AlertDefineService {
    @Autowired
    private PeriodicAlertRuleScheduler periodicAlertRuleScheduler;

+    private final DataSourceService dataSourceService;
+
    private final Map<String, AlertDefineImExportService> alertDefineImExportServiceMap = new HashMap<>();

    private static final String CONTENT_TYPE = MediaType.APPLICATION_OCTET_STREAM_VALUE + SignConstants.SINGLE_MARK + "charset=" + StandardCharsets.UTF_8;

-    public AlertDefineServiceImpl(List<AlertDefineImExportService> alertDefineImExportServiceList) {
+    public AlertDefineServiceImpl(List<AlertDefineImExportService> alertDefineImExportServiceList, DataSourceService dataSourceService) {
        alertDefineImExportServiceList.forEach(it -> alertDefineImExportServiceMap.put(it.type(), it));
+        this.dataSourceService = dataSourceService;
    }

    @Override
    public void validate(AlertDefine alertDefine, boolean isModify) throws IllegalArgumentException {
        if (StringUtils.hasText(alertDefine.getExpr())) {
-            if (ALERT_THRESHOLD_TYPE_REALTIME.equals(alertDefine.getType())) {
+            if (CommonConstants.ALERT_THRESHOLD_TYPE_REALTIME.equals(alertDefine.getType())) {
                try {
                    JexlExpressionRunner.compile(alertDefine.getExpr());
                } catch (Exception e) {
@@ -213,9 +217,23 @@ public class AlertDefineServiceImpl implements AlertDefineService {
    public List<AlertDefine> getRealTimeAlertDefines() {
        List<AlertDefine> alertDefines = CacheFactory.getAlertDefineCache();
        if (alertDefines == null) {
-            alertDefines = alertDefineDao.findAlertDefinesByTypeAndEnableTrue(ALERT_THRESHOLD_TYPE_REALTIME);
+            alertDefines = alertDefineDao.findAlertDefinesByTypeAndEnableTrue(CommonConstants.ALERT_THRESHOLD_TYPE_REALTIME);
            CacheFactory.setAlertDefineCache(alertDefines);
        }
        return alertDefines;
    }
+
+    @Override
+    public List<Map<String, Object>> getDefinePreview(String datasource, String type, String expr) {
+        if (!StringUtils.hasText(expr) || !StringUtils.hasText(datasource) || !StringUtils.hasText(type)) {
+            return Collections.emptyList();
+        }
+        switch (type) {
+            case CommonConstants.ALERT_THRESHOLD_TYPE_PERIODIC:
+                return dataSourceService.calculate(datasource, expr);
+            default:
+                log.error("Get define preview unsupported type: {}", type);
+                return Collections.emptyList();
+        }
+    }
 }
@@ -27,11 +27,14 @@ import org.apache.hertzbeat.common.entity.alerter.NoticeReceiver;
 import org.apache.hertzbeat.common.entity.alerter.NoticeTemplate;
 import org.apache.hertzbeat.common.support.exception.SendMessageException;
 import org.apache.hertzbeat.common.util.JsonUtil;
+import org.apache.hertzbeat.common.util.LogUtil;
 import org.apache.http.client.methods.CloseableHttpResponse;
 import org.apache.http.client.methods.HttpPost;
 import org.apache.http.impl.client.CloseableHttpClient;
 import org.apache.http.impl.client.HttpClients;
 import org.apache.http.util.EntityUtils;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;

 import java.nio.charset.StandardCharsets;
 import java.text.SimpleDateFormat;
@@ -62,6 +65,7 @@ public class AlibabaSmsClientImpl implements SmsClient {
    private final String accessKeySecret;
    private final String signName;
    private final String templateCode;
+    private static final Logger logger = LoggerFactory.getLogger(AlibabaSmsClientImpl.class);

    public AlibabaSmsClientImpl(AlibabaSmsProperties config) {
        if (config != null) {
@@ -173,7 +177,7 @@ public class AlibabaSmsClientImpl implements SmsClient {
                log.info("Successfully sent SMS to phone: {}", phoneNumber);
            }
        } catch (Exception e) {
-            log.warn("Failed to send SMS: {}", e.getMessage());
+            LogUtil.warn(logger, "Failed to send SMS: {0}", e.getMessage());
            throw new SendMessageException(e.getMessage());
        }
    }
@@ -192,6 +196,7 @@ public class AlibabaSmsClientImpl implements SmsClient {
            // Step 4: Build authorization header
            return ALGORITHM + " Credential=" + accessKeyId + ",SignedHeaders=host;x-acs-action;x-acs-content-sha256;x-acs-date;" + "x-acs-signature-nonce;x-acs-version,Signature=" + signature;
        } catch (Exception e) {
+            LogUtil.warn(logger, "Failed to calculate authorization {0}", e.getMessage());
            throw new RuntimeException("Failed to calculate authorization", e);
        }
    }
@@ -24,11 +24,14 @@ import lombok.Setter;
 import lombok.extern.slf4j.Slf4j;
 import org.antlr.v4.runtime.CharStreams;
 import org.antlr.v4.runtime.CommonTokenStream;
+import org.antlr.v4.runtime.Token;
 import org.antlr.v4.runtime.tree.ParseTree;
 import org.apache.hertzbeat.alert.expr.AlertExpressionEvalVisitor;
 import org.apache.hertzbeat.alert.expr.AlertExpressionLexer;
 import org.apache.hertzbeat.alert.expr.AlertExpressionParser;
 import org.apache.hertzbeat.alert.service.DataSourceService;
+import org.apache.hertzbeat.common.support.exception.AlertExpressionException;
+import org.apache.hertzbeat.common.util.ResourceBundleUtil;
 import org.apache.hertzbeat.warehouse.db.QueryExecutor;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.stereotype.Service;
@@ -36,6 +39,7 @@ import org.springframework.util.StringUtils;

 import java.util.List;
 import java.util.Map;
+import java.util.ResourceBundle;
 import java.util.concurrent.TimeUnit;

 /**
@@ -45,6 +49,8 @@ import java.util.concurrent.TimeUnit;
@Slf4j
 public class DataSourceServiceImpl implements DataSourceService {

+    protected ResourceBundle bundle = ResourceBundleUtil.getBundle("alerter");
+
    @Setter
    @Autowired(required = false)
    private List<QueryExecutor> executors;
@@ -80,6 +86,9 @@ public class DataSourceServiceImpl implements DataSourceService {
        expr = expr.replaceAll("\\s+", " ");
        try {
            return evaluate(expr, executor);
+        } catch (AlertExpressionException ae) {
+            log.error("Calculate query parse error {}: {}", datasource, ae.getMessage());
+            throw ae;
        } catch (Exception e) {
            log.error("Error executing query on datasource {}: {}", datasource, e.getMessage());
            throw new RuntimeException("Query execution failed", e);
@@ -90,9 +99,11 @@ public class DataSourceServiceImpl implements DataSourceService {
        CommonTokenStream tokens = tokenStreamCache.get(expr, this::createTokenStream);
        AlertExpressionParser parser = new AlertExpressionParser(tokens);
        ParseTree tree = expressionCache.get(expr, e -> parser.expr());
+        if (null != tokens && tokens.LA(1) != Token.EOF) {
+            throw new AlertExpressionException(bundle.getString("alerter.calculate.parse.error"));
+        }
        AlertExpressionEvalVisitor visitor = new AlertExpressionEvalVisitor(executor, tokens);
        return visitor.visit(tree);
-
    }

    private CommonTokenStream createTokenStream(String expr) {
@@ -32,3 +32,4 @@ alerter.notify.console = Console Login
 alerter.priority.0 = Emergency Alert
 alerter.priority.1 = Critical Alert
 alerter.priority.2 = Warning Alert
+alerter.calculate.parse.error = Expression is not fully parsed, may have syntax errors or incomplete inputs
@@ -32,3 +32,4 @@ alerter.notify.console = 登入控制台
 alerter.priority.0 = 紧急告警
 alerter.priority.1 = 严重告警
 alerter.priority.2 = 警告告警
+alerter.calculate.parse.error = 表达式未完全解析，可能存在语法错误或输入不完整
@@ -32,3 +32,4 @@ alerter.notify.console = 控制台登錄
 alerter.priority.0 = 緊急警報
 alerter.priority.1 = 嚴重警報
 alerter.priority.2 = 警告警報
+alerter.calculate.parse.error = 表達式未完全解析，可能存在語法錯誤或輸入不完整
@@ -0,0 +1,135 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hertzbeat.alert.calculate;
+
+import org.apache.hertzbeat.alert.dao.SingleAlertDao;
+import org.apache.hertzbeat.alert.util.AlertUtil;
+import org.apache.hertzbeat.common.constants.CommonConstants;
+import org.apache.hertzbeat.common.entity.alerter.SingleAlert;
+import org.junit.jupiter.api.BeforeEach;
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.extension.ExtendWith;
+import org.mockito.Mock;
+import org.mockito.junit.jupiter.MockitoExtension;
+
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.Map;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertNotNull;
+import static org.junit.jupiter.api.Assertions.assertNull;
+import static org.mockito.Mockito.when;
+
+/**
+ * alert cache manager test
+ */
+@ExtendWith(MockitoExtension.class)
+public class AlarmCacheManagerTest {
+
+    @Mock
+    private SingleAlertDao singleAlertDao;
+
+    private AlarmCacheManager alarmCacheManager;
+
+    @BeforeEach
+    public void setUp() {
+        Map<String, String> labels = new HashMap<>();
+        labels.put(CommonConstants.LABEL_ALERT_SEVERITY, CommonConstants.ALERT_SEVERITY_CRITICAL);
+        labels.put(CommonConstants.LABEL_DEFINE_ID, String.valueOf(1L));
+        SingleAlert alert = new SingleAlert();
+        alert.setContent("Alert cache manager test");
+        alert.setLabels(labels);
+        when(singleAlertDao.querySingleAlertsByStatus(CommonConstants.ALERT_STATUS_FIRING)).thenReturn(Collections.singletonList(alert));
+        alarmCacheManager = new AlarmCacheManager(singleAlertDao);
+    }
+
+    @Test
+    void testInit() {
+        Map<String, String> labels = new HashMap<>();
+        labels.put(CommonConstants.LABEL_ALERT_SEVERITY, CommonConstants.ALERT_SEVERITY_CRITICAL);
+        labels.put(CommonConstants.LABEL_DEFINE_ID, String.valueOf(1L));
+
+        String fingerprint = AlertUtil.calculateFingerprint(labels);
+        SingleAlert firingSingleAlert = alarmCacheManager.getFiring(1L, fingerprint);
+        assertNotNull(firingSingleAlert);
+        assertEquals("Alert cache manager test", firingSingleAlert.getContent());
+        alarmCacheManager.removeFiring(1L, fingerprint);
+        firingSingleAlert = alarmCacheManager.getFiring(1L, fingerprint);
+        assertNull(firingSingleAlert);
+    }
+
+    @Test
+    void testPending() {
+        Map<String, String> labels = new HashMap<>();
+        labels.put(CommonConstants.LABEL_ALERT_SEVERITY, CommonConstants.ALERT_SEVERITY_CRITICAL);
+        labels.put(CommonConstants.ALERT_SEVERITY_INFO, CommonConstants.ALERT_STATUS_PENDING);
+        labels.put(CommonConstants.LABEL_DEFINE_ID, String.valueOf(2L));
+
+        SingleAlert alert = new SingleAlert();
+        alert.setContent("Alert cache manager test");
+        alert.setLabels(labels);
+
+        String fingerprint = AlertUtil.calculateFingerprint(alert.getLabels());
+        alarmCacheManager.putPending(2L, fingerprint, alert);
+
+        SingleAlert pendingSingleAlert = alarmCacheManager.getPending(2L, fingerprint);
+        assertNotNull(pendingSingleAlert);
+        alarmCacheManager.removePending(2L, fingerprint);
+        pendingSingleAlert = alarmCacheManager.getPending(2L, fingerprint);
+        assertNull(pendingSingleAlert);
+    }
+
+    @Test
+    void testFiring() {
+        Map<String, String> labels = new HashMap<>();
+        labels.put(CommonConstants.LABEL_ALERT_SEVERITY, CommonConstants.ALERT_SEVERITY_CRITICAL);
+        labels.put(CommonConstants.ALERT_SEVERITY_INFO, CommonConstants.ALERT_STATUS_PENDING);
+        labels.put(CommonConstants.LABEL_DEFINE_ID, String.valueOf(3L));
+
+        SingleAlert alert = new SingleAlert();
+        alert.setContent("Alert cache manager test");
+        alert.setLabels(labels);
+
+        String fingerprint = AlertUtil.calculateFingerprint(alert.getLabels());
+        alarmCacheManager.putFiring(3L, fingerprint, alert);
+
+        SingleAlert firingSingleAlert = alarmCacheManager.getFiring(3L, fingerprint);
+        assertNotNull(firingSingleAlert);
+        alarmCacheManager.removeFiring(3L, fingerprint);
+        firingSingleAlert = alarmCacheManager.getFiring(3L, fingerprint);
+        assertNull(firingSingleAlert);
+    }
+
+    @Test
+    void testHistorical() {
+        SingleAlert alert = new SingleAlert();
+        alert.setContent("Alert cache manager test");
+        alert.setLabels(Collections.singletonMap(CommonConstants.LABEL_ALERT_SEVERITY, CommonConstants.ALERT_SEVERITY_CRITICAL));
+        when(singleAlertDao.querySingleAlertsByStatus(CommonConstants.ALERT_STATUS_FIRING)).thenReturn(Collections.singletonList(alert));
+        alarmCacheManager = new AlarmCacheManager(singleAlertDao);
+
+        String fingerprint = AlertUtil.calculateFingerprint(alert.getLabels());
+        SingleAlert historicalSingleAlert = alarmCacheManager.getFiring(4L, fingerprint);
+        assertNotNull(historicalSingleAlert);
+        SingleAlert singleAlert = alarmCacheManager.removeFiring(4L, fingerprint);
+        assertNotNull(singleAlert);
+        historicalSingleAlert = alarmCacheManager.getFiring(4L, fingerprint);
+        assertNull(historicalSingleAlert);
+    }
+}
@@ -42,6 +42,7 @@ import static org.junit.jupiter.api.Assertions.assertNotNull;
 import static org.junit.jupiter.api.Assertions.assertTrue;
 import static org.mockito.ArgumentMatchers.any;
 import static org.mockito.ArgumentMatchers.anyString;
+import static org.mockito.ArgumentMatchers.eq;
 import static org.mockito.Mockito.reset;
 import static org.mockito.Mockito.times;
 import static org.mockito.Mockito.verify;
@@ -92,12 +93,12 @@ class PeriodicAlertCalculatorTest {
        result.put("__value__", 95.0); // Non-null, matched with threshold
        result.put("__timestamp__", System.currentTimeMillis());
        when(dataSourceService.calculate(anyString(), anyString())).thenReturn(List.of(result));
-        when(alarmCacheManager.getPending(anyString())).thenReturn(null);
+        when(alarmCacheManager.getPending(eq(rule.getId()), anyString())).thenReturn(null);
        periodicAlertCalculator.calculate(rule);
        // Verify that putFiring is called
        ArgumentCaptor<String> idCaptor = ArgumentCaptor.forClass(String.class);
        ArgumentCaptor<SingleAlert> alertCaptor = ArgumentCaptor.forClass(SingleAlert.class);
-        verify(alarmCacheManager).putFiring(idCaptor.capture(), alertCaptor.capture());
+        verify(alarmCacheManager).putFiring(eq(rule.getId()), idCaptor.capture(), alertCaptor.capture());
        // Assertion alarm status and content
        SingleAlert alert = alertCaptor.getValue();
        assertAll(() -> assertEquals(CommonConstants.ALERT_STATUS_FIRING, alert.getStatus()),
@@ -112,7 +113,7 @@ class PeriodicAlertCalculatorTest {
        result.put("__timestamp__", System.currentTimeMillis());
        when(dataSourceService.calculate(anyString(), anyString())).thenReturn(List.of(result));
        periodicAlertCalculator.calculate(rule);
-        verify(alarmCacheManager, times(0)).putFiring(any(), any());
+        verify(alarmCacheManager, times(0)).putFiring(any(), any(), any());
    }

    @Test
@@ -126,7 +127,7 @@ class PeriodicAlertCalculatorTest {
                .triggerTimes(2).startAt(System.currentTimeMillis() - 60000)
                .activeAt(System.currentTimeMillis() - 30000)
                .build();
-        when(alarmCacheManager.removeFiring(anyString())).thenReturn(pendingAlert);
+        when(alarmCacheManager.removeFiring(eq(rule.getId()), anyString())).thenReturn(pendingAlert);
        when(dataSourceService.calculate(anyString(), anyString())).thenReturn(List.of(result));
        periodicAlertCalculator.calculate(rule);
        ArgumentCaptor<SingleAlert> resolvedCaptor = ArgumentCaptor.forClass(SingleAlert.class);
@@ -132,6 +132,7 @@ public class RealTimeAlertCalculatorMatchTest {


        AlertDefine matchDefine = new AlertDefine();
+        matchDefine.setId(1L);
        matchDefine.setName("test");
        matchDefine.setExpr(
            "equals(__app__,\"prometheus\") && "
@@ -151,8 +152,8 @@ public class RealTimeAlertCalculatorMatchTest {

        Thread.sleep(3000);

-        verify(alarmCacheManager, times(1)).getPending(any());
-        verify(alarmCacheManager, times(1)).putFiring(any(), any());
+        verify(alarmCacheManager, times(1)).getPending(any(), any());
+        verify(alarmCacheManager, times(1)).putFiring(any(), any(), any());
        verify(alarmCommonReduce, times(1)).reduceAndSendAlarm(any());
    }

@@ -180,6 +181,7 @@ public class RealTimeAlertCalculatorMatchTest {
        CollectRep.MetricsData metricsData = builder.build();

        AlertDefine matchDefine = new AlertDefine();
+        matchDefine.setId(1L);
        matchDefine.setName("test");
        matchDefine.setExpr("equals(__app__,\"prometheus\") && equals(__metrics__,\"canal_instance\") && metric_value > 0");
        matchDefine.setTemplate("Canal instance val: ${value}%");
@@ -194,8 +196,8 @@ public class RealTimeAlertCalculatorMatchTest {

        Thread.sleep(3000);

-        verify(alarmCacheManager, times(1)).getPending(any());
-        verify(alarmCacheManager, times(1)).putFiring(any(), any());
+        verify(alarmCacheManager, times(1)).getPending(any(), any());
+        verify(alarmCacheManager, times(1)).putFiring(any(), any(), any());
        verify(alarmCommonReduce, times(1)).reduceAndSendAlarm(any());
    }

@@ -229,6 +231,7 @@ public class RealTimeAlertCalculatorMatchTest {
        CollectRep.MetricsData metricsData = builder.build();

        AlertDefine matchDefine = new AlertDefine();
+        matchDefine.setId(1L);
        matchDefine.setName("test");
        matchDefine.setExpr("equals(__app__,\"springboot3\") && equals(__metrics__,\"available\") && equals(__instance__, \"518679137103104\") && responseTime > 0");
        matchDefine.setTemplate("Canal instance val: ${value}%");
@@ -243,8 +246,8 @@ public class RealTimeAlertCalculatorMatchTest {

        Thread.sleep(3000);

-        verify(alarmCacheManager, times(1)).getPending(any());
-        verify(alarmCacheManager, times(1)).putFiring(any(), any());
+        verify(alarmCacheManager, times(1)).getPending(any(), any());
+        verify(alarmCacheManager, times(1)).putFiring(any(), any(), any());
        verify(alarmCommonReduce, times(1)).reduceAndSendAlarm(any());
    }

@@ -17,15 +17,22 @@

 package org.apache.hertzbeat.alert.controller;

+import static org.mockito.ArgumentMatchers.anyString;
 import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.jsonPath;
 import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.status;
+
+import java.util.ArrayList;
 import java.util.Collections;
+import java.util.HashMap;
 import java.util.List;
+import java.util.Map;
+
 import org.apache.hertzbeat.alert.service.impl.AlertDefineServiceImpl;
 import org.apache.hertzbeat.common.constants.CommonConstants;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefine;
 import org.apache.hertzbeat.common.entity.alerter.AlertDefineMonitorBind;
 import org.apache.hertzbeat.common.entity.manager.Monitor;
+import org.apache.hertzbeat.common.support.exception.AlertExpressionException;
 import org.apache.hertzbeat.common.util.JsonUtil;
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Test;
@@ -100,6 +107,37 @@ class AlertDefineControllerTest {
                .andReturn();
    }

+    @Test
+    void testGetDefinePreview() throws Exception {
+        List<Map<String, Object>> previewData = new ArrayList<>();
+        Map<String, Object> row = new HashMap<>();
+        row.put("__value__", 123);
+        row.put("job", "spring-boot");
+        previewData.add(row);
+
+        Mockito.when(alertDefineService.getDefinePreview(anyString(), anyString(), anyString()))
+                .thenReturn(previewData);
+
+        mockMvc.perform(MockMvcRequestBuilders.get("/api/alert/define/preview/{datasource}", "promql")
+                        .param("type", "periodic")
+                        .param("expr", "up == 1"))
+                .andExpect(status().isOk())
+                .andExpect(jsonPath("$.code").value(0))
+                .andExpect(jsonPath("$.data[0].__value__").value(123))
+                .andExpect(jsonPath("$.data[0].job").value("spring-boot"));
+
+        Mockito.when(alertDefineService.getDefinePreview(anyString(), anyString(), anyString()))
+                .thenThrow(new AlertExpressionException("Expression error"));
+
+        mockMvc.perform(MockMvcRequestBuilders.get("/api/alert/define/preview/{datasource}", "promql")
+                        .param("type", "periodic")
+                        .param("expr", "http_server_requests_seconds_count{!@~!!#$%^&}"))
+                .andExpect(status().isBadRequest())
+                .andExpect(jsonPath("$.code").exists())
+                .andExpect(jsonPath("$.msg").value("Expression error"));
+
+    }
+
    @Test
    void modifyAlertDefine() throws Exception {
        mockMvc.perform(MockMvcRequestBuilders.put("/api/alert/define")
@@ -17,19 +17,7 @@

 package org.apache.hertzbeat.alert.service;

-import static org.junit.jupiter.api.Assertions.assertDoesNotThrow;
-import static org.junit.jupiter.api.Assertions.assertNotNull;
-import static org.junit.jupiter.api.Assertions.assertThrows;
-import static org.mockito.Mockito.any;
-import static org.mockito.Mockito.anySet;
-import static org.mockito.Mockito.doNothing;
-import static org.mockito.Mockito.reset;
-import static org.mockito.Mockito.times;
-import static org.mockito.Mockito.verify;
-import static org.mockito.Mockito.when;
-import java.util.HashSet;
-import java.util.List;
-import java.util.Optional;
+import com.google.common.collect.Lists;
 import org.apache.hertzbeat.alert.calculate.PeriodicAlertRuleScheduler;
 import org.apache.hertzbeat.alert.dao.AlertDefineDao;
 import org.apache.hertzbeat.alert.service.impl.AlertDefineServiceImpl;
@@ -45,6 +33,27 @@ import org.springframework.data.domain.PageRequest;
 import org.springframework.data.jpa.domain.Specification;
 import org.springframework.test.util.ReflectionTestUtils;

+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Optional;
+
+import static org.apache.hertzbeat.common.constants.CommonConstants.ALERT_THRESHOLD_TYPE_PERIODIC;
+import static org.apache.hertzbeat.common.constants.CommonConstants.ALERT_THRESHOLD_TYPE_REALTIME;
+import static org.junit.jupiter.api.Assertions.assertDoesNotThrow;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertNotNull;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+import static org.mockito.ArgumentMatchers.eq;
+import static org.mockito.Mockito.any;
+import static org.mockito.Mockito.anySet;
+import static org.mockito.Mockito.doNothing;
+import static org.mockito.Mockito.reset;
+import static org.mockito.Mockito.times;
+import static org.mockito.Mockito.verify;
+import static org.mockito.Mockito.when;
+
 /**
 * Test case for {@link AlertDefineService}
 */
@@ -62,6 +71,9 @@ class AlertDefineServiceTest {
    @Mock
    private List<AlertDefineImExportService> alertDefineImExportServiceList;

+    @Mock
+    private DataSourceService dataSourceService;
+
    @InjectMocks
    private AlertDefineServiceImpl alertDefineService;

@@ -131,4 +143,36 @@ class AlertDefineServiceTest {
        assertNotNull(alertDefineService.getAlertDefines(null, null, "id", "desc", 1, 10));
        verify(alertDefineDao, times(1)).findAll(any(Specification.class), any(PageRequest.class));
    }
+
+    @Test
+    void getDefinePreview() {
+        String expr = "http_server_requests_seconds_count > 10";
+
+        Map<String, Object> countValue1 = new HashMap<>() {
+            {
+                put("exception", "none");
+                put("instance", "host.docker.internal:8989");
+                put("__value__", 1307);
+                put("method", "GET");
+                put("__name__", "http_server_requests_seconds_count");
+                put("__timestamp__", "1.750320922467E9");
+                put("error", "none");
+                put("job", "spring-boot-app");
+                put("uri", "/actuator/prometheus");
+                put("outcome", "SUCCESS");
+                put("status", "200");
+            }
+        };
+        when(dataSourceService.calculate(eq("promql"), eq(expr))).thenReturn(Lists.newArrayList(countValue1));
+        List<Map<String, Object>> result = alertDefineService.getDefinePreview("promql", ALERT_THRESHOLD_TYPE_PERIODIC, expr);
+        assertNotNull(result);
+        assertEquals(1307, result.get(0).get("__value__"));
+
+        result = alertDefineService.getDefinePreview("promql", ALERT_THRESHOLD_TYPE_PERIODIC, null);
+        assertEquals(0, result.size());
+
+        result = alertDefineService.getDefinePreview("promql", ALERT_THRESHOLD_TYPE_REALTIME, null);
+        assertEquals(0, result.size());
+    }
+
 }
@@ -21,6 +21,7 @@ import com.github.benmanes.caffeine.cache.Cache;
 import org.antlr.v4.runtime.CommonTokenStream;
 import org.antlr.v4.runtime.tree.ParseTree;
 import org.apache.hertzbeat.alert.service.impl.DataSourceServiceImpl;
+import org.apache.hertzbeat.common.support.exception.AlertExpressionException;
 import org.apache.hertzbeat.warehouse.db.QueryExecutor;
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Test;
@@ -34,6 +35,9 @@ import java.util.Map;
 import static org.junit.jupiter.api.Assertions.assertEquals;
 import static org.junit.jupiter.api.Assertions.assertNotNull;
 import static org.junit.jupiter.api.Assertions.assertNull;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+import static org.mockito.ArgumentMatchers.eq;
+import static org.mockito.Mockito.when;

 /**
 * test case for {@link DataSourceService}
@@ -555,7 +559,6 @@ class DataSourceServiceTest {
        tokenStreamCache.invalidateAll();
        long beforeHits = tokenStreamCache.stats().hitCount();
        dataSourceService.calculate("promql", expr);
-        expressionCache.invalidateAll();
        dataSourceService.calculate("promql", expr);
        long actualHits = tokenStreamCache.stats().hitCount() - beforeHits;
        assertEquals(1, actualHits, "expression cache should hit but miss");
@@ -606,4 +609,34 @@ class DataSourceServiceTest {
        long actualHits = tokenStreamCache.stats().hitCount() - beforeHits;
        assertEquals(0, actualHits, "expression cache should miss but hit");
    }
+
+    @Test
+    void testAlertExpressionException() {
+        List<Map<String, Object>> prometheusData = List.of(
+                new HashMap<>() {
+                    {
+                        put("exception", "none");
+                        put("instance", "host.docker.internal:8989");
+                        put("__value__", 1307);
+                        put("method", "GET");
+                        put("__name__", "http_server_requests_seconds_count");
+                        put("__timestamp__", "1.750320922467E9");
+                        put("error", "none");
+                        put("job", "spring-boot-app");
+                        put("uri", "/actuator/prometheus");
+                        put("outcome", "SUCCESS");
+                        put("status", "200");
+                    }
+                });
+        QueryExecutor mockExecutor = Mockito.mock(QueryExecutor.class);
+        when(mockExecutor.support(eq("promql"))).thenReturn(true);
+        when(mockExecutor.execute(eq("http_server_requests_seconds_count"))).thenReturn(prometheusData);
+
+        dataSourceService.setExecutors(List.of(mockExecutor));
+        List<Map<String, Object>> result = dataSourceService.calculate("promql", "http_server_requests_seconds_count > 10");
+        assertNotNull(result);
+        assertEquals(1307, result.get(0).get("__value__"));
+
+        assertThrows(AlertExpressionException.class, () -> dataSourceService.calculate("promql", "http_server_requests_seconds_count{!@~!!#$%^&}"));
+    }
 }
@@ -42,7 +42,6 @@ import javax.management.remote.JMXServiceURL;
 import javax.management.remote.rmi.RMIConnectorServer;
 import javax.naming.Context;
 import javax.rmi.ssl.SslRMIClientSocketFactory;
-import lombok.extern.slf4j.Slf4j;
 import org.apache.hertzbeat.collector.collect.AbstractCollect;
 import org.apache.hertzbeat.collector.collect.common.cache.AbstractConnection;
 import org.apache.hertzbeat.collector.collect.common.cache.CacheIdentifier;
@@ -54,13 +53,15 @@ import org.apache.hertzbeat.common.entity.job.Metrics;
 import org.apache.hertzbeat.common.entity.job.protocol.JmxProtocol;
 import org.apache.hertzbeat.common.entity.message.CollectRep;
 import org.apache.hertzbeat.common.util.CommonUtil;
+import org.apache.hertzbeat.common.util.LogUtil;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
 import org.springframework.util.Assert;
 import org.springframework.util.StringUtils;

 /**
 * jmx protocol acquisition implementation
 */
-@Slf4j
 public class JmxCollectImpl extends AbstractCollect {

    private static final String JMX_URL_PREFIX = "service:jmx:rmi:///jndi/rmi://";
@@ -75,6 +76,8 @@ public class JmxCollectImpl extends AbstractCollect {

    private final ClassLoader jmxClassLoader;

+    private static final Logger logger = LoggerFactory.getLogger(JmxCollectImpl.class);
+
    public JmxCollectImpl() {
        jmxClassLoader = new JmxClassLoader(ClassLoader.getSystemClassLoader());
    }
@@ -195,12 +198,12 @@ public class JmxCollectImpl extends AbstractCollect {
            }
        } catch (IOException exception) {
            String errorMsg = CommonUtil.getMessageFromThrowable(exception);
-            log.error("JMX IOException :{}", errorMsg);
+            LogUtil.error(logger, "JMX IOException: {0}", errorMsg);
            builder.setCode(CollectRep.Code.UN_CONNECTABLE);
            builder.setMsg(errorMsg);
        } catch (Exception e) {
            String errorMsg = CommonUtil.getMessageFromThrowable(e);
-            log.error("JMX Error :{}", errorMsg);
+            LogUtil.error(logger, "JMX Error: {0}", errorMsg);
            builder.setCode(CollectRep.Code.FAIL);
            builder.setMsg(errorMsg);
        } finally {
@@ -221,7 +224,7 @@ public class JmxCollectImpl extends AbstractCollect {
        for (Attribute attribute : attributeList.asList()) {
            Object value = attribute.getValue();
            if (value == null) {
-                log.info("attribute {} value is null.", attribute.getName());
+                LogUtil.info(logger, "attribute {0} value is null.", attribute.getName());
                continue;
            }
            if (value instanceof Number || value instanceof String || value instanceof ObjectName
@@ -245,7 +248,7 @@ public class JmxCollectImpl extends AbstractCollect {
                }
                attributeValueMap.put(attribute.getName(), builder.toString());
            } else {
-                log.warn("attribute value type {} not support.", value.getClass().getName());
+                LogUtil.warn(logger, "attribute value type {0} not support.", value.getClass().getName());
            }
        }
        return attributeValueMap;
@@ -319,7 +322,7 @@ public class JmxCollectImpl extends AbstractCollect {
            connectionCommonCache.addCache(identifier, new JmxConnect(conn));
            return conn;
        } catch (Exception e) {
-            log.error("Failed to connect to JMX server: {}", e.getMessage());
+            LogUtil.error(logger, "Failed to connect to JMX connection: {0}", e.getMessage());
            throw new IOException("Failed to connect to JMX server: " + e.getMessage(), e);
        }
    }
@@ -87,6 +87,11 @@ public interface CommonConstants {
     */
    String LABEL_INSTANCE = "instance";

+    /**
+     * label key: defineid
+     */
+    String LABEL_DEFINE_ID = "defineid";
+
    /**
     * label key: alert name
     */
@@ -0,0 +1,28 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hertzbeat.common.support.exception;
+
+/**
+ * Alert expression exception
+ */
+public class AlertExpressionException extends RuntimeException {
+
+    public AlertExpressionException(String message) {
+        super(message);
+    }
+}
@@ -17,6 +17,8 @@

 package org.apache.hertzbeat.common.util;

+import com.fasterxml.jackson.annotation.JsonAutoDetect;
+import com.fasterxml.jackson.annotation.PropertyAccessor;
 import com.fasterxml.jackson.core.JsonProcessingException;
 import com.fasterxml.jackson.core.type.TypeReference;
 import com.fasterxml.jackson.databind.DeserializationFeature;
@@ -44,6 +46,7 @@ public final class JsonUtil {
        OBJECT_MAPPER
                .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)
                .configure(SerializationFeature.FAIL_ON_EMPTY_BEANS, false)
+                .setVisibility(PropertyAccessor.FIELD, JsonAutoDetect.Visibility.ANY)
                .registerModule(new JavaTimeModule());
    }

@@ -0,0 +1,167 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hertzbeat.common.util;
+
+import org.apache.commons.lang3.ArrayUtils;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.commons.lang3.builder.ToStringBuilder;
+import org.apache.commons.lang3.builder.ToStringStyle;
+import org.slf4j.Logger;
+
+import java.text.MessageFormat;
+
+/**
+ * Log utility class that provides formatted logging methods with location information.
+ * This class enhances standard SLF4J logging by automatically adding caller location details.
+ */
+public class LogUtil {
+
+    private static final String TEMPLATE_REGEX = "\\{\\d}";
+
+    /**
+     * Print debug level formatted log
+     * Example: LogUtil.debug(logger, "hello,{0},here has a {1} exception", "other information");
+     */
+    @SuppressWarnings("unused")
+    public static void debug(Logger logger, String msg, Object... params) {
+        if (logger.isDebugEnabled()) {
+
+            if (ArrayUtils.isEmpty(params)) {
+                logger.debug(LogUtil.buildLocationInfo() + msg);
+            } else {
+                logger.debug(LogUtil.buildLocationInfo() + format(msg, params));
+            }
+        }
+    }
+
+
+    /**
+     * Print info level formatted log
+     * Example: LogUtil.info(logger, "hello,{0},{1} exception", "dear", "database operation");
+     */
+    public static void info(Logger logger, String msg, Object... params) {
+        if (logger.isInfoEnabled()) {
+            if (ArrayUtils.isEmpty(params)) {
+                logger.info(LogUtil.buildLocationInfo() + msg);
+            } else {
+                logger.info(LogUtil.buildLocationInfo() + format(msg, params));
+            }
+        }
+    }
+
+    /**
+     * Print warn level formatted log
+     */
+    public static void warn(Logger logger, String msg, Object... params) {
+        if (logger.isWarnEnabled()) {
+            if (ArrayUtils.isEmpty(params)) {
+                logger.warn(LogUtil.buildLocationInfo() + msg);
+            } else {
+                logger.warn(LogUtil.buildLocationInfo() + format(msg, params));
+            }
+        }
+    }
+
+    /**
+     * Print error level formatted log, use {0},{1},.. for parameter replacement
+     * Example: LogUtil.error(logger, "hello,{0}, a {1} exception occurred here", "dear", "database operation");
+     */
+    public static void error(Logger logger, String msg, Object... params) {
+        if (logger.isErrorEnabled()) {
+            if (ArrayUtils.isEmpty(params)) {
+                logger.error(LogUtil.buildLocationInfo() + msg);
+            } else {
+                logger.error(LogUtil.buildLocationInfo() + format(msg, params));
+            }
+        }
+
+    }
+
+
+    /**
+     * Print warn level formatted log with exception, use {0},{1},.. for parameter replacement
+     * Example: LogUtil.warn(logger, e, "hello,{0}, a {1} exception occurred here", "dear", "database operation");
+     */
+    public static void warn(Logger logger, Throwable e, String msg, Object... params) {
+        if (logger.isWarnEnabled()) {
+            if (ArrayUtils.isEmpty(params)) {
+                logger.warn(LogUtil.buildLocationInfo() + msg, e);
+            } else {
+                logger.warn(LogUtil.buildLocationInfo() + format(msg, params), e);
+            }
+        }
+    }
+
+
+    /**
+     * Print error level formatted log with exception, use {0},{1},.. for parameter replacement
+     * Example: LogUtil.error(logger, e, "hello,{0}, a {1} exception occurred here", "dear", "database operation");
+     */
+    public static void error(Logger logger, Throwable e, String msg, Object... params) {
+        if (logger.isErrorEnabled()) {
+            if (ArrayUtils.isEmpty(params)) {
+                logger.error(LogUtil.buildLocationInfo() + msg, e);
+            } else {
+                logger.error(LogUtil.buildLocationInfo() + format(msg, params), e);
+            }
+        }
+
+    }
+
+
+    /**
+     * Get the class name, method and line number that calls LogUtil
+     *
+     * @return location information string
+     */
+    private static String buildLocationInfo() {
+        StringBuilder header = new StringBuilder();
+        // LOG4J2-1029 new Throwable().getStackTrace is faster than Thread.currentThread().getStackTrace().
+        final StackTraceElement[] stackTraceElements = new Throwable().getStackTrace();
+
+        for (int i = 0; i < stackTraceElements.length - 1; i++) {
+            StackTraceElement currentStackTrace = stackTraceElements[i];
+            StackTraceElement nextStackTrace = stackTraceElements[i + 1];
+
+            // If current stack trace is in LogUtil
+            // and next stack trace is not in LogUtil
+            // then the next node is the caller of LogUtil
+            if (LogUtil.class.getName().equals(currentStackTrace.getClassName())
+                    && !LogUtil.class.getName().equals(nextStackTrace.getClassName())) {
+                String stackTrace = nextStackTrace.toString();
+                header.append(" ").append(StringUtils.removeStart(stackTrace, nextStackTrace.getClassName() + "."));
+                break;
+            }
+        }
+        return header.append(":").toString();
+    }
+
+    private static String format(String msg, Object... params) {
+        if (StringUtils.isEmpty(msg)) {
+            return StringUtils.EMPTY;
+        }
+        if (params != null && params.length > 0) {
+            msg = MessageFormat.format(msg, params);
+        }
+        return msg.replaceAll(TEMPLATE_REGEX, StringUtils.EMPTY);
+    }
+
+    private static String toString(Object object) {
+        return ToStringBuilder.reflectionToString(object, ToStringStyle.SHORT_PREFIX_STYLE);
+    }
+}
@@ -0,0 +1,117 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hertzbeat.common.util;
+
+import org.junit.jupiter.api.AfterEach;
+import org.junit.jupiter.api.BeforeEach;
+import org.junit.jupiter.api.Test;
+import org.mockito.ArgumentCaptor;
+import org.mockito.Mock;
+import org.mockito.MockitoAnnotations;
+import org.slf4j.Logger;
+import java.lang.reflect.Method;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+import static org.mockito.Mockito.anyString;
+import static org.mockito.Mockito.contains;
+import static org.mockito.Mockito.eq;
+import static org.mockito.Mockito.never;
+import static org.mockito.Mockito.verify;
+import static org.mockito.Mockito.when;
+
+class LogUtilTest {
+
+    @Mock
+    private Logger mockLogger;
+    
+    private AutoCloseable mocks;
+
+    @BeforeEach
+    void setUp() {
+        mocks = MockitoAnnotations.openMocks(this);
+    }
+    
+    @AfterEach
+    void tearDown() throws Exception {
+        if (mocks != null) {
+            mocks.close();
+        }
+    }
+
+    @Test
+    void testFormat_noParams_returnsOriginalMessage() throws Exception {
+        String original = "hello world";
+        Method formatMethod = LogUtil.class.getDeclaredMethod("format", String.class, Object[].class);
+        formatMethod.setAccessible(true);
+        String formatted = (String) formatMethod.invoke(null, original, new Object[0]);
+        assertEquals(original, formatted);
+    }
+
+    @Test
+    void testFormat_withParams_replacesPlaceholders() throws Exception {
+        String template = "hello,{0}, world {1}!";
+        Method formatMethod = LogUtil.class.getDeclaredMethod("format", String.class, Object[].class);
+        formatMethod.setAccessible(true);
+        Object[] params = {"Alice", 123};
+        String result = (String) formatMethod.invoke(null, template, params);
+        assertTrue(result.contains("hello,Alice"));
+        assertTrue(result.contains("world 123!"));
+    }
+
+    @Test
+    void testDebug_noParams_logsRawMessage() {
+        when(mockLogger.isDebugEnabled()).thenReturn(true);
+        String msg = "test-debug";
+        LogUtil.debug(mockLogger, msg);
+        verify(mockLogger).debug(contains(msg));
+    }
+
+    @Test
+    void testDebug_withParams_logsFormattedMessage() {
+        when(mockLogger.isDebugEnabled()).thenReturn(true);
+        LogUtil.debug(mockLogger, "user={0}", "Bob");
+        verify(mockLogger).debug(contains("user=Bob"));
+    }
+
+    @Test
+    void testInfo_levelOff_doesNotLog() {
+        when(mockLogger.isInfoEnabled()).thenReturn(false);
+        LogUtil.info(mockLogger, "should-not-log");
+        verify(mockLogger, never()).info(anyString());
+    }
+
+    @Test
+    void testWarn_withException_logsMessageAndException() {
+        when(mockLogger.isWarnEnabled()).thenReturn(true);
+        RuntimeException ex = new RuntimeException("warn-ex");
+        LogUtil.warn(mockLogger, ex, "warning {0}", "occurred");
+        ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class);
+        verify(mockLogger).warn(captor.capture(), eq(ex));
+        assertTrue(captor.getValue().contains("warning occurred"));
+    }
+
+    @Test
+    void testError_withExceptionAndParams_logsError() {
+        when(mockLogger.isErrorEnabled()).thenReturn(true);
+        RuntimeException ex = new RuntimeException("err");
+        LogUtil.error(mockLogger, ex, "fail code {0}", 500);
+        ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class);
+        verify(mockLogger).error(captor.capture(), eq(ex));
+        assertTrue(captor.getValue().contains("fail code 500"));
+    }
+}
@@ -31,7 +31,6 @@
        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-        <mysql.version>8.0.30</mysql.version>
        <postgresql.version>42.5.5</postgresql.version>
    </properties>

@@ -82,9 +81,8 @@

        <!-- JDBC Drivers -->
        <dependency>
-            <groupId>mysql</groupId>
-            <artifactId>mysql-connector-java</artifactId>
-            <version>${mysql.version}</version>
+            <groupId>com.mysql</groupId>
+            <artifactId>mysql-connector-j</artifactId>
            <scope>test</scope>
            <optional>true</optional>
        </dependency>
@@ -79,7 +79,7 @@ public class KafkaCollectE2eTest {
                .withNetwork(network)
                .withNetworkAliases(ZOOKEEPER_NAME)
                .waitingFor(Wait.forListeningPort())
-                .withStartupTimeout(Duration.ofSeconds(30));
+                .withStartupTimeout(Duration.ofSeconds(120));
        zookeeperContainer.setPortBindings(Collections.singletonList(ZOOKEEPER_PORT + ":" + ZOOKEEPER_PORT));

        Startables.deepStart(Stream.of(zookeeperContainer)).join();
@@ -90,7 +90,8 @@ public class KafkaCollectE2eTest {
                .withNetworkAliases(KAFKA_NAME)
                .withLogConsumer(
                        new Slf4jLogConsumer(
-                                DockerLoggerFactory.getLogger(KAFKA_IMAGE_NAME)));
+                                DockerLoggerFactory.getLogger(KAFKA_IMAGE_NAME)))
+                .withStartupTimeout(Duration.ofSeconds(120));
        Startables.deepStart(Stream.of(kafkaContainer)).join();
    }

@@ -113,11 +114,12 @@ public class KafkaCollectE2eTest {
        // Create Topic
        Properties properties = new Properties();
        properties.put("bootstrap.servers", bootstrapServers);
-        AdminClient adminClient = KafkaAdminClient.create(properties);
        int numPartitions = 1;
        short replicationFactor = 1;
-        NewTopic newTopic = new NewTopic(topicName, numPartitions, replicationFactor);
-        adminClient.createTopics(Collections.singletonList(newTopic)).all().get(60, TimeUnit.SECONDS);
+        try (AdminClient adminClient = KafkaAdminClient.create(properties)) {
+            NewTopic newTopic = new NewTopic(topicName, numPartitions, replicationFactor);
+            adminClient.createTopics(Collections.singletonList(newTopic)).all().get(60, TimeUnit.SECONDS);
+        }

        // Verify the information of topic list monitoring
        builder = CollectRep.MetricsData.newBuilder();
@@ -121,6 +121,14 @@ public class MonitorsController {
        monitorService.export(ids, type, res);
    }

+    @GetMapping("/export/all")
+    @Operation(summary = "export all monitor config", description = "export all monitor config")
+    public void exportAll(
+            @Parameter(description = "Export Type:JSON,EXCEL,YAML") @RequestParam(defaultValue = "JSON") String type,
+            HttpServletResponse res) throws Exception {
+        monitorService.exportAll(type, res);
+    }
+
    @PostMapping("/import")
    @Operation(summary = "import monitor config", description = "import monitor config")
    public ResponseEntity<Message<Void>> export(MultipartFile file) throws Exception {
@@ -173,6 +173,15 @@ public interface MonitorService {
     */
    void export(List<Long> ids, String type, HttpServletResponse res) throws Exception;

+    /**
+     * Export All Monitoring Configuration
+     *
+     * @param type file type
+     * @param res  response
+     * @throws Exception This exception will be thrown if the export fails
+     */
+    void exportAll(String type, HttpServletResponse res) throws Exception;
+
    /**
     * Import Monitoring Configuration
     *
@@ -235,6 +235,18 @@ public class MonitorServiceImpl implements MonitorService {
        imExportService.exportConfig(res.getOutputStream(), ids);
    }

+    @Override
+    public void exportAll(String type, HttpServletResponse res) throws Exception {
+        // Get all monitor IDs from the database
+        List<Long> allMonitorIds = monitorDao.findAll()
+                .stream()
+                .map(Monitor::getId)
+                .collect(Collectors.toList());
+        
+        // Use the existing export method to export all monitors
+        export(allMonitorIds, type, res);
+    }
+
    @Override
    public void importConfig(MultipartFile file) throws Exception {
        var fileName = FileUtil.getFileName(file);
@@ -26,8 +26,8 @@ name:
 help:
  zh-CN: HertzBeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMX 协议</a> 对 Apache ActiveMQ 消息中间件的运行状态，节点，Topic等相关指标（broker、topic、memory pool、class loading、thread）进行监测。<br><span class='help_module_span'>⚠️注意：您需要在 ActiveMQ 开启 JMX 服务。<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/activemq'>点击查看开启步骤</a>。</span>
  en-US: "HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMX protocol</a> to monitor the running status, nodes, topics, and other metrics of Apache ActiveMQ message-oriented middleware. <br><span class='help_module_span'>⚠️Note: You should enable the JMX service in ActiveMQ. <a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/activemq'>Click here to view the specific steps.</a></span>"
-  zh-TW: HertzBeat使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMX 協定</a> 對 Apache ActiveMQ 消息中介軟體的運行狀態，節點，Topic 等相關名額（broker、topic、memory pool、class loading、thread）進行監測。<br><span class='help_module_span'> ⚠️注意：您需要在 ActiveMQ 開啟 JMX 服務。<a class='help_module_content' href=' https://hertzbeat.apache.org/zh-cn/docs/help/activemq'>點擊查看開啟步驟</a>。</span>
-  ja-JP: HertzBeatは <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMXプロトコルを介して</a> Apache ActiveMQメッセージングシステムのランタイムステータス、ノード、トピック、その他の関連メトリックを監視します。<br><span class='help_module_span'> ⚠️注意：ActiveMQ で JMX サービスを有効にする必要があります。<a class='help_module_content' href=' https://hertzbeat.apache.org/zh-cn/docs/help/activemq'>クリックしてガイドを見ます</a>。</span>
+  zh-TW: HertzBeat使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMX 協定</a> 對 Apache ActiveMQ 消息中介軟體的運行狀態，節點，Topic 等相關名額（broker、topic、memory pool、class loading、thread）進行監測。<br><span class='help_module_span'> ⚠️注意：您需要在 ActiveMQ 開啟 JMX 服務。<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/activemq'>點擊查看開啟步驟</a>。</span>
+  ja-JP: HertzBeatは <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMXプロトコルを介して</a> Apache ActiveMQメッセージングシステムのランタイムステータス、ノード、トピック、その他の関連メトリクスを監視します。<br><span class='help_module_span'> ⚠️注意：ActiveMQ で JMX サービスを有効にする必要があります。<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/activemq'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/activemq
  en-US: https://hertzbeat.apache.org/docs/help/activemq
@@ -196,7 +196,7 @@ metrics:
        i18n:
          zh-CN: 持久化
          en-US: Persistence
-          ja-JP: 永続性
+          ja-JP: 永続化
        type: 1
      - field: DataDirectory
        i18n:
@@ -271,19 +271,19 @@ metrics:
        i18n:
          zh-CN: 平均消息大小
          en-US: Average Message Size
-          ja-JP: 平均メッセージサイズ
+          ja-JP: メッセージの平均サイズ
        type: 0
      - field: MaxMessageSize
        i18n:
          zh-CN: 最大消息大小
          en-US: Max Message Size
-          ja-JP: 最大メッセージサイズ
+          ja-JP: メッセージの最大サイズ
        type: 0
      - field: MinMessageSize
        i18n:
          zh-CN: 最小消息大小
          en-US: Min Message Size
-          ja-JP: 最小メッセージサイズ
+          ja-JP: メッセージの最小サイズ
        type: 0
    protocol: jmx
    jmx:
@@ -372,7 +372,7 @@ metrics:
        i18n:
          zh-CN: 存储消息大小
          en-US: Store Message Size
-          ja-JP: ストレージメッセージサイズ
+          ja-JP: ストレージメッセージのサイズ
      - field: AverageEnqueueTime
        type: 0
        unit: ms
@@ -407,21 +407,21 @@ metrics:
        i18n:
          zh-CN: 平均消息大小
          en-US: Average Message Size
-          ja-JP: 平均メッセージサイズ
+          ja-JP: メッセージの平均サイズ
      - field: MaxMessageSize
        type: 0
        unit: B
        i18n:
          zh-CN: 最大消息大小
          en-US: Max Message Size
-          ja-JP: 最大メッセージサイズ
+          ja-JP: メッセージの最大サイズ
      - field: MinMessageSize
        type: 0
        unit: B
        i18n:
          zh-CN: 最小消息大小
          en-US: Min Message Size
-          ja-JP: 最小メッセージサイズ
+          ja-JP: メッセージの最小サイズ
    units:
      - MemoryLimit=B->MB
    protocol: jmx
@@ -446,14 +446,14 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: Name
-          ja-JP: 指標名
+          ja-JP: メトリクス名
      - field: committed
        type: 0
        unit: MB
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
-          ja-JP: コミットメモリ
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        unit: MB
@@ -474,7 +474,7 @@ metrics:
        i18n:
          zh-CN: 已使用内存
          en-US: Used
-          ja-JP: 使用済みのメモリ
+          ja-JP: 使用したメモリ
    units:
      - committed=B->MB
      - init=B->MB
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 Apache Airflow 通用性能指标（airflow health、airflow version）进行采集监控。<br>您可以点击“<i>新建 Apache Airflow </i>”并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat monitors Apache Airflow through general performance metrics such as airflow health and airflow version. You could click the "<i>New Apache Airflow</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat對Apache Airflow通用性能指標（airflow health、airflow version）進行採集監控。<br>您可以點擊“<i>新建 Apache Airflow</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeatは、Apache Airflowの一般的なパフォーマンスのメトリックを監視します。 <br><i>新規Apache Airflow</i>をクリックして設定しましょう。
+  ja-JP: Hertzbeatは、Apache Airflowの一般的なパフォーマンスのメトリクスを監視します。 <br><i>新規Apache Airflow</i>をクリックして設定しましょう。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/airflow/
  en-US: https://hertzbeat.apache.org/docs/help/airflow/
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 AlmaLinux 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 AlmaLinux</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors AlmaLinux operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New AlmaLinux</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 AlmaLinux 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建AlmaLinux</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> AlmaLinuxシステムの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 AlmaLinux</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> AlmaLinuxシステムの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 AlmaLinux</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/almalinux
  en-US: https://hertzbeat.apache.org/docs/help/almalinux
@@ -80,7 +80,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -92,7 +92,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -246,7 +246,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
      - field: uptime
        type: 1
        i18n:
@@ -544,14 +544,14 @@ metrics:
        i18n:
          zh-CN: 入站数据流量
          en-US: Receive Bytes
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: transmit_bytes
        type: 0
        unit: Mb
        i18n:
          zh-CN: 出站数据流量
          en-US: Transmit Bytes
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
    units:
      - receive_bytes=B->MB
      - transmit_bytes=B->MB
@@ -679,7 +679,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -738,7 +738,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 将调用 HTTP API 接口，查看接口是否可用，并以 ms 为指标单位对其响应时间等指标进行监测。您可以先点击“新增 HTTP API”按钮并进行配置，或在“更多操作”中导入已有配置。
  en-US: The platform will invoke an HTTP API endpoint to verify its accessibility and monitor various metrics, including response time, measured in milliseconds (ms). <br>To set up this functionality, you could click the "Add HTTP API" button and proceed with the configuration or import an existing setup through the "More Actions" menu.
  zh-TW: Hertzbeat將調用HTTP API介面，查看介面是否可用，並以ms為名額組織對其回應時間等名額進行監測。 您可以先點擊“新增HTTP API”按鈕並進行配寘，或在“更多操作”中導入已有配寘。
-  ja-JP: Hertzbeatは、HTTP APIを呼び出して利用可能かどうかを確認し、応答時間(ms)などのメトリックを監視します。「新規HTTP API」をクリックして設定しましょう。
+  ja-JP: Hertzbeatは、HTTP APIを呼び出して利用可能かどうかを確認し、応答時間(ms)などのメトリクスを監視します。「新規HTTP API」をクリックして設定しましょう。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/api
  en-US: https://hertzbeat.apache.org/docs/help/api
@@ -173,7 +173,6 @@ params:
      ja-JP: ボディ
    # type-param field type(most mapping the html input type)
    type: textarea
-    # 参数输入框提示信息
    # param field input placeholder
    placeholder: 'Available When POST PUT'
    # dependent parameter values list
@@ -27,7 +27,7 @@ help:
  zh-CN: 监控 HTTP API 接口，对 API 返回的业务自定义状态码(非 Http 状态码)进行监控。此需通过配置 JsonPath 来解析您 API 的业务状态码路径。<br>您可以点击 “<i>新建 API Code</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Monitor HTTP API to monitor business-defined status codes (non-HTTP status codes) returned by API. To do this, you need to configure JsonPath to resolve the business status code path of your API. <br>You could click the "<i>New API Codes</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: 監控 HTTP API 接口，對 API 返回的業務自定義狀態碼(非 Http 狀態碼)進行監控。此需通過配置 JsonPath 來解析您 API 的業務狀態碼路徑。<br>您可以點擊“<i>新建API Code</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeatは、HTTP APIを呼び出して利用可能かどうかを確認し、ビジネスステータスコード（HTTPステータスコードではない）のメトリックを監視します。これには、API のビジネスステータスコードのパスを解析するように JsonPath を構成する必要があります。「新規API Code」をクリックして設定しましょう。
+  ja-JP: Hertzbeatは、HTTP APIを呼び出して利用可能かどうかを確認し、ビジネスステータスコード（HTTPステータスコードではない）のメトリクスを監視します。これには、API のビジネスステータスコードのパスを解析するように JsonPath を構成する必要があります。「新規API Code」をクリックして設定しましょう。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/api_code
  en-US: https://hertzbeat.apache.org/docs/help/api_code
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 Centos 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 Centos</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors Centos operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New Centos</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 Centos 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 Centos</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Centosシステムの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 Centos Linux</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Centosシステムの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Centos Linux</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/centos/
  en-US: https://hertzbeat.apache.org/docs/help/centos/
@@ -80,7 +80,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -92,7 +92,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -246,7 +246,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
      - field: uptime
        type: 1
        i18n:
@@ -544,14 +544,14 @@ metrics:
        i18n:
          zh-CN: 入站数据流量
          en-US: Receive Bytes
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: transmit_bytes
        type: 0
        unit: Mb
        i18n:
          zh-CN: 出站数据流量
          en-US: Transmit Bytes
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
    units:
      - receive_bytes=B->MB
      - transmit_bytes=B->MB
@@ -679,7 +679,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -738,7 +738,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 协议</a> 对 思科交换机 的通用指标(可用性，系统信息，端口流量等)进行采集监控。<br>您可以点击 “<i>新建 思科通用交换机</i>” 并进行配置SNMP相关参数添加，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP Protocol</a> to monitoring Cisco Switch general performance metrics. <br>You can click the "<i>New Cisco Switch</i>" button and config snmp params to add monitor or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 協議</a> 對 思科交換機 的通用指標(可用性，系統信息，端口流量等)進行采集監控。<br>您可以點擊 “<i>新建 思科通用交換機</i>” 並進行配置SNMP相關參數添加，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP プロトコルを介して</a> シスコ・スイッチングハブの一般的なメトリック監視します。<br>「<i>新規 シスコ・スイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP プロトコルを介して</a> シスコ・スイッチングハブの一般的なメトリクスを監視します。<br>「<i>新規 シスコ・スイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/cisco_switch
  en-US: https://hertzbeat.apache.org/docs/help/cisco_switch
@@ -361,13 +361,13 @@ metrics:
        i18n:
          zh-CN: 入流量
          en-US: In Octets
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: in_discards
        type: 0
        i18n:
          zh-CN: 入丢包数
          en-US: In Discards
-          ja-JP: 受信パケットロス数
+          ja-JP: 受信されたパケットのロス数
      - field: in_errors
        type: 0
        i18n:
@@ -380,19 +380,19 @@ metrics:
        i18n:
          zh-CN: 出流量
          en-US: Out Octets
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
      - field: out_discards
        type: 0
        i18n:
          zh-CN: 出丢包数
          en-US: Out Discards
-          ja-JP: 送信パケットロス数
+          ja-JP: 転送されたパケットロス数
      - field: out_errors
        type: 0
        i18n:
          zh-CN: 出错包数
          en-US: Out Errors
-          ja-JP: 送信異常パケット数
+          ja-JP: 転送された異常パケット数
      - field: admin_status
        type: 1
        i18n:
@@ -404,7 +404,7 @@ metrics:
        i18n:
          zh-CN: 当前状态
          en-US: Current Status
-          ja-JP: ステータス
+          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:
      - ifIndex
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 ClickHouse 数据库监控通用指标进行测量监控。<br>您可以点击 “<i>新建 ClickHouse 数据库</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors the status codes which returned by the API. You could click the "<i>New ClickHouse Database</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 ClickHouse 資料庫監控通用名額進行量測監控。<br>您可以點擊 “<i>新建ClickHouse資料庫</i>” 並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は ClickHouse データベースの一般的なメトリック監視します。<br>「<i>新規 ClickHouse データベース</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は ClickHouse データベースの一般的なメトリクスを監視します。<br>「<i>新規 ClickHouse データベース</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/clickhouse
  en-US: https://hertzbeat.apache.org/docs/help/clickhouse
@@ -161,19 +161,19 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: metric
-          ja-JP: メトリック名
+          ja-JP: メトリクス名
      - field: value
        type: 0
        i18n:
          zh-CN: 指标值
          en-US: value
-          ja-JP: メトリック値
+          ja-JP: メトリクス値
      - field: description
        type: 1
        i18n:
          zh-CN: 说明
          en-US: description
-          ja-JP: メトリック説明
+          ja-JP: メトリクス説明
    protocol: jdbc
    jdbc:
      host: ^_^host^_^
@@ -236,19 +236,19 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: metric
-          ja-JP: メトリック名
+          ja-JP: メトリクス名
      - field: value
        type: 0
        i18n:
          zh-CN: 指标值
          en-US: value
-          ja-JP: メトリック値
+          ja-JP: メトリクス値
      - field: description
        type: 1
        i18n:
          zh-CN: 说明
          en-US: description
-          ja-JP: メトリック説明
+          ja-JP: メトリクス説明
    protocol: jdbc
    jdbc:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 Fedora CoreOS 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 Fedora CoreOS</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors Fedora CoreOS operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New Fedora CoreOS</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 Fedora CoreOS 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 Fedora CoreOS</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH プロトコルを介して</a> Fedora CoreOSの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 Fedora CoreOS</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH プロトコルを介して</a> Fedora CoreOSの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Fedora CoreOS</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/coreos
  en-US: https://hertzbeat.apache.org/docs/help/coreos
@@ -80,7 +80,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -92,7 +92,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -246,7 +246,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
      - field: uptime
        type: 1
        i18n:
@@ -544,14 +544,14 @@ metrics:
        i18n:
          zh-CN: 入站数据流量
          en-US: Receive Bytes
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: transmit_bytes
        type: 0
        unit: Mb
        i18n:
          zh-CN: 出站数据流量
          en-US: Transmit Bytes
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
    units:
      - receive_bytes=B->MB
      - transmit_bytes=B->MB
@@ -679,7 +679,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -738,7 +738,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -80,7 +80,7 @@ params:

 # collect metrics config list
 metrics:
-  - name: network_info # 指标集合名称
+  - name: network_info
    i18n:
      zh-CN: 网络信息
      en-US: Network Info
@@ -20,18 +20,18 @@ app: darwin
 # The monitoring i18n name
 name:
  zh-CN: Darwin操作系统
-  en-US: Darwin Linux
-  ja-JP: Darwin Linux
+  en-US: OS Darwin
+  ja-JP: Darwinオーエス
  zh-TW: Darwin操作系統
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 使用 <a class='help_module_content' href='https://HertzBeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 Darwin 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 Darwin</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://HertzBeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors Darwin operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New Darwin</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
-#  zh-TW: HertzBeat 使用 <a class='help_module_content' href='https://HertzBeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 Darwin 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 Darwin</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-#  ja-JP: HertzBeat は <a class='help_module_content' href='https://HertzBeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Darwinシステムの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 Darwin Linux</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  zh-TW: HertzBeat 使用 <a class='help_module_content' href='https://HertzBeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 Darwin 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 Darwin</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
+  ja-JP: HertzBeat は <a class='help_module_content' href='https://HertzBeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Darwinシステムの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Darwin Linux</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
-  zh-CN: https://HertzBeat.apache.org/zh-cn/docs/help/Darwin/
-  en-US: https://HertzBeat.apache.org/docs/help/Darwin/
+  zh-CN: https://HertzBeat.apache.org/zh-cn/docs/help/darwin/
+  en-US: https://HertzBeat.apache.org/docs/help/darwin/
 # Input params define for monitoring(render web ui by the definition)
 params:
  # field-param field key
@@ -77,7 +77,6 @@ params:
    # required-true or false
    required: false
    # default value
-    # 默认值
    defaultValue: 6000
  # field-param field key
  - field: reuseConnection
@@ -85,7 +84,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
      zh-TW: 復用連接
    # type-param field type(most mapping the html input type)
    type: boolean
@@ -98,7 +97,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
      zh-TW: 使用代理
    # type-param field type(most mapping the html input type)
    type: boolean
@@ -264,7 +263,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
          zh-TW: 操作系統版本
      - field: uptime
        type: 1
@@ -526,74 +525,75 @@ metrics:
        }'
      parseType: multiRow

-#  - name: disk
-#    i18n:
-#      zh-CN: 磁盘信息
-#      zh-TW: 磁盤信息
-#      en-US: Disk Info
-#      ja-JP: ディスク情報
-#    priority: 3
-#    fields:
-#      - field: disk_num
-#        type: 1
-#        i18n:
-#          zh-CN: 磁盘总数
-#          zh-TW: 磁盤總數
-#          en-US: Disk Num
-#          ja-JP: ディスク番号
-#      - field: partition_num
-#        type: 1
-#        i18n:
-#          zh-CN: 分区总数
-#          zh-TW: 分區總數
-#          en-US: Partition Num
-#          ja-JP: パーティション
-#      - field: block_write
-#        type: 0
-#        i18n:
-#          zh-CN: 写磁盘块数
-#          zh-TW: 寫磁盤塊數
-#          en-US: Block Write
-#          ja-JP: 書き込みディスクブロック数
-#      - field: block_read
-#        type: 0
-#        i18n:
-#          zh-CN: 读磁盘块数
-#          zh-TW: 讀磁盤塊數
-#          en-US: Block Read
-#          ja-JP: 読み取りブロック数
-#      - field: write_rate
-#        type: 0
-#        unit: iops
-#        i18n:
-#          zh-CN: 磁盘写速率
-#          zh-TW: 磁盤寫速率
-#          en-US: Write Rate
-#          ja-JP: ディスク書き込み速度
-#    protocol: ssh
-#    ssh:
-#      host: ^_^host^_^
-#      port: ^_^port^_^
-#      username: ^_^username^_^
-#      password: ^_^password^_^
-#      privateKey: ^_^privateKey^_^
-#      privateKeyPassphrase: ^_^privateKeyPassphrase^_^
-#      timeout: ^_^timeout^_^
-#      reuseConnection: ^_^reuseConnection^_^
-#      # whether to use proxy server for ssh connection
-#      useProxy: ^_^useProxy^_^
-#      # ssh proxy host: ipv4 domain
-#      proxyHost: ^_^proxyHost^_^
-#      # ssh proxy port
-#      proxyPort: ^_^proxyPort^_^
-#      # ssh proxy username
-#      proxyUsername: ^_^proxyUsername^_^
-#      # ssh proxy password
-#      proxyPassword: ^_^proxyPassword^_^
-#      # ssh proxy private key
-#      proxyPrivateKey: ^_^proxyPrivateKey^_^
-#      script: cat /proc/net/dev | tail -n +3 | awk 'BEGIN{ print "interface_name receive_bytes transmit_bytes"} {gsub(":", "", $1); print $1,$2,$10}'
-#      parseType: oneRow
+  - name: disk
+    i18n:
+      zh-CN: 磁盘信息
+      zh-TW: 磁盤信息
+      en-US: Disk Info
+      ja-JP: ディスク情報
+    priority: 3
+    fields:
+      - field: disk_num
+        type: 1
+        i18n:
+          zh-CN: 磁盘总数
+          zh-TW: 磁盤總數
+          en-US: Disk Num
+          ja-JP: ディスク番号
+      - field: partition_num
+        type: 1
+        i18n:
+          zh-CN: 分区总数
+          zh-TW: 分區總數
+          en-US: Partition Num
+          ja-JP: パーティション
+    #      - field: block_write
+    #        type: 0
+    #        i18n:
+    #          zh-CN: 写磁盘块数
+    #          zh-TW: 寫磁盤塊數
+    #          en-US: Block Write
+    #          ja-JP: 書き込みディスクブロック数
+    #      - field: block_read
+    #        type: 0
+    #        i18n:
+    #          zh-CN: 读磁盘块数
+    #          zh-TW: 讀磁盤塊數
+    #          en-US: Block Read
+    #          ja-JP: 読み取りブロック数
+    #      - field: write_rate
+    #        type: 0
+    #        unit: iops
+    #        i18n:
+    #          zh-CN: 磁盘写速率
+    #          zh-TW: 磁盤寫速率
+    #          en-US: Write Rate
+    #          ja-JP: ディスク書き込み速度
+    protocol: ssh
+    ssh:
+      host: ^_^host^_^
+      port: ^_^port^_^
+      username: ^_^username^_^
+      password: ^_^password^_^
+      privateKey: ^_^privateKey^_^
+      privateKeyPassphrase: ^_^privateKeyPassphrase^_^
+      timeout: ^_^timeout^_^
+      reuseConnection: ^_^reuseConnection^_^
+      # whether to use proxy server for ssh connection
+      useProxy: ^_^useProxy^_^
+      # ssh proxy host: ipv4 domain
+      proxyHost: ^_^proxyHost^_^
+      # ssh proxy port
+      proxyPort: ^_^proxyPort^_^
+      # ssh proxy username
+      proxyUsername: ^_^proxyUsername^_^
+      # ssh proxy password
+      proxyPassword: ^_^proxyPassword^_^
+      # ssh proxy private key
+      proxyPrivateKey: ^_^proxyPrivateKey^_^
+      #      script: cat /proc/net/dev | tail -n +3 | awk 'BEGIN{ print "interface_name receive_bytes transmit_bytes"} {gsub(":", "", $1); print $1,$2,$10}'
+      script: diskutil list | grep '^/dev/' | wc -l; diskutil list | grep -E 'Apple_HFS|Apple_APFS|Microsoft Basic Data|Linux Filesystem' | wc -l;
+      parseType: oneRow

  - name: interface
    i18n:
@@ -618,7 +618,7 @@ metrics:
          zh-CN: 入站数据流量
          zh-TW: 入站數據流量
          en-US: Receive Bytes
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: transmit_bytes
        type: 0
        unit: Mb
@@ -626,7 +626,7 @@ metrics:
          zh-CN: 出站数据流量
          zh-TW: 出站數據流量
          en-US: Transmit Bytes
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
    units:
      - receive_bytes=B->MB
      - transmit_bytes=B->MB
@@ -765,7 +765,7 @@ metrics:
          zh-CN: 执行命令
          zh-TW: 執行指令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -829,7 +829,7 @@ metrics:
          zh-CN: 执行命令
          zh-TW: 執行指令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 Debian 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 Debian</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors Debian operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New Debian</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 Debian 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 Debian</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Centosシステムの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 Debian</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Centosシステムの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Debian</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/debian
  en-US: https://hertzbeat.apache.org/docs/help/debian
@@ -80,7 +80,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -92,7 +92,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -245,7 +245,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
      - field: uptime
        type: 1
        i18n:
@@ -543,14 +543,14 @@ metrics:
        i18n:
          zh-CN: 入站数据流量
          en-US: Receive Bytes
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: transmit_bytes
        type: 0
        unit: Mb
        i18n:
          zh-CN: 出站数据流量
          en-US: Transmit Bytes
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
    units:
      - receive_bytes=B->MB
      - transmit_bytes=B->MB
@@ -678,7 +678,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -737,7 +737,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: HertzBeat 对 DM达梦数据库 的通用性能指标(basic、status、thread)进行采集监控，支持版本为 DM8+。<br>您可以点击“<i>新建 达梦数据库</i>”并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat monitors DM database of basic performance metrics such as status and thread, the version we support is DM8+. You could click the "<i>New DM</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: HertzBeat 對 DM達夢數據庫 的通用性能指標(basic、status、thread)進行采集監控，支持版本爲 DM8+。<br>您可以點擊“<i>新建 達夢數據庫</i>”並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は DM データベースの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 DM データベース</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は DM データベースの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 DM データベース</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/dm
  en-US: https://hertzbeat.apache.org/docs/help/dm
@@ -27,7 +27,7 @@ help:
  zh-CN: HertzBeat 对 DNS 服务相关指标进行监测。
  en-US: HertzBeat monitors related indicators of the DNS service.
  zh-TW: HertzBeat對DNS服務相關名額進行監測。
-  ja-JP: HertzBeatはDNSのメトリックを監視します。
+  ja-JP: HertzBeatはDNSのメトリクスを監視します。
 # Input params define for monitoring(render web ui by the definition)
 params:
  # field-param field key
@@ -27,7 +27,7 @@ help:
  zh-CN: HertzBeat 对 Docker 容器的通用性能指标（system、containers、stats）进行采集监控。<br><span class='help_module_span'>注意⚠️：为了监控 Docker 中的容器信息，您需要打开端口，让采集请求获取到对应的信息, <a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/docker'>点击查看开启步骤</a>。</span>
  en-US: HertzBeat monitoring Docker of general performance metrics such as containers, status etc. <br><span class='help_module_span'>Note⚠️:In order to monitoring metrics of Docker, you need to enable the data export port so that the collector can collect data from here，<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/docker'>Click here to view the steps</a>.</span>
  zh-TW: HertzBeat 對 Docker 容器的通用性能指標（system、containers、stats）進行采集監控。<br><span class='help_module_span'>注意⚠️：爲了監控 Docker 中的容器信息，您需要打開端口，讓采集請求獲取到對應的信息, <a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/docker'>點擊查看開啓步驟</a>。</span>
-  ja-JP: HertzBeat は Dockerコンテナの一般的なパフォーマンスのメトリック監視します。<br><span class='help_module_span'>注意⚠️：Dockerコンテナの情報を監視するために、ポートを有効にする必要があります。<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/docker'>クリックしてガイドを見ます</a>。</span>
+  ja-JP: HertzBeat は Dockerコンテナの一般的なパフォーマンスのメトリクスを監視します。<br><span class='help_module_span'>注意⚠️：Dockerコンテナの情報を監視するために、ポートを有効にする必要があります。<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/docker'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/docker/
  en-US: https://hertzbeat.apache.org/docs/help/docker/
@@ -226,7 +226,7 @@ metrics:
        i18n:
          zh-CN: 命令行
          en-US: command
-          ja-JP: 指令
+          ja-JP: コマンド
        type: 1
      - field: state
        i18n:
@@ -274,9 +274,9 @@ metrics:

  - name: stats
    i18n:
-      zh-CN: 状态
+      zh-CN: 统计
      en-US: stats
-      ja-JP: スタッツ
+      ja-JP: 統計
    priority: 2
    fields:
      - field: name
@@ -296,7 +296,7 @@ metrics:
        i18n:
          zh-CN: 已用内存
          en-US: used memory
-          ja-JP: 使用済みのメモリ
+          ja-JP: 使用したメモリ
        type: 0
        unit: MB
      - field: memory_usage
@@ -26,7 +26,7 @@ help:
  zh-CN: Hertzbeat 对 DORIS 数据库BE的通用性能指标（load channel count、memtable flush total、process thread num、light work max threads等）进行采集监控，支持版本为DORIS2.0.0。<br>您可以点击 “<i>新建 Doris DatabaseBE</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring Doris DatabaseBE through general performance metric such as load channel count, memtable flush total, process thread num and light work max threads. The version we support is DORIS2.0.0. You could click the "<i>New Doris DatabaseBE Monitor</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 DORIS 資料庫BE的通用性能指標（load channel count、memtable flush total、process thread num、light work max threads等）進行採集監控，支持版本為DORIS2.0.0。<br>您可以點擊“<i>新建Doris DatabaseBE</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は DORIS 2.0.0のデータベースBEの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 Doris DatabaseBE</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は DORIS 2.0.0のデータベースBEの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Doris DatabaseBE</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/doris_be/
  en-US: https://hertzbeat.apache.org/docs/help/doris_be/
@@ -178,7 +178,7 @@ metrics:
    i18n:
      zh-CN: 批量发送线程池队列大小
      en-US: Send Batch Thread Pool Queue Size
-      ja-JP: バッチ送信スレッドプールのキューサイズ
+      ja-JP: バッチ転送されたスレッドプールのキューサイズ
    priority: 6
    fields:
      - field: value
@@ -26,7 +26,7 @@ help:
  zh-CN: Hertzbeat 对 Doris 数据库FE的通用指标（doris_fe connection total、doris_fe edit log clean、doris_fe image、doris_fe rps等）进行测量监控，支持版本为DORIS2.0.0。<br>您可以点击 “<i>新建 Doris DatabaseFE</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring Doris DatabaseFE through general performance metric such as doris_fe connection total, doris_fe edit log clean, doris_fe image and doris_fe rps. The version we support is DORIS2.0.0. You could click the "<i>New Doris DatabaseFE Monitor</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 Doris 資料庫FE的通用名額（doris_fe connection total、doris_fe edit log clean、doris_fe image、doris_fe rps等）進行量測監控，支持版本為DORIS2.0.0。<br>您可以點擊“<i>新建Doris DatabaseFE</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は DORIS 2.0.0のデータベースFEの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 Doris DatabaseFE</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は DORIS 2.0.0のデータベースFEの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 Doris DatabaseFE</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/doris_fe/
  en-US: https://hertzbeat.apache.org/docs/help/doris_fe/
@@ -70,7 +70,7 @@ metrics:
    i18n:
      zh-CN: 连接总数
      en-US: Connection Total
-      ja-JP: コネクション数
+      ja-JP: 接続総数
    priority: 0
    fields:
      - field: value
@@ -26,8 +26,8 @@ name:
 help:
  zh-CN: HertzBeat 对 DynamicTp actuator 暴露的线程池性能指标（thread pool）进行采集监控。<br><span class='help_module_span'>注意⚠️：您需要集成使用 DynamicTp，<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/dynamic_tp'>点击查看集成步骤</a>。
  en-US: HertzBeat monitoring DynamicTp of the thread Pool Performance Metrics which exposed by DynamicTp actuator. <br><span class='help_module_span'>Note⚠️:You should integrate and use DynamicTp, <a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/dynamic_tp'>Click here to view the specific steps.</a>"
-  zh-TW: HertzBeat 對 DynamicTp actuator暴露的執行緒池性能指標（thread pool）進行採集監控。<br><span class='help_ module_ span'>注意⚠️：您需要集成使用DynamicTp，<a class='help_ module_ content' href='https://hertzbeat.apache.org/zh-cn/docs/help/dynamic_tp'>點擊查看集成步驟</a>。
-  ja-JP: HertzBeat は DynamicTpスレッドプールの一般的なパフォーマンスのメトリック監視します。<br><span class='help_module_span'>注意⚠️：DynamicTpの使用を統合する必要があり、<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/dynamic_tp'>クリックしてガイドを見ます</a>。
+  zh-TW: HertzBeat 對 DynamicTp actuator暴露的執行緒池性能指標（thread pool）進行採集監控。<br><span class='help_module_span'>注意⚠️：您需要集成使用DynamicTp，<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/dynamic_tp'>點擊查看集成步驟</a>。
+  ja-JP: HertzBeat は DynamicTpスレッドプールの一般的なパフォーマンスのメトリクスを監視します。<br><span class='help_module_span'>注意⚠️：DynamicTpの使用を統合する必要があり、<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/dynamic_tp'>クリックしてガイドを見ます</a>。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/dynamic_tp/
  en-US: https://hertzbeat.apache.org/docs/help/dynamic_tp/
@@ -128,7 +128,7 @@ metrics:
        i18n:
          zh-CN: 公平
          en-US: fair
-          ja-JP: 目標ホスト
+          ja-JP: 公平
        type: 1
      - field: reject_handler_name
        type: 1
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 ElasticSearch 数据库监控通用指标进行测量监控。<br>您可以点击 “<i>新建 ElasticSearch</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring ElasticSearch through general performance metrics. You could click the "<i>New ElasticSearch</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 ElasticSearch 資料庫監控通用名額進行量測監控。<br>您可以點擊“<i>新建ElasticSearch</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: HertzBeat は ElasticSearch データベースの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 ElasticSearch</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: HertzBeat は ElasticSearch データベースの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 ElasticSearch</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/elasticsearch
  en-US: https://hertzbeat.apache.org/docs/help/elasticsearch
@@ -27,7 +27,7 @@ help:
  zh-CN: EMQX 是一款开源的大规模分布式 MQTT 消息服务器。Hertzbeat对EMQX MQTT消息服务器 5.0+ 版本的通用指标进行测量监控，<br>您可以点击 “<i>新建 EMQX 消息服务器</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: EMQX is an open source large-scale distributed MQTT message server. Hertzbeat measures and monitors common metrics of the EMQX message server 5.0+ version.<br>You can click "<i>New EMQX message server</i>" and configure it, or select "<i>More operations</i>", Import existing configuration.
  zh-TW: EMQX 是一款開源的大規模分散式 MQTT 訊息伺服器。 Hertzbeat對EMQX MQTT訊息伺服器 5.0+ 版本的通用指標進行測量監控，<br>您可以點擊“<i>新建 EMQX 訊息伺服器</i>” 並進行配置，或者選擇“<i>更多操作</i>” ，導入已有配置。
-  ja-JP: EMQXは、オープンソースの大規模分散MQTTメッセージサーバーです。HertzbeatはEMQX MQTTメッセージサーバー（バージョン5.0+）の一般的なフォーマンスのメトリック監視します。<br>「<i>新規 EMQX</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: EMQXは、オープンソースの大規模分散MQTTメッセージサーバーです。HertzbeatはEMQX MQTTメッセージサーバー（バージョン5.0+）の一般的なフォーマンスのメトリクスを監視します。<br>「<i>新規 EMQX</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/emqx
  en-US: https://hertzbeat.apache.org/docs/help/emqx
@@ -179,7 +179,7 @@ metrics:
    i18n:
      zh-CN: 指标
      en-US: Metrics
-      ja-JP: メトリック
+      ja-JP: メトリクス
    # metrics scheduling priority(0->127)->(high->low), metrics with the same priority will be scheduled in parallel
    # priority 0's metrics is availability metrics, it will be scheduled first, only availability metrics collect success will the scheduling continue
    priority: 1
@@ -203,31 +203,31 @@ metrics:
        i18n:
          zh-CN: 发送数据包
          en-US: Packets Sent
-          ja-JP: 送信パケット
+          ja-JP: 転送されたパケット
      - field: packets_received
        type: 0
        i18n:
          zh-CN: 接收数据包
          en-US: Packets Received
-          ja-JP: 受信パケット
+          ja-JP: 受信されたパケット
      - field: bytes_sent
        type: 0
        i18n:
          zh-CN: 发送字节
          en-US: Bytes Sent
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
      - field: bytes_received
        type: 0
        i18n:
          zh-CN: 接收字节
          en-US: Bytes Received
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: messages_sent
        type: 0
        i18n:
          zh-CN: 发送消息
          en-US: Messages Sent
-          ja-JP: 送信メッセージ
+          ja-JP: 転送されたメッセージ
      - field: messages_acked
        type: 0
        i18n:
@@ -257,13 +257,13 @@ metrics:
        i18n:
          zh-CN: 会话创建
          en-US: Session Created
-          ja-JP: 目標ホスト
+          ja-JP: 作成されたセッション
      - field: session_discarded
        type: 0
        i18n:
          zh-CN: 会话丢弃
          en-US: Session Discarded
-          ja-JP: 目標ホスト
+          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:
      - client.connected
@@ -324,7 +324,7 @@ metrics:
    i18n:
      zh-CN: 统计
      en-US: Stats
-      ja-JP: スタッツ
+      ja-JP: 統計
    priority: 2
    fields:
      # metrics content contains field-metric name, type-metric type:0-number,1-string, instance-if is metrics, unit-metric unit('%','ms','MB')
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 EulerOS 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 EulerOS</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors EulerOS operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New EulerOS</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 EulerOS 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 EulerOS</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> EulerOS システムの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 EulerOS</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> EulerOS システムの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 EulerOS</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/euleros
  en-US: https://hertzbeat.apache.org/docs/help/euleros
@@ -80,7 +80,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -92,7 +92,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -246,7 +246,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
      - field: uptime
        type: 1
        i18n:
@@ -544,14 +544,14 @@ metrics:
        i18n:
          zh-CN: 入站数据流量
          en-US: Receive Bytes
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: transmit_bytes
        type: 0
        unit: Mb
        i18n:
          zh-CN: 出站数据流量
          en-US: Transmit Bytes
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
    units:
      - receive_bytes=B->MB
      - transmit_bytes=B->MB
@@ -679,7 +679,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -738,7 +738,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 Flink流引擎的通用指标进行测量监控。<br>您可以点击 “<i>新建 Flink流引擎</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring Flink Stream through general performance metric. You could click the "<i>New Flink Stream</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 Flink流引擎的通用名額進行量測監控。<br>您可以點擊“<i>新建Flink流引擎</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: HertzBeat は Flinkの一般的なメトリック監視します。<br>「<i>新規 Flink</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: HertzBeat は Flinkの一般的なメトリクスを監視します。<br>「<i>新規 Flink</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/flink
  en-US: https://hertzbeat.apache.org/docs/help/flink
@@ -158,7 +158,7 @@ metrics:
        i18n:
          zh-CN: 已用插槽数
          en-US: Slots Used
-          ja-JP: 使用済みのスロット数
+          ja-JP: 使用したスロット数
      - field: task_total        # task count
        type: 0
        i18n:
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 Flink 流引擎 Yarn 模式的通用指标进行测量监控。<br>您可以点击 “<i>新建 Flink On Yarn</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring Flink Stream through general performance metric. You could click the "<i>New Flink Stream</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 Flink 流引擎 Yarn 模式的通用指標進行測量監控。<br>您可以點擊 “<i>新建 Flink On Yarn</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: HertzBeat は Flink 「Yarn モード」の一般的なメトリック監視します。<br>「<i>新規 Flink</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: HertzBeat は Flink 「Yarn モード」の一般的なメトリクスを監視します。<br>「<i>新規 Flink</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/flink_on_yarn
  en-US: https://hertzbeat.apache.org/docs/help/flink_on_yarn
@@ -120,7 +120,7 @@ metrics:
    i18n:
      zh-CN: JobManager Metrics
      en-US: JobManager Metrics
-      ja-JP: JobManagerメトリック
+      ja-JP: JobManagerメトリクス
    priority: 0
    fields:
      - field: id
@@ -485,7 +485,7 @@ metrics:
    i18n:
      zh-CN: TaskManager Metrics
      en-US: TaskManager Metrics
-      ja-JP: TaskManagerメトリック
+      ja-JP: TaskManagerメトリクス
    priority: 3
    fields:
      - field: container_id
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 对 FreeBSD 操作系统的通用性能指标 (系统信息、CPU、内存、磁盘、网卡、文件系统、TOP资源进程等) 进行采集监控。<br>您可以点击“<i>新建 FreeBSD</i>”并配置HOST端口账户等相关参数进行添加，支持SSH账户密码或密钥认证。或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH protocol</a> to monitors FreeBSD operating system's general performance metrics such as cpu, memory, disk, basic, interface, disk_free, top_process etc. <br>You can click the "<i>New FreeBSD</i>" and config host port and other related params to add, auth support password or secretKey. Or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSH 协议</a> 對 FreeBSD 操作系统的通用性能指標 (系統信息、CPU、內存、磁盤、網卡、文件系統、TOP資源進程等) 進行採集監控。<br>您可以點擊“<i>新建 FreeBSD</i>”並配置HOST端口賬戶等相關參數進行添加，支持SSH賬戶密碼或密鑰認證。或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Centosシステムの一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 FreeBSD</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-ssh'> SSHプロトコルを介して</a> Centosシステムの一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 FreeBSD</i>」をクリックしてホストなどのパラメタを設定した後、新規することができます。SSHまたはキー認証をサポートします。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn//docs/help/freebsd
  en-US: https://hertzbeat.apache.org/docs/help/freebsd
@@ -80,7 +80,7 @@ params:
    name:
      zh-CN: 复用连接
      en-US: Reuse Connection
-      ja-JP: コネクション再利用
+      ja-JP: 接続再利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -92,7 +92,7 @@ params:
    name:
      zh-CN: 使用代理
      en-US: Use Proxy Connection
-      ja-JP: プロキシコネクション利用
+      ja-JP: プロキシ接続利用
    # type-param field type(most mapping the html input type)
    type: boolean
    # required-true or false
@@ -246,7 +246,7 @@ metrics:
        i18n:
          zh-CN: 操作系统版本
          en-US: System Version
-          ja-JP: システムバージョン
+          ja-JP: オーエスバージョン
      - field: uptime
        type: 1
        i18n:
@@ -557,7 +557,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -616,7 +616,7 @@ metrics:
        i18n:
          zh-CN: 执行命令
          en-US: Command
-          ja-JP: 指令
+          ja-JP: コマンド
    protocol: ssh
    ssh:
      host: ^_^host^_^
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 FTP 服务器的通用指标进行测量监控。<br>您可以点击 “<i>新建 FTP服务器</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring FTP server through general performance metric. You could click the "<i>New FTP server</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對 FTP 伺服器的通用名額進行量測監控。<br>您可以點擊“<i>新建FTP伺服器</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は FTPサーバーの一般的なメトリック監視します。<br>「<i>新規 FTPサーバー</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は FTPサーバーの一般的なメトリクスを監視します。<br>「<i>新規 FTPサーバー</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/ftp
  en-US: https://hertzbeat.apache.org/docs/help/ftp
@@ -26,8 +26,8 @@ name:
 help:
  zh-CN: HertzBeat 对网站全部页面的 URL 路径、HTTP 状态码、响应时间及请求反馈进行监测。由于一个网站可能有多个不同服务提供的页面，系统将采集网站暴露的<a class='help_module_content' href='https://en.wikipedia.org/wiki/Site_map'>网站地图(SiteMap)</a>来监控全站。<span class='help_module_span'><br>⚠️注意：此功能需要您的网站支持 XML 和 TXT 格式的 SiteMap。</span>
  en-US: HertzBeat monitoring all pages of website by URL path, HTTP status code, response times and request feedback. Due to the possibility that a website may have multiple pages provided by different services, Hertzbeat will collect <a class='help_module_content' href='https://en.wikipedia.org/wiki/Site_map'>SiteMap</a> which exposed by the website to monitor the entire site. <span class='help_module_span'><br>⚠️Note:HertzBeat support SiteMap in XML or TXT format.</span>
-  zh-TW: HertzBeat對網站全部頁面的URL路徑、HTTP狀態碼、回應時間及請求迴響進行監測。 由於一個網站可能有多個不同服務提供的頁面，系統將採集網站暴露的<a class='help_ module_ content' href='https://en.wikipedia.org/wiki/Site_map'>網站地圖（SiteMap）</a>來監控全站。<span class='help_ module_ span'> <br>⚠️注意：此功能需要您的網站支持XML和TXT格式的SiteMap。</span>
-  ja-JP: HertzBeat はウェブサイトの全てのURL、HTTPステータスコード、応答時間などのメトリック監視します。ウェブサイトには、異なるサービスによって提供される複数のページが存在する可能性があるため、システムはウェブサイトによって公開される<a class='help_ module_ content' href='https://en.wikipedia.org/wiki/Site_map'>SiteMap</a>を収集して監視します。<span class='help_ module_ span'> <br>⚠️注意：この機能を使用するには、ウェブサイトがXMLおよびTXT形式のSiteMapをサポートしている必要があります。</span>
+  zh-TW: HertzBeat對網站全部頁面的URL路徑、HTTP狀態碼、回應時間及請求迴響進行監測。 由於一個網站可能有多個不同服務提供的頁面，系統將採集網站暴露的<a class='help_module_content' href='https://en.wikipedia.org/wiki/Site_map'>網站地圖（SiteMap）</a>來監控全站。<span class='help_module_span'> <br>⚠️注意：此功能需要您的網站支持XML和TXT格式的SiteMap。</span>
+  ja-JP: HertzBeat はウェブサイトの全てのURL、HTTPステータスコード、応答時間などのメトリクスを監視します。ウェブサイトには、異なるサービスによって提供される複数のページが存在する可能性があるため、システムはウェブサイトによって公開される<a class='help_module_content' href='https://en.wikipedia.org/wiki/Site_map'>SiteMap</a>を収集して監視します。<span class='help_module_span'> <br>⚠️注意：この機能を使用するには、ウェブサイトがXMLおよびTXT形式のSiteMapをサポートしている必要があります。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/guide/
  en-US: https://hertzbeat.apache.org/docs/help/guide/
@@ -27,7 +27,7 @@ help:
  zh-CN: HertzBeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jdbc'> JDBC 协议</a> 通过配置 SQL 对 GreenPlum 数据库的通用性能指标 (basic、state、activity etc) 进行采集监控，支持版本为 GreenPlum 6.23.0+。<br>您可以点击“<i>新建 GreenPlum 数据库</i>”并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jdbc'> JDBC Protocol</a> to configure SQL for collecting general metrics of GreenPlum database  (basic、state、activity etc). Supported version is GreenPlum 6.23.0+. <br>You can click "<i>New GreenPlum Database</i>" and configure it, or select "<i>More Action</i>" to import the existing configuration.
  zh-TW: HertzBeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jdbc'> JDBC 協議</a> 通過配置 SQL 對 GreenPlum 數據庫的通用性能指標 (basic、state、activity etc)進行采集監控，支持版本爲 GreenPlum 6.23.0+。<br>您可以點擊“<i>新建 GreenPlum 數據庫</i>”並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jdbc'> JDBCプロトコルを介して</a> GreenPlum データベース（6.23.0+）の一般的なパフォーマンスのメトリック監視します。<br>「<i>新規 GreenPlum データベース</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jdbc'> JDBCプロトコルを介して</a> GreenPlum データベース（6.23.0+）の一般的なパフォーマンスのメトリクスを監視します。<br>「<i>新規 GreenPlum データベース</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/greenplum
  en-US: https://hertzbeat.apache.org/docs/help/greenplum
@@ -145,7 +145,7 @@ metrics:
        i18n:
          zh-CN: 最大连接数
          en-US: Max Connections
-          ja-JP: 最大コネクション数
+          ja-JP: 最大接続数
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jdbc
    # the config content when protocol is jdbc
@@ -221,7 +221,7 @@ metrics:
        i18n:
          zh-CN: 写入时间
          en-US: Write Time
-          ja-JP: 書き込まれタイム
+          ja-JP: 書き込まれ時間
      - field: stats_reset
        type: 1
        i18n:
@@ -300,7 +300,7 @@ metrics:
        i18n:
          zh-CN: 最大连接数
          en-US: Max Connections
-          ja-JP: 最大コネクション数
+          ja-JP: 最大接続数
      - field: effective_cache_size
        type: 0
        unit: MB
@@ -332,7 +332,7 @@ metrics:
    i18n:
      zh-CN: 连接信息
      en-US: Connection Info
-      ja-JP: コネクション情報
+      ja-JP: 接続情報
    priority: 4
    fields:
      - field: active
@@ -340,7 +340,7 @@ metrics:
        i18n:
          zh-CN: 活动连接
          en-US: Active Connection
-          ja-JP: 活躍的なコネクション
+          ja-JP: 活躍的な接続
    protocol: jdbc
    jdbc:
      host: ^_^host^_^
@@ -358,7 +358,7 @@ metrics:
    i18n:
      zh-CN: 连接状态
      en-US: Connection State
-      ja-JP: コネクションステート
+      ja-JP: 接続状態
    priority: 5
    fields:
      - field: state
@@ -391,7 +391,7 @@ metrics:
    i18n:
      zh-CN: 连接数据库
      en-US: Connection Db
-      ja-JP: コネクションデータベース
+      ja-JP: 接続データベース
    priority: 6
    fields:
      - field: db_name
@@ -406,7 +406,7 @@ metrics:
        i18n:
          zh-CN: 活动连接
          en-US: Active Connection
-          ja-JP: 活躍的なコネクション
+          ja-JP: 活躍的な接続
    protocol: jdbc
    jdbc:
      host: ^_^host^_^
@@ -555,7 +555,7 @@ metrics:
    i18n:
      zh-CN: 慢查询
      en-US: Slow Sql
-      ja-JP: スロークエリ
+      ja-JP: スローSQL
    priority: 10
    fields:
      - field: sql_text
@@ -564,7 +564,7 @@ metrics:
        i18n:
          zh-CN: SQL语句
          en-US: SQL Text
-          ja-JP: SQL
+          ja-JP: SQL文のテキスト
      - field: calls
        type: 0
        i18n:
@@ -23,7 +23,6 @@ name:
  en-US: GreptimeDB
  ja-JP: GreptimeDB
 # The description and help of this monitoring type
-# 监控类型的帮助描述信息
 help:
  zh-CN: HertzBeat 对 GreptimeDB 时序数据库进行监控。<br><span class='help_module_span'><a class='help_module_content' https://docs.greptime.com/user-guide/operations/monitoring'>点击查看开启步骤</a>。</span>
  en-US: HertzBeat monitors the GreptimeDB time series database. <br><span class='help_module_span'><a class='help_module_content' https://docs.greptime.com/user-guide/operations/monitoring'>Click to view the activation steps</a>. </span>
@@ -366,7 +365,7 @@ metrics:
    i18n:
      zh-CN: greptime 服务 MySQL 连接数
      en-US: greptime_servers_mysql_connection_count
-      ja-JP: MySQLのコネクション数
+      ja-JP: MySQLの接続数
    priority: 10
    fields:
      - field: value
@@ -389,7 +388,7 @@ metrics:
    i18n:
      zh-CN: greptime 服务 Postgres 连接数
      en-US: greptime_servers_postgres_connection_count
-      ja-JP: Postgresのコネクション数
+      ja-JP: Postgresの接続数
    priority: 11
    fields:
      - field: value
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 协议</a> 对 华三交换机 的通用指标(可用性，系统信息，端口流量等)进行采集监控。<br>您可以点击 “<i>新建 华三通用交换机</i>” 并进行配置SNMP相关参数添加，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP Protocol</a> to monitoring H3C Switch general performance metrics. <br>You can click the "<i>New H3C Switch</i>" button and config snmp params to add monitor or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 協議</a> 對 華三交換機 的通用指標(可用性，系統信息，端口流量等)進行采集監控。<br>您可以點擊 “<i>新建 華三通用交換機</i>” 並進行配置SNMP相關參數添加，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP プロトコルを介して</a> H3Cスイッチングハブの一般的なメトリック監視します。<br>「<i>新規 H3Cスイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP プロトコルを介して</a> H3Cスイッチングハブの一般的なメトリクスを監視します。<br>「<i>新規 H3Cスイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/h3c_switch
  en-US: https://hertzbeat.apache.org/docs/help/h3c_switch
@@ -361,13 +361,13 @@ metrics:
        i18n:
          zh-CN: 入流量
          en-US: In Octets
-          ja-JP: 受信バイト数
+          ja-JP: 受信されたバイト数
      - field: in_discards
        type: 0
        i18n:
          zh-CN: 入丢包数
          en-US: In Discards
-          ja-JP: 受信パケットロス数
+          ja-JP: 受信されたパケットのロス数
      - field: in_errors
        type: 0
        i18n:
@@ -380,19 +380,19 @@ metrics:
        i18n:
          zh-CN: 出流量
          en-US: Out Octets
-          ja-JP: 送信バイト数
+          ja-JP: 転送されたバイト数
      - field: out_discards
        type: 0
        i18n:
          zh-CN: 出丢包数
          en-US: Out Discards
-          ja-JP: 送信パケットロス数
+          ja-JP: 転送されたパケットのロス数
      - field: out_errors
        type: 0
        i18n:
          zh-CN: 出错包数
          en-US: Out Errors
-          ja-JP: 送信異常パケット数
+          ja-JP: 転送異常パケット数
      - field: admin_status
        type: 1
        i18n:
@@ -404,7 +404,7 @@ metrics:
        i18n:
          zh-CN: 当前状态
          en-US: Current Status
-          ja-JP: ステータス
+          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:
      - ifIndex
@@ -26,8 +26,8 @@ name:
 help:
  zh-CN: HertzBeat 使用<a class='help_module_content' href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'> JMX 协议</a>对 Hadoop 的 JVM 虚拟机的通用性能指标（memory pool，限JDK8及以下的code cache、class loading、thread）进行采集监控。<br><span class='help_module_span'>⚠️注意：您需要在 Hadoop 应用开启 JMX 服务, <a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>点击查看开启步骤</a>。</span>
  en-US: "HertzBeat monitors general performance metrics(memory pool, class loading, thread) of Hadoop VMware through <a class='help_module_content' href='https://zh.wikipedia.org/JMX'>JMX protocol</a>. <br><span class='help_module_span'>⚠️Note: You should enable the JMX service in Hadoop application, and the metric of code cache is only available to JDK8 and below.<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>Click here to view the specific steps.</a></span>"
-  zh-TW: HertzBeat使用<a class='help_ module_ content' href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'> JMX協定</a>對Hadoop的JVM虛擬機器的通用性能指標（memory pool，限JDK8及以下的code cache、class loading、thread）進行採集監控。<br><span class='help_ module_ span'> ⚠️ ️注意：您需要在Hadoop應用開啟JMX服務，<a class='help_ module_ content' href='https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>點擊查看開啟步驟</a>。</span>
-  ja-JP: HertzBeatは <a class='help_module_content' href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'> JMXプロトコルを介して</a> HadoopのJava仮想マシンの一般的なパフォーマンスのメトリックを監視します。<br><span class='help_module_span'> ⚠️注意：Hadoop で JMX サービスを有効にする必要があります。<a class='help_module_content' href=' https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>クリックしてガイドを見ます</a>。</span>
+  zh-TW: HertzBeat使用<a class='help_module_content' href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'> JMX協定</a>對Hadoop的JVM虛擬機器的通用性能指標（memory pool，限JDK8及以下的code cache、class loading、thread）進行採集監控。<br><span class='help_module_span'> ⚠️ ️注意：您需要在Hadoop應用開啟JMX服務，<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>點擊查看開啟步驟</a>。</span>
+  ja-JP: HertzBeatは <a class='help_module_content' href='https://baijiahao.baidu.com/s?id=1605937053950156833&wfr=spider&for=pc'> JMXプロトコルを介して</a> HadoopのJava仮想マシンの一般的なパフォーマンスのメトリクスを監視します。<br><span class='help_module_span'> ⚠️注意：Hadoop で JMX サービスを有効にする必要があります。<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/hadoop#hadoop%E5%BA%94%E7%94%A8%E5%BC%80%E5%90%AFjmx%E5%8D%8F%E8%AE%AE%E6%AD%A5%E9%AA%A4'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hadoop/
  en-US: https://hertzbeat.apache.org/docs/help/hadoop/
@@ -168,14 +168,14 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: Name
-          ja-JP: 指標名
+          ja-JP: メトリクス名
      - field: committed
        type: 0
        unit: MB
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
-          ja-JP: コミットメモリ
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        unit: MB
@@ -196,7 +196,7 @@ metrics:
        i18n:
          zh-CN: 已使用内存
          en-US: Used
-          ja-JP: 使用済みのメモリ
+          ja-JP: 使用したメモリ
    units:
      - committed=B->MB
      - init=B->MB
@@ -240,7 +240,7 @@ metrics:
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
-          ja-JP: コミットメモリ
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        i18n:
@@ -258,7 +258,7 @@ metrics:
        i18n:
          zh-CN: 已使用内存
          en-US: Used
-          ja-JP: 使用済みのメモリ
+          ja-JP: 使用したメモリ
    aliasFields:
      - Usage->committed
      - Usage->init
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 Hbase 数据库 Master 节点监控指标进行监控。<br>您可以点击 “<i>新建 Apache Hbase Master</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors the Master node monitoring indicators of the Hbase database. <br>You can click "<i>New Apache Hbase Master</i>" to configure, or select "<i>More Actions</i>" to import an existing configuration.
  zh-TW: Hertzbeat 對 Hbase 數據庫 Master 节點監控指標進行監控。<br>您可以點擊 “<i>新建 Apache Hbase Master</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は HbaseデータベースのMasterノードの一般的なメトリック監視します。<br>「<i>新規 Apache Hbase Master</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は HbaseデータベースのMasterノードの一般的なメトリクスを監視します。<br>「<i>新規 Apache Hbase Master</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hbase_master/
  en-US: https://hertzbeat.apache.org/docs/help/hbase_master/
@@ -92,7 +92,7 @@ metrics:
    i18n:
      zh-CN: Master服务信息
      en-US: Master Service Info
-      ja-JP: 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
@@ -224,7 +224,7 @@ metrics:
        i18n:
          zh-CN: Master节点
          en-US: masterHostName
-          ja-JP: Masterホスト名
+          ja-JP: マスターホスト名
      - field: BalancerCluster_num_ops
        type: 0
        i18n:
@@ -243,14 +243,14 @@ metrics:
        i18n:
          zh-CN: 集群接收数据量(MB)
          en-US: receivedBytes
-          ja-JP: 受信バイト
+          ja-JP: 受信されたバイト
      - field: sentBytes
        type: 0
        unit: 'MB'
        i18n:
          zh-CN: 集群发送数据量(MB)
          en-US: sentBytes
-          ja-JP: 送信バイト
+          ja-JP: 転送されたバイト
      - field: clusterRequests
        type: 0
        i18n:
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 Hbase 数据库 RegionServer 节点监控指标进行监控。<br>您可以点击 “<i>新建 Apache Hbase RegionServer</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors the RegionServer node monitoring indicators of the Hbase database. <br>You can click "<i>New Apache Hbase RegionServer</i>" to configure, or select "<i>More Actions</i>" to import an existing configuration.
  zh-TW: Hertzbeat 對 Hbase 數據庫 RegionServer 节點監控指標進行監控。<br>您可以點擊 “<i>新建 Apache Hbase RegionServer</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は HbaseデータベースのRegionServerノードの一般的なメトリック監視します。<br>「<i>新規 Apache Hbase RegionServer</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は HbaseデータベースのRegionServerノードの一般的なメトリクスを監視します。<br>「<i>新規 Apache Hbase RegionServer</i>」をクリックしてパラメタを設定した後、新規することができます。

 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hbase_regionserver/
@@ -530,7 +530,7 @@ metrics:
          i18n:
            zh-CN: 进程使用的非堆内存大小
            en-US: MemNonHeapUsedM
-            ja-JP: 使用済みのノンヒープメモリサイズ
+            ja-JP: 使用したノンヒープメモリのサイズ
        # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
        - field: MemNonHeapCommittedM
          type: 0
@@ -538,7 +538,7 @@ metrics:
          i18n:
            zh-CN: 进程 commit 的非堆内存大小
            en-US: MemNonHeapCommittedM
-            ja-JP: コミットのノンヒープメモリサイズ
+            ja-JP: コミットされたノンヒープメモリのサイズ
        # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
        - field: MemHeapUsedM
          type: 0
@@ -546,7 +546,7 @@ metrics:
          i18n:
            zh-CN: 进程使用的堆内存大小
            en-US: MemHeapUsedM
-            ja-JP: 使用済みのヒープメモリサイズ
+            ja-JP: 使用したヒープメモリのサイズ
        # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
        - field: MemHeapCommittedM
          type: 0
@@ -554,7 +554,7 @@ metrics:
          i18n:
            zh-CN: 进程 commit 的堆内存大小
            en-US: MemHeapCommittedM
-            ja-JP: コミットのヒープメモリサイズ
+            ja-JP: コミットされたヒープメモリのサイズ
        # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
        - field: MemHeapMaxM
          type: 0
@@ -562,7 +562,7 @@ metrics:
          i18n:
            zh-CN: 进程最大的堆内存大小
            en-US: MemHeapMaxM
-            ja-JP: 最大のヒープメモリサイズ
+            ja-JP: ヒープメモリサイズの最大値
        # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
        - field: MemMaxM
          type: 0
@@ -570,7 +570,7 @@ metrics:
          i18n:
            zh-CN: 进程最大内存大小
            en-US: MemMaxM
-            ja-JP: 最大のメモリサイズ
+            ja-JP: メモリサイズの最大値
        # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
        - field: GcCount
          type: 0
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 HDFS DataNode 节点监控指标进行监控。<br>您可以点击 “<i>新建 Apache HDFS DataNode</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors the HDFS DataNode metrics. <br>You can click "<i>New Apache HDFS DataNode</i>" to configure, or select "<i>More Actions</i>" to import an existing configuration.
  zh-TW: Hertzbeat 對 HDFS DataNode 節點監控指標進行監控。<br>您可以點擊 “<i>新建 Apache HDFS DataNode</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は HDFS DataNodeの一般的なメトリック監視します。<br>「<i>新規 Apache HDFS DataNode</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は HDFS DataNodeの一般的なメトリクスを監視します。<br>「<i>新規 Apache HDFS DataNode</i>」をクリックしてパラメタを設定した後、新規することができます。

 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hdfs_datanode/
@@ -91,7 +91,7 @@ metrics:
        i18n:
          zh-CN: DataNode HDFS使用量
          en-US: DfsUsed
-          ja-JP: 使用済みのHDFS容量
+          ja-JP: 使用したHDFS容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: Remaining
        type: 0
@@ -142,70 +142,70 @@ metrics:
        i18n:
          zh-CN: JVM 当前已经使用的 NonHeapMemory 的大小
          en-US: MemNonHeapUsedM
-          ja-JP: 使用済みのノンヒープメモリサイズ
+          ja-JP: 使用したノンヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemNonHeapCommittedM
        type: 0
        i18n:
          zh-CN: JVM 配置的 NonHeapCommittedM 的大小
          en-US: MemNonHeapCommittedM
-          ja-JP: コミットのノンヒープメモリサイズ
+          ja-JP: コミットされたノンヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemHeapUsedM
        type: 0
        i18n:
          zh-CN: JVM 当前已经使用的 HeapMemory 的大小
          en-US: MemHeapUsedM
-          ja-JP: 使用済みのヒープメモリサイズ
+          ja-JP: 使用したヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemHeapCommittedM
        type: 0
        i18n:
          zh-CN: JVM HeapMemory 提交大小
          en-US: MemHeapCommittedM
-          ja-JP: コミットのヒープメモリサイズ
+          ja-JP: コミットされたヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemHeapMaxM
        type: 0
        i18n:
          zh-CN: JVM 配置的 HeapMemory 的大小
          en-US: MemHeapMaxM
-          ja-JP: 配置のヒープメモリサイズ
+          ja-JP: 配置のヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemMaxM
        type: 0
        i18n:
          zh-CN: JVM 运行时可以使用的最大内存大小
          en-US: MemMaxM
-          ja-JP: 最大のヒープメモリサイズ
+          ja-JP: 最大のヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsRunnable
        type: 0
        i18n:
          zh-CN: 处于 RUNNABLE 状态的线程数量
          en-US: ThreadsRunnable
-          ja-JP: RUNNABLE スレッド数
+          ja-JP: 実行中のスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsBlocked
        type: 0
        i18n:
          zh-CN: 处于 BLOCKED 状态的线程数量
          en-US: ThreadsBlocked
-          ja-JP: BLOCKED スレッド数
+          ja-JP: ブロックされたスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsWaiting
        type: 0
        i18n:
          zh-CN: 处于 WAITING 状态的线程数量
          en-US: ThreadsWaiting
-          ja-JP: WAITING スレッド数
+          ja-JP: 待機中のスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsTimedWaiting
        type: 0
        i18n:
          zh-CN: 处于 TIMED WAITING 状态的线程数量
          en-US: ThreadsTimedWaiting
-          ja-JP: TIMED WAITING スレッド数
+          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:
      - $.MemNonHeapUsedM
@@ -27,7 +27,7 @@ help:
  zh-CN: Hertzbeat 对 HDFS NameNode 节点监控指标进行监控。<br>您可以点击 “<i>新建 Apache HDFS NameNode</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors the HDFS NameNode metrics. <br>You can click "<i>New Apache HDFS NameNode</i>" to configure, or select "<i>More Actions</i>" to import an existing configuration.
  zh-TW: Hertzbeat 對 HDFS NameNode 節點監控指標進行監控。<br>您可以點擊 “<i>新建 Apache HDFS NameNode</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
-  ja-JP: Hertzbeat は HDFS NameNodeの一般的なメトリック監視します。<br>「<i>新規 Apache HDFS NameNode</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は HDFS NameNodeの一般的なメトリクスを監視します。<br>「<i>新規 Apache HDFS NameNode</i>」をクリックしてパラメタを設定した後、新規することができます。

 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hdfs_namenode/
@@ -105,7 +105,7 @@ metrics:
        i18n:
          zh-CN: 集群存储已使用容量
          en-US: CapacityUsed
-          ja-JP: 使用済みの容量
+          ja-JP: 使用した容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: CapacityUsedGB
        type: 0
@@ -113,7 +113,7 @@ metrics:
          zh-CN: 集群存储已使用容量
          unit: 'GB'
          en-US: CapacityUsedGB
-          ja-JP: 使用済みの容量（ＧＢ）
+          ja-JP: 使用した容量（ＧＢ）
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: CapacityRemaining
        type: 0
@@ -135,14 +135,14 @@ metrics:
        i18n:
          zh-CN: 集群非 HDFS 使用容量
          en-US: CapacityUsedNonDFS
-          ja-JP: 使用済みのノンHDFS容量
+          ja-JP: 使用したノンHDFS容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: TotalLoad
        type: 0
        i18n:
          zh-CN: 整个集群的客户端连接数
          en-US: TotalLoad
-          ja-JP: クライアントとのコネクション総数
+          ja-JP: クライアントとの接続総数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: FilesTotal
        type: 0
@@ -336,14 +336,14 @@ metrics:
        i18n:
          zh-CN: 接收数据速率
          en-US: ReceivedBytes
-          ja-JP: 受信バイト
+          ja-JP: 受信されたバイト
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: SentBytes
        type: 0
        i18n:
          zh-CN: 发送数据速率
          en-US: SentBytes
-          ja-JP: 送信バイト
+          ja-JP: 転送されたバイト
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: RpcQueueTimeNumOps
        type: 0
@@ -369,7 +369,6 @@ metrics:
      ssl: ^_^ssl^_^
      parseType: jsonPath
      parseScript: '$.beans[?(@.name =~ /Hadoop:service=NameNode,name=RpcActivityForPort80\d+/)]'
-#      parseScript: '$.beans[?(@.name == "Hadoop:service=NameNode,name=RpcActivityForPort8020")]'
  - name: runtime
    # 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
@@ -382,7 +381,7 @@ metrics:
        i18n:
          zh-CN: 启动时间
          en-US: StartTime
-          ja-JP: 目標ホスト
+          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:
      - $.beans[?(@.name == "java.lang:type=Runtime")].StartTime
@@ -410,56 +409,56 @@ metrics:
        i18n:
          zh-CN: JVM 当前已经使用的 NonHeapMemory 的大小
          en-US: MemNonHeapUsedM
-          ja-JP: 使用済みのノンヒープメモリサイズ
+          ja-JP: 使用したノンヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemNonHeapCommittedM
        type: 0
        i18n:
          zh-CN: JVM 配置的 NonHeapCommittedM 的大小
          en-US: MemNonHeapCommittedM
-          ja-JP: コミットのノンヒープメモリサイズ
+          ja-JP: コミットされたノンヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemHeapUsedM
        type: 0
        i18n:
          zh-CN: JVM 当前已经使用的 HeapMemory 的大小
          en-US: MemHeapUsedM
-          ja-JP: 使用済みのヒープメモリサイズ
+          ja-JP: 使用したヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemHeapCommittedM
        type: 0
        i18n:
          zh-CN: JVM HeapMemory 提交大小
          en-US: MemHeapCommittedM
-          ja-JP: コミットのヒープメモリサイズ
+          ja-JP: コミットされたヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemHeapMaxM
        type: 0
        i18n:
          zh-CN: JVM 配置的 HeapMemory 的大小
          en-US: MemHeapMaxM
-          ja-JP: 配置のヒープメモリサイズ
+          ja-JP: 配置のヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: MemMaxM
        type: 0
        i18n:
          zh-CN: JVM 运行时可以使用的最大内存大小
          en-US: MemMaxM
-          ja-JP: 最大のヒープメモリサイズ
+          ja-JP: 最大のヒープメモリのサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: GcCountParNew
        type: 0
        i18n:
          zh-CN: 新生代GC次数
          en-US: GcCountParNew
-          ja-JP: 新領域GC回数
+          ja-JP: 若い領域GC回数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: GcTimeMillisParNew
        type: 0
        i18n:
          zh-CN: 新生代GC消耗时间
          en-US: GcTimeMillisParNew
-          ja-JP: 新領域GC時間
+          ja-JP: 若い領域GC時間
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: GcCountConcurrentMarkSweep
        type: 0
@@ -494,28 +493,28 @@ metrics:
        i18n:
          zh-CN: 处于 RUNNABLE 状态的线程数量
          en-US: ThreadsRunnable
-          ja-JP: RUNNABLE スレッド数
+          ja-JP: 実行中のスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsBlocked
        type: 0
        i18n:
          zh-CN: 处于 BLOCKED 状态的线程数量
          en-US: ThreadsBlocked
-          ja-JP: BLOCKED スレッド数
+          ja-JP: ブロックされたスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsWaiting
        type: 0
        i18n:
          zh-CN: 处于 WAITING 状态的线程数量
          en-US: ThreadsWaiting
-          ja-JP: WAITING スレッド数
+          ja-JP: 待機中のスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: ThreadsTimedWaiting
        type: 0
        i18n:
          zh-CN: 处于 TIMED WAITING 状态的线程数量
          en-US: ThreadsTimedWaiting
-          ja-JP: TIMED WAITING スレッド数
+          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:
      - $.MemNonHeapUsedM
@@ -26,7 +26,7 @@ help:
  zh-CN: Hertzbeat 对 Hertzbeat 监控系统的通用指标进行测量监控。<br>您可以点击 “<i>新建 HertzBeat监控系统</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors HertzBeat Monitor through general performance metric. You could click the "<i>New HertzBeat Monitor</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat對Hertzbeat監控系統的通用指標進行量測監控。<br>您可以點擊“<i>新建HertzBeat監控系統</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は Hertzbeatの一般的なメトリック監視します。<br>「<i>新規 Apache Hertzbeat</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は Hertzbeatの一般的なメトリクスを監視します。<br>「<i>新規 Apache Hertzbeat</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hertzbeat
  en-US: https://hertzbeat.apache.org/docs/help/hertzbeat
@@ -323,7 +323,7 @@ metrics:
    i18n:
      zh-CN: 内存使用
      en-US: Memory Used
-      ja-JP: 使用済みのメモリ
+      ja-JP: 使用したメモリ
    priority: 5
    fields:
      - field: space
@@ -338,7 +338,7 @@ metrics:
        i18n:
          zh-CN: 已使用内存
          en-US: Used Memory
-          ja-JP: 使用済みのメモリ
+          ja-JP: 使用したメモリ
    aliasFields:
      - $.measurements[?(@.statistic == "VALUE")].value
    calculates:
@@ -28,7 +28,7 @@ help:
  zh-CN: Hertzbeat 对 HertzBeat监控(Token)进行测量监控。<br>您可以点击 “<i>新建 HertzBeat监控(Token)</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors HertzBeat Monitor(Token). You could click the "<i>New HertzBeat Monitor(Token)</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat對HertzBeat監控（Token）進行量測監控。<br>您可以點擊“<i>新建HertzBeat監控（Token）</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
-  ja-JP: Hertzbeat は Hertzbeat(Token)の一般的なメトリック監視します。<br>「<i>新規 Apache Hertzbeat(Token)</i>」をクリックしてパラメタを設定した後、新規することができます。
+  ja-JP: Hertzbeat は Hertzbeat(Token)の一般的なメトリクスを監視します。<br>「<i>新規 Apache Hertzbeat(Token)</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hertzbeat_token
  en-US: https://hertzbeat.apache.org/docs/help/hertzbeat_token
@@ -337,7 +337,7 @@ metrics:
    i18n:
      zh-CN: 内存使用
      en-US: Memory Used
-      ja-JP: 使用済みのメモリ
+      ja-JP: 使用したメモリ
    priority: 5
    fields:
      - field: space
@@ -352,7 +352,7 @@ metrics:
        i18n:
          zh-CN: 内存使用量
          en-US: Memory Used
-          ja-JP: 使用済みのメモリ
+          ja-JP: 使用したメモリ
    aliasFields:
      - $.measurements[?(@.statistic == "VALUE")].value
    calculates:
@@ -21,10 +21,12 @@ app: hikvision_isapi
 name:
  zh-CN: 海康威视 ISAPI
  en-US: Hikvision ISAPI
+  ja-JP: Hikvision ISAPI
 # The description and help of this monitoring type
 help:
  zh-CN: 通过ISAPI接口监控海康威视设备状态，获取设备健康数据。
  en-US: Monitor Hikvision devices through ISAPI interface to collect health data.
+  ja-JP: ISAPIを呼び出して健康データを収集し、Hikvisionデバイスを監視します。

 # Input params define for monitoring(render web ui by the definition)
 params:
@@ -32,12 +34,14 @@ params:
    name:
      zh-CN: 主机Host
      en-US: Host
+      ja-JP: ホスト
    type: host
    required: true
  - field: port
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    type: number
    range: '[0,65535]'
    required: true
@@ -46,6 +50,7 @@ params:
    name:
      zh-CN: 超时时间(ms)
      en-US: Timeout(ms)
+      ja-JP: タイムアウト（ｍｓ）
    type: number
    range: '[1000,60000]'
    required: true
@@ -54,18 +59,21 @@ params:
    name:
      zh-CN: 用户名
      en-US: Username
+      ja-JP: ユーザー名
    type: text
    required: true
  - field: password
    name:
      zh-CN: 密码
      en-US: Password
+      ja-JP: パスワード
    type: password
    required: true
  - field: ssl
    name:
      zh-CN: 启用HTTPS
      en-US: SSL
+      ja-JP: SSL利用
    type: boolean
    required: false
    defaultValue: false
@@ -76,6 +84,7 @@ metrics:
    i18n:
      zh-CN: 系统信息
      en-US: System Info
+      ja-JP: システム情報
    priority: 0
    protocol: http
    http:
@@ -97,30 +106,36 @@ metrics:
        i18n:
          zh-CN: 设备名称
          en-US: Device Name
+          ja-JP: デバイス名
      - field: deviceID
        type: 1
        i18n:
          zh-CN: 设备ID
          en-US: Device ID
+          ja-JP: デバイスID
      - field: firmwareVersion
        type: 1
        i18n:
          zh-CN: 固件版本
          en-US: Firmware Version
+          ja-JP: ファームウェアバージョン
      - field: model
        type: 1
        i18n:
          zh-CN: 设备型号
          en-US: Device Model
+          ja-JP: デバイスモデル
      - field: macAddress
        type: 1
        i18n:
          zh-CN: mac地址
          en-US: Mac Address
+          ja-JP: Macアドレス
  - name: status
    i18n:
      zh-CN: 设备状态
      en-US: Status
+      ja-JP: 状態
    priority: 0
    protocol: http
    http:
@@ -141,91 +156,107 @@ metrics:
        i18n:
          zh-CN: CPU 利用率
          en-US: CPU Utilization
+          ja-JP: CPU使用率
        type: 0
        unit: '%'
      - field: memory_usage
        i18n:
          zh-CN: 内存使用量
          en-US: Memory Usage
+          ja-JP: メモリ使用量
        type: 0
        unit: MB
      - field: memory_available
        i18n:
          zh-CN: 可用内存
          en-US: Memory Available
+          ja-JP: 使用可能のメモリ
        type: 0
        unit: MB
      - field: cache_size
        i18n:
          zh-CN: 缓存大小
          en-US: Cache Size
+          ja-JP: キャッシュサイズ
        type: 0
        unit: MB
      - field: net_port_1_speed
        i18n:
          zh-CN: 网口1速度
          en-US: Net Port 1 Speed
+          ja-JP: ネットポート1速度
        type: 0
        unit: Mbps
      - field: net_port_2_speed
        i18n:
          zh-CN: 网口2速度
          en-US: Net Port 2 Speed
+          ja-JP: ネットポート2速度
        type: 0
        unit: Mbps
      - field: boot_time
        i18n:
          zh-CN: 启动时间
          en-US: Boot Time
+          ja-JP: 起動時間
        type: 1
      - field: device_uptime
        i18n:
          zh-CN: 运行时长
          en-US: Device Uptime
+          ja-JP: デバイスアップタイム
        type: 1
      - field: last_calibration_time
        i18n:
          zh-CN: 上次校时时间
          en-US: Last Calibration Time
+          ja-JP: 最終校正時刻
        type: 1
      - field: last_calibration_time_diff
        i18n:
          zh-CN: 上次校时时间差
          en-US: Last Calibration Time Diff
+          ja-JP: 最終校正時間差
        type: 0
        unit: s
      - field: avg_upload_time
        i18n:
          zh-CN: 平均上传耗时
          en-US: Avg Upload Time
+          ja-JP: 平均アップロード時間
        type: 0
        unit: ms
      - field: max_upload_time
        i18n:
          zh-CN: 最大上传耗时
          en-US: Max Upload Time
+          ja-JP: 最大アップロード時間
        type: 0
        unit: ms
      - field: min_upload_time
        i18n:
          zh-CN: 最小上传耗时
          en-US: Min Upload Time
+          ja-JP: 最小アップロード時間
        type: 0
        unit: ms
      - field: last_calibration_mode
        i18n:
          zh-CN: 上次校时模式
          en-US: Last Calibration Mode
+          ja-JP: 最終校正モード
        type: 1
      - field: last_calibration_address
        i18n:
          zh-CN: 上次校时地址
          en-US: Last Calibration Address
+          ja-JP: 最終校正アドレス
        type: 1
      - field: response_time
        i18n:
          zh-CN: 响应时间
          en-US: Response Time
+          ja-JP: 応答時間
        type: 0
        unit: ms
    aliasFields:
@@ -21,11 +21,13 @@ app: hive
 name:
  zh-CN: Apache Hive
  en-US: Apache Hive
+  ja-JP: Apache Hive
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 对 <a class='help_module_content' href='https://cwiki.apache.org/confluence/display/Hive/Hive+Metrics'> HServer2 </a> 暴露的通用性能指标(basic、environment、thread、code_cache)进行采集监控。<span class='help_module_span'>⚠️注意：如果要监控 Apache Hive 中的信息，需要您的 Apache Hive 应用集成并开启 Hive Server2, <a class='help_module_content'  href='https://hertzbeat.apache.org/zh-cn/docs/help/hive'>点击查看具体步骤</a>。</span>
  en-US: HertzBeat collects and monitors Apache Hive through general performance metric(health, environment, threads, memory_used) that exposed by the Hive Server2. <br><span class='help_module_span'>⚠️Note:You should make sure that your Apache Hive application have already integrated and enabled the Hive Server2, <a class='help_module_content'  href='https://hertzbeat.apache.org/docs/help/hive'>click here to see the specific steps.</a></span>
  zh-TW: HertzBeat 對<a class='help_module_content' href='https://cwiki.apache.org/confluence/display/Hive/Hive+Metrics'> HServer2 </a>暴露的通用性能指標（basic、environment、thread、code_cache）進行採集監控。< span class='help_module_span'> ⚠️ 注意：如果要監控Apache Hive中的指標，需要您的Apache Hive應用集成並開啟Hive Server2，<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/hive'>點擊查看具體步驟</a>。</span>
+  ja-JP: HertzBeat は <a class='help_module_content' href='https://cwiki.apache.org/confluence/display/Hive/Hive+Metrics'> HServer2 </a> の一般的なパフォーマンスのメトリクスを監視します。<span class='help_module_span'>⚠️注意：Apache Hive で Hive Server2を有効にする必要があります。<a class='help_module_content'  href='https://hertzbeat.apache.org/docs/help/hive'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hive
  en-US: https://hertzbeat.apache.org/docs/help/hive
@@ -37,6 +39,7 @@ params:
    name:
      zh-CN: 目标 Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    # type-param field type(most mapping the html input type)
    type: host
    # required-true or false
@@ -47,6 +50,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -61,6 +65,7 @@ params:
    name:
      zh-CN: 启动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
@@ -71,6 +76,7 @@ params:
    name:
      zh-CN: Base Path
      en-US: Base Path
+      ja-JP: Base Path
    # type-param field type(most mapping the html input type) The type "text" belongs to a text input field.
    type: text
    # default value
@@ -86,6 +92,7 @@ metrics:
    i18n:
      zh-CN: 可用性
      en-US: Availability
+      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
@@ -96,6 +103,7 @@ metrics:
        i18n:
          zh-CN: 响应时间
          en-US: Response Time
+          ja-JP: 応答時間
        type: 0
        unit: ms
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
@@ -119,27 +127,32 @@ metrics:
    i18n:
      zh-CN: 基本信息
      en-US: Basic
+      ja-JP: 基礎情報
    priority: 1
    fields:
      - field: vm_name
        i18n:
          zh-CN: 虚拟机名称
          en-US: VM Name
+          ja-JP: 仮想マシン名
        type: 1
      - field: vm_vendor
        i18n:
          zh-CN: 虚拟机供应商
          en-US: VM Vendor
+          ja-JP: 仮想マシンベンダー
        type: 1
      - field: vm_version
        i18n:
          zh-CN: 虚拟机版本
          en-US: VM Version
+          ja-JP: 仮想マシンバージョン
        type: 1
      - field: up_time
        i18n:
          zh-CN: 运行时间
          en-US: Uptime
+          ja-JP: アップタイム
        type: 0
        unit: ms
    aliasFields:
@@ -167,6 +180,7 @@ metrics:
    i18n:
      zh-CN: 环境信息
      en-US: Environment
+      ja-JP: 環境
    priority: 2
    # collect metrics content
    fields:
@@ -175,31 +189,37 @@ metrics:
        i18n:
          zh-CN: https 代理端口
          en-US: https Proxy Port
+          ja-JP: https プロキシポート
        type: 0
      - field: os_name
        i18n:
          zh-CN: os 名称
          en-US: OS Name
+          ja-JP: OS名
        type: 1
      - field: os_version
        i18n:
          zh-CN: os 版本
          en-US: OS Version
+          ja-JP: OSバージョン
        type: 1
      - field: os_arch
        i18n:
          zh-CN: os 架构
          en-US: OS Arch
+          ja-JP: OSアーキテクチャ
        type: 1
      - field: java_runtime_name
        i18n:
          zh-CN: java 运行时名称
          en-US: Java Runtime Name
+          ja-JP: Java ランタイム名
        type: 1
      - field: java_runtime_version
        i18n:
          zh-CN: java 运行时版本
          en-US: Java Runtime Version
+          ja-JP: Java ランタイムバージョン
        type: 1
    # metric alias list, used to identify metrics in query results
    aliasFields:
@@ -240,27 +260,32 @@ metrics:
    i18n:
      zh-CN: 线程
      en-US: Thread
+      ja-JP: スレッド
    priority: 3
    fields:
      - field: thread_count
        i18n:
          zh-CN: 线程数
          en-US: Thread Count
+          ja-JP: スレッド総数
        type: 0
      - field: total_started_thread
        i18n:
          zh-CN: 启动线程数
          en-US: Total Started Thread
+          ja-JP: スレッド開始数
        type: 0
      - field: peak_thread_count
        i18n:
          zh-CN: 峰值线程数
          en-US: Peak Thread Count
+          ja-JP: ピークスレッド数
        type: 0
      - field: daemon_thread_count
        i18n:
          zh-CN: 守护线程数
          en-US: Daemon Thread Count
+          ja-JP: デーモンスレッド数
        type: 0
    aliasFields:
      - $.beans[?(@.name == 'java.lang:type=Threading')].ThreadCount
@@ -286,30 +311,35 @@ metrics:
    i18n:
      zh-CN: 代码缓存
      en-US: Code Cache
+      ja-JP: コードキャッシュ
    priority: 4
    fields:
      - field: committed
        i18n:
          zh-CN: 已提交
          en-US: Committed
+          ja-JP: コミット
        type: 1
        unit: MB
      - field: init
        i18n:
          zh-CN: 初始化
          en-US: Init
+          ja-JP: イニシャル
        type: 0
        unit: MB
      - field: max
        i18n:
          zh-CN: 最大
          en-US: Max
+          ja-JP: 最大
        type: 0
        unit: MB
      - field: used
        i18n:
          zh-CN: 已使用
          en-US: Used
+          ja-JP: 使用済み
        type: 0
        unit: MB
    aliasFields:
@@ -21,11 +21,13 @@ app: hpe_switch
 name:
  zh-CN: HPE通用交换机
  en-US: HPE Switch
+  ja-JP: HPEスイッチングハブ
 # The description and help of this monitoring type
 help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 协议</a> 对 HPE交换机 的通用指标(可用性，系统信息，端口流量等)进行采集监控。<br>您可以点击 “<i>新建 HPE通用交换机</i>” 并进行配置SNMP相关参数添加，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP Protocol</a> to monitoring HPE Switch general performance metrics. <br>You can click the "<i>New HPE Switch</i>" button and config snmp params to add monitor or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 協議</a> 對 HPE交換機 的通用指標(可用性，系統信息，端口流量等)進行采集監控。<br>您可以點擊 “<i>新建 HPE通用交換機</i>” 並進行配置SNMP相關參數添加，或者選擇“<i>更多操作</i>”，導入已有配置。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP プロトコルを介して</a> HPEスイッチングハブの一般的なメトリクスを監視します。<br>「<i>新規 HPEスイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hpe_switch
  en-US: https://hertzbeat.apache.org/docs/help/hpe_switch
@@ -37,6 +39,7 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    # type-param field type(most mapping the html input type)
    type: host
    # required-true or false
@@ -47,6 +50,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -61,6 +65,7 @@ params:
    name:
      zh-CN: SNMP 版本
      en-US: SNMP Version
+      ja-JP: SNMPバージョン
    # type-param field type(radio mapping the html radio tag)
    type: radio
    # required-true or false
@@ -79,6 +84,7 @@ params:
    name:
      zh-CN: SNMP 团体字
      en-US: SNMP Community
+      ja-JP: SNMPコミュニティ
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -98,6 +104,7 @@ params:
    name:
      zh-CN: SNMP username
      en-US: SNMP username
+      ja-JP: SNMPユーザー名
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -116,6 +123,7 @@ params:
    name:
      zh-CN: SNMP contextName
      en-US: SNMP contextName
+      ja-JP: SNMPコンテキスト名
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -134,6 +142,7 @@ params:
    name:
      zh-CN: SNMP authPassword
      en-US: SNMP authPassword
+      ja-JP: SNMP認証パスワード
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -152,6 +161,7 @@ params:
    name:
      zh-CN: authPassword 加密方式
      en-US: authPassword Encryption
+      ja-JP: 認証暗号
    # type-param field type(radio mapping the html radio tag)
    type: radio
    # required-true or false
@@ -172,6 +182,7 @@ params:
    name:
      zh-CN: SNMP privPassphrase
      en-US: SNMP privPassphrase
+      ja-JP: SNMPパスワードフレーズ
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -190,6 +201,7 @@ params:
    name:
      zh-CN: privPassword 加密方式
      en-US: privPassword Encryption
+      ja-JP: パスワードの暗号
    # type-param field type(radio mapping the html radio tag)
    type: radio
    # required-true or false
@@ -210,6 +222,7 @@ params:
    name:
      zh-CN: 超时时间(ms)
      en-US: Timeout(ms)
+      ja-JP: タイムアウト（ｍｓ）
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -227,6 +240,7 @@ metrics:
    i18n:
      zh-CN: 系统信息
      en-US: System Info
+      ja-JP: システム情報
    # metrics scheduling priority(0->127)->(high->low), metrics with the same priority will be scheduled in parallel
    # priority 0's metrics is availability metrics, it will be scheduled first, only availability metrics collect success will the scheduling continue
    priority: 0
@@ -238,32 +252,38 @@ metrics:
        i18n:
          zh-CN: 主机名称
          en-US: Host Name
+          ja-JP: ホスト名
      - field: descr
        type: 1
        i18n:
          zh-CN: 描述信息
          en-US: Description
+          ja-JP: 説明
      - field: uptime
        type: 1
        i18n:
          zh-CN: 运行时长
          en-US: Uptime
+          ja-JP: アップタイム
      - field: location
        type: 1
        i18n:
          zh-CN: 位置
          en-US: Location
+          ja-JP: 位置
      - field: contact
        type: 1
        i18n:
          zh-CN: 联系人
          en-US: Contact
+          ja-JP: 連絡先
      - field: responseTime
        type: 0
        unit: ms
        i18n:
          zh-CN: 响应时间
          en-US: Response Time
+          ja-JP: 応答時間
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: snmp
    # the config content when protocol is snmp
@@ -305,6 +325,7 @@ metrics:
    i18n:
      zh-CN: 接口详情
      en-US: Interfaces Detail
+      ja-JP: ネットワークカード詳細
    priority: 1
    fields:
      - field: index
@@ -312,68 +333,79 @@ metrics:
        i18n:
          zh-CN: 编号
          en-US: Index
+          ja-JP: 番号
      - field: descr
        type: 1
        label: true
        i18n:
          zh-CN: 接口名称
          en-US: Interface Name
+          ja-JP: ネットワークカード名
      - field: mtu
        type: 0
        unit: 'byte'
        i18n:
          zh-CN: MTU
          en-US: MTU
+          ja-JP: MTU
      - field: speed
        type: 0
        unit: 'MB/s'
        i18n:
          zh-CN: 接口速率
          en-US: Interface Speed
+          ja-JP: ネットワークカード速度
      - field: in_octets
        type: 0
        unit: 'MByte'
        i18n:
          zh-CN: 入流量
          en-US: In Octets
+          ja-JP: 受信されたバイト数
      - field: in_discards
        type: 0
        i18n:
          zh-CN: 入丢包数
          en-US: In Discards
+          ja-JP: 受信されたパケットのロス数
      - field: in_errors
        type: 0
        i18n:
          zh-CN: 入错包数
          en-US: In Errors
+          ja-JP: 受信異常パケット数
      - field: out_octets
        type: 0
        unit: 'MByte'
        i18n:
          zh-CN: 出流量
          en-US: Out Octets
+          ja-JP: 転送されたバイト数
      - field: out_discards
        type: 0
        i18n:
          zh-CN: 出丢包数
          en-US: Out Discards
+          ja-JP: 転送されたパケットのロス数
      - field: out_errors
        type: 0
        i18n:
          zh-CN: 出错包数
          en-US: Out Errors
+          ja-JP: 転送異常パケット数
      - field: admin_status
        type: 1
        i18n:
          zh-CN: 配置状态
          en-US: Config Status
+          ja-JP: 設定ステータス
      - field: oper_status
        type: 1
        i18n:
          zh-CN: 当前状态
          en-US: Current Status
+          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:
      - ifIndex
      - ifDescr
@@ -21,6 +21,7 @@ app: http_sd
 name:
  zh-CN: Http Service Discovery
  en-US: Http Service Discovery
+  ja-JP: Httpサービスディスカバリー
 # Input params define for app api(render web ui by the definition)
 params:
  # field-param field key
@@ -29,6 +30,7 @@ params:
    name:
      zh-CN: 服务发现地址
      en-US: Service Discovery Url
+      ja-JP: サービスディスカバリー Url
    # type-param field type(most mapping the html input type)
    type: text
    # required-true or false
@@ -39,6 +41,7 @@ params:
    name:
      zh-CN: 认证方式
      en-US: Auth Type
+      ja-JP: 認証方法
    # type-param field type(most mapping the html input type)
    type: radio
    # required-true or false
@@ -57,6 +60,7 @@ params:
    name:
      zh-CN: 认证Token
      en-US: Access Token
+      ja-JP: アクセストークン
    # type-param field type(most mapping the html input type)
    type: text
    # dependent parameter values list
@@ -73,6 +77,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
@@ -92,6 +97,7 @@ params:
    name:
      zh-CN: 密码
      en-US: Password
+      ja-JP: パスワード
    # type-param field type(most mapping the html input type)
    type: password
    # dependent parameter values list
@@ -109,6 +115,7 @@ metrics:
    i18n:
      zh-CN: 监控目标
      en-US: Monitor Target
+      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
@@ -120,11 +127,13 @@ metrics:
        i18n:
          zh-CN: Host
          en-US: Host
+          ja-JP: ホスト
      - field: port
        type: 1
        i18n:
          zh-CN: Port
          en-US: Port
+          ja-JP: ポート
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: http_sd
    # the config content when protocol is http_sd
@@ -21,11 +21,13 @@ app: huawei_switch
 name:
  zh-CN: 华为通用交换机
  en-US: Huawei Switch
+  ja-JP: Huaweiスイッチングハブ
 # The description and help of this monitoring type
 help:
  zh-CN: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 协议</a> 对 华为交换机 的通用指标(可用性，系统信息，端口流量等)进行采集监控。<br>您可以点击 “<i>新建 华为通用交换机</i>” 并进行配置SNMP相关参数添加，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP Protocol</a> to monitoring Huawei Switch general performance metrics. <br>You can click the "<i>New Huawei Switch</i>" button and config snmp params to add monitor or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP 協議</a> 對 华为交換機 的通用指標(可用性，系統信息，端口流量等)進行采集監控。<br>您可以點擊 “<i>新建 华为通用交換機</i>” 並進行配置SNMP相關參數添加，或者選擇“<i>更多操作</i>”，導入已有配置。
+  ja-JP: Hertzbeat は <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-snmp'> SNMP プロトコルを介して</a> Huaweiスイッチングハブの一般的なメトリクスを監視します。<br>「<i>新規 Huaweiスイッチングハブ</i>」をクリックしてSNMPなどのパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/huawei_switch
  en-US: https://hertzbeat.apache.org/docs/help/huawei_switch
@@ -37,6 +39,7 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    # type-param field type(most mapping the html input type)
    type: host
    # required-true or false
@@ -47,6 +50,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -61,6 +65,7 @@ params:
    name:
      zh-CN: SNMP 版本
      en-US: SNMP Version
+      ja-JP: SNMPバージョン
    # type-param field type(radio mapping the html radio tag)
    type: radio
    # required-true or false
@@ -79,6 +84,7 @@ params:
    name:
      zh-CN: SNMP 团体字
      en-US: SNMP Community
+      ja-JP: SNMPコミュニティ
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -98,6 +104,7 @@ params:
    name:
      zh-CN: SNMP username
      en-US: SNMP username
+      ja-JP: SNMPユーザー名
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -116,6 +123,7 @@ params:
    name:
      zh-CN: SNMP contextName
      en-US: SNMP contextName
+      ja-JP: SNMPコンテキスト名
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -134,6 +142,7 @@ params:
    name:
      zh-CN: SNMP authPassword
      en-US: SNMP authPassword
+      ja-JP: SNMP認証パスワード
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -152,6 +161,7 @@ params:
    name:
      zh-CN: authPassword 加密方式
      en-US: authPassword Encryption
+      ja-JP: 認証暗号
    # type-param field type(radio mapping the html radio tag)
    type: radio
    # required-true or false
@@ -172,6 +182,7 @@ params:
    name:
      zh-CN: SNMP privPassphrase
      en-US: SNMP privPassphrase
+      ja-JP: SNMPパスワードフレーズ
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -190,6 +201,7 @@ params:
    name:
      zh-CN: privPassword 加密方式
      en-US: privPassword Encryption
+      ja-JP: パスワードの暗号
    # type-param field type(radio mapping the html radio tag)
    type: radio
    # required-true or false
@@ -210,6 +222,7 @@ params:
    name:
      zh-CN: 超时时间(ms)
      en-US: Timeout(ms)
+      ja-JP: タイムアウト（ｍｓ）
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -227,6 +240,7 @@ metrics:
    i18n:
      zh-CN: 系统信息
      en-US: System Info
+      ja-JP: システム情報
    # metrics scheduling priority(0->127)->(high->low), metrics with the same priority will be scheduled in parallel
    # priority 0's metrics is availability metrics, it will be scheduled first, only availability metrics collect success will the scheduling continue
    priority: 0
@@ -238,32 +252,38 @@ metrics:
        i18n:
          zh-CN: 主机名称
          en-US: Host Name
+          ja-JP: ホスト名
      - field: descr
        type: 1
        i18n:
          zh-CN: 描述信息
          en-US: Description
+          ja-JP: 説明
      - field: uptime
        type: 1
        i18n:
          zh-CN: 运行时长
          en-US: Uptime
+          ja-JP: アップタイム
      - field: location
        type: 1
        i18n:
          zh-CN: 位置
          en-US: Location
+          ja-JP: 位置
      - field: contact
        type: 1
        i18n:
          zh-CN: 联系人
          en-US: Contact
+          ja-JP: 連絡先
      - field: responseTime
        type: 0
        unit: ms
        i18n:
          zh-CN: 响应时间
          en-US: Response Time
+          ja-JP: 応答時間
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: snmp
    # the config content when protocol is snmp
@@ -304,6 +324,7 @@ metrics:
    i18n:
      zh-CN: 接口详情
      en-US: Interfaces Detail
+      ja-JP: ネットワークカード詳細
    priority: 1
    fields:
      - field: index
@@ -311,66 +332,78 @@ metrics:
        i18n:
          zh-CN: 编号
          en-US: Index
+          ja-JP: 番号
      - field: descr
        type: 1
        label: true
        i18n:
          zh-CN: 接口名称
          en-US: Interface Name
+          ja-JP: ネットワークカード名
      - field: mtu
        type: 0
        unit: 'byte'
        i18n:
          zh-CN: MTU
          en-US: MTU
+          ja-JP: MTU
      - field: speed
        type: 0
        unit: 'MB/s'
        i18n:
          zh-CN: 接口速率
          en-US: Interface Speed
+          ja-JP: ネットワークカード速度
      - field: in_octets
        type: 0
        unit: 'MByte'
        i18n:
          zh-CN: 入流量
          en-US: In Octets
+          ja-JP: 受信されたバイト数
      - field: in_discards
        type: 0
        i18n:
          zh-CN: 入丢包数
          en-US: In Discards
+          ja-JP: 受信されたパケットのロス数
      - field: in_errors
        type: 0
        i18n:
          zh-CN: 入错包数
          en-US: In Errors
+          ja-JP: 受信異常パケット数
      - field: out_octets
        type: 0
        unit: 'MByte'
        i18n:
          zh-CN: 出流量
          en-US: Out Octets
+          ja-JP: 転送されたバイト数
      - field: out_discards
        type: 0
        i18n:
          zh-CN: 出丢包数
          en-US: Out Discards
+          ja-JP: 転送されたパケットのロス数
      - field: out_errors
        type: 0
        i18n:
          zh-CN: 出错包数
          en-US: Out Errors
+          ja-JP: 転送異常パケット数
      - field: admin_status
        type: 1
        i18n:
          zh-CN: 配置状态
          en-US: Config Status
+          ja-JP: 設定ステータス
      - field: oper_status
        type: 1
        i18n:
          zh-CN: 当前状态
          en-US: Current Status
+          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:
      - ifIndex
@@ -21,11 +21,13 @@ app: hugegraph
 name:
  zh-CN: HugeGraph
  en-US: HugeGraph
+  ja-JP: HugeGraph
 # The description and help of this monitoring type
 help:
  zh-CN: Hertzbeat 对 HugeGraph 节点监控指标进行监控。<br>您可以点击 “<i>新建 Apache HugeGraph</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitors the HugeGraph metrics. <br>You can click "<i>New Apache HugeGraph</i>" to configure, or select "<i>More Actions</i>" to import an existing configuration.
  zh-TW: Hertzbeat 對 HugeGraph 節點監控指標進行監控。<br>您可以點擊 “<i>新建 Apache HugeGraph</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
+  ja-JP: Hertzbeat は HugeGraphノードの一般的なメトリクスを監視します。<br>「<i>新規 Apache HugeGraph</i>」をクリックしてパラメタを設定した後、新規することができます。

 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/hugegraph
@@ -38,6 +40,7 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    # type-param field type(most mapping the html input type)
    type: host
    # required-true or false
@@ -48,6 +51,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -62,6 +66,7 @@ params:
    name:
      zh-CN: 启动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
@@ -72,6 +77,7 @@ params:
    name:
      zh-CN: Base Path
      en-US: Base Path
+      ja-JP: Base Path
    # type-param field type(most mapping the html input type) The type "text" belongs to a text input field.
    type: text
    # default value
@@ -94,336 +100,392 @@ metrics:
        i18n:
          zh-CN: edge-hugegraph-capacity
          en-US: edge-hugegraph-capacity
+          ja-JP: edge-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: edge-hugegraph-expire
        type: 0
        i18n:
          zh-CN: edge-hugegraph-expire
          en-US: edge-hugegraph-expire
+          ja-JP: edge-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: edge-hugegraph-hits
        type: 0
        i18n:
          zh-CN: edge-hugegraph-hits
          en-US: edge-hugegraph-hits
+          ja-JP: edge-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: edge-hugegraph-miss
        type: 0
        i18n:
          zh-CN: edge-hugegraph-miss
          en-US: edge-hugegraph-miss
+          ja-JP: edge-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: edge-hugegraph-size
        type: 0
        i18n:
          zh-CN: edge-hugegraph-size
          en-US: edge-hugegraph-size
+          ja-JP: edge-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: instances
        type: 0
        i18n:
          zh-CN: instances
          en-US: instances
+          ja-JP: instances
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-id-hugegraph-capacity
        type: 0
        i18n:
          zh-CN: schema-id-hugegraph-capacity
          en-US: schema-id-hugegraph-capacity
+          ja-JP: schema-id-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-id-hugegraph-expire
        type: 0
        i18n:
          zh-CN: schema-id-hugegraph-expire
          en-US: schema-id-hugegraph-expire
+          ja-JP: schema-id-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-id-hugegraph-hits
        type: 0
        i18n:
          zh-CN: schema-id-hugegraph-hits
          en-US: schema-id-hugegraph-hits
+          ja-JP: schema-id-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-id-hugegraph-miss
        type: 0
        i18n:
          zh-CN: schema-id-hugegraph-miss
          en-US: schema-id-hugegraph-miss
+          ja-JP: schema-id-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-id-hugegraph-size
        type: 0
        i18n:
          zh-CN: schema-id-hugegraph-size
          en-US: schema-id-hugegraph-size
+          ja-JP: schema-id-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-name-hugegraph-capacity
        type: 0
        i18n:
          zh-CN: schema-name-hugegraph-capacity
          en-US: schema-name-hugegraph-capacity
+          ja-JP: schema-name-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-name-hugegraph-expire
        type: 0
        i18n:
          zh-CN: schema-name-hugegraph-expire
          en-US: schema-name-hugegraph-expire
+          ja-JP: schema-name-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-name-hugegraph-hits
        type: 0
        i18n:
          zh-CN: schema-name-hugegraph-hits
          en-US: schema-name-hugegraph-hits
+          ja-JP: schema-name-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-name-hugegraph-miss
        type: 0
        i18n:
          zh-CN: schema-name-hugegraph-miss
          en-US: schema-name-hugegraph-miss
+          ja-JP: schema-name-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: schema-name-hugegraph-size
        type: 0
        i18n:
          zh-CN: schema-name-hugegraph-size
          en-US: schema-name-hugegraph-size
+          ja-JP: schema-name-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: token-hugegraph-capacity
        type: 0
        i18n:
          zh-CN: token-hugegraph-capacity
          en-US: token-hugegraph-capacity
+          ja-JP: token-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: token-hugegraph-expire
        type: 0
        i18n:
          zh-CN: token-hugegraph-expire
          en-US: token-hugegraph-expire
+          ja-JP: token-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: token-hugegraph-hits
        type: 0
        i18n:
          zh-CN: token-hugegraph-hits
          en-US: token-hugegraph-hits
+          ja-JP: token-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: token-hugegraph-miss
        type: 0
        i18n:
          zh-CN: token-hugegraph-miss
          en-US: token-hugegraph-miss
+          ja-JP: token-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: token-hugegraph-size
        type: 0
        i18n:
          zh-CN: token-hugegraph-size
          en-US: token-hugegraph-size
+          ja-JP: token-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users-hugegraph-capacity
        type: 0
        i18n:
          zh-CN: users-hugegraph-capacity
          en-US: users-hugegraph-capacity
+          ja-JP: users-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users-hugegraph-expire
        type: 0
        i18n:
          zh-CN: users-hugegraph-expire
          en-US: users-hugegraph-expire
+          ja-JP: users-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users-hugegraph-hits
        type: 0
        i18n:
          zh-CN: users-hugegraph-hits
          en-US: users-hugegraph-hits
+          ja-JP: users-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users-hugegraph-miss
        type: 0
        i18n:
          zh-CN: users-hugegraph-miss
          en-US: users-hugegraph-miss
+          ja-JP: users-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users-hugegraph-size
        type: 0
        i18n:
          zh-CN: users-hugegraph-size
          en-US: users-hugegraph-size
+          ja-JP: users-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users_pwd-hugegraph-capacity
        type: 0
        i18n:
          zh-CN: users_pwd-hugegraph-capacity
          en-US: users_pwd-hugegraph-capacity
+          ja-JP: users_pwd-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users_pwd-hugegraph-expire
        type: 0
        i18n:
          zh-CN: users_pwd-hugegraph-expire
          en-US: users_pwd-hugegraph-expire
+          ja-JP: users_pwd-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users_pwd-hugegraph-hits
        type: 0
        i18n:
          zh-CN: users_pwd-hugegraph-hits
          en-US: users_pwd-hugegraph-hits
+          ja-JP: users_pwd-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users_pwd-hugegraph-miss
        type: 0
        i18n:
          zh-CN: users_pwd-hugegraph-miss
          en-US: users_pwd-hugegraph-miss
+          ja-JP: users_pwd-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: users_pwd-hugegraph-size
        type: 0
        i18n:
          zh-CN: users_pwd-hugegraph-size
          en-US: users_pwd-hugegraph-size
+          ja-JP: users_pwd-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: vertex-hugegraph-capacity
        type: 0
        i18n:
          zh-CN: vertex-hugegraph-capacity
          en-US: vertex-hugegraph-capacity
+          ja-JP: vertex-hugegraph容量
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: vertex-hugegraph-expire
        type: 0
        i18n:
          zh-CN: vertex-hugegraph-expire
          en-US: vertex-hugegraph-expire
+          ja-JP: vertex-hugegraph期限切れ数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: vertex-hugegraph-hits
        type: 0
        i18n:
          zh-CN: vertex-hugegraph-hits
          en-US: vertex-hugegraph-hits
+          ja-JP: vertex-hugegraphヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: vertex-hugegraph-miss
        type: 0
        i18n:
          zh-CN: vertex-hugegraph-miss
          en-US: vertex-hugegraph-miss
+          ja-JP: vertex-hugegraphミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: vertex-hugegraph-size
        type: 0
        i18n:
          zh-CN: vertex-hugegraph-size
          en-US: vertex-hugegraph-size
+          ja-JP: vertex-hugegraphサイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: batch-write-threads
        type: 0
        i18n:
          zh-CN: batch-write-threads
          en-US: batch-write-threads
+          ja-JP: 一括書き込みスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: max-write-threads
        type: 0
        i18n:
          zh-CN: max-write-threads
          en-US: max-write-threads
+          ja-JP: 最大書き込みスレッド数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: pending-tasks
        type: 0
        i18n:
          zh-CN: pending-tasks
          en-US: pending-tasks
+          ja-JP: ペンディングタスク数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: workers
        type: 0
        i18n:
          zh-CN: workers
          en-US: workers
+          ja-JP: ワーカー数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: average-load-penalty
        type: 0
        i18n:
          zh-CN: average-load-penalty
          en-US: average-load-penalty
+          ja-JP: 平均負荷ペナルティ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: estimated-size
        type: 0
        i18n:
          zh-CN: estimated-size
          en-US: estimated-size
+          ja-JP: 推定サイズ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: eviction-count
        type: 0
        i18n:
          zh-CN: eviction-count
          en-US: eviction-count
+          ja-JP: 立ち退き数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: eviction-weight
        type: 0
        i18n:
          zh-CN: eviction-weight
          en-US: eviction-weight
+          ja-JP: 立ち退きウェイト
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: hit-count
        type: 0
        i18n:
          zh-CN: hit-count
          en-US: hit-count
+          ja-JP: ヒット数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: hit-rate
        type: 0
        i18n:
          zh-CN: hit-rate
          en-US: hit-rate
+          ja-JP: ヒット率
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: load-count
        type: 0
        i18n:
          zh-CN: load-count
          en-US: load-count
+          ja-JP: ロード数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: load-failure-count
        type: 0
        i18n:
          zh-CN: load-failure-count
          en-US: load-failure-count
+          ja-JP: ロード失敗数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: load-failure-rate
        type: 0
        i18n:
          zh-CN: load-failure-rate
          en-US: load-failure-rate
+          ja-JP: ロード失敗率
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: load-success-count
        type: 0
        i18n:
          zh-CN: load-success-count
          en-US: load-success-count
+          ja-JP: ロード成功数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: long-run-compilation-count
        type: 0
        i18n:
          zh-CN: long-run-compilation-count
          en-US: long-run-compilation-count
+          ja-JP: long-run-compilation-count
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: miss-count
        type: 0
        i18n:
          zh-CN: miss-count
          en-US: miss-count
+          ja-JP: ミス数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: miss-rate
        type: 0
        i18n:
          zh-CN: miss-rate
          en-US: miss-rate
+          ja-JP: ミス率
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: request-count
        type: 0
        i18n:
          zh-CN: request-count
          en-US: request-count
+          ja-JP: リクエスト数
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: total-load-time
        type: 0
        i18n:
          zh-CN: total-load-time
          en-US: total-load-time
+          ja-JP: ロード時間合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: sessions
        type: 0
        i18n:
          zh-CN: sessions
          en-US: sessions
+          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:
      - $.['org.apache.hugegraph.backend.cache.Cache.edge-hugegraph.capacity'].['value']
@@ -568,90 +630,105 @@ metrics:
        i18n:
          zh-CN: GET-SUCCESS_COUNTER
          en-US: GET-SUCCESS_COUNTER
+          ja-JP: GET成功カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: GET-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: GET-TOTAL_COUNTER
          en-US: GET-TOTAL_COUNTER
+          ja-JP: GETカウンタ合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: favicon-ico-GET-FAILED_COUNTER
        type: 0
        i18n:
          zh-CN: favicon-ico-GET-FAILED_COUNTER
          en-US: favicon-ico-GET-FAILED_COUNTER
+          ja-JP: favicon-ico-GET失敗カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: favicon-ico-GET-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: favicon-ico-GET-TOTAL_COUNTER
          en-US: favicon-ico-GET-TOTAL_COUNTER
+          ja-JP: favicon-ico-GETカウンタ合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: graphs-HEAD-FAILED_COUNTER
        type: 0
        i18n:
          zh-CN: graphs-HEAD-FAILED_COUNTER
          en-US: graphs-HEAD-FAILED_COUNTER
+          ja-JP: graphs-HEAD失敗カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: graphs-HEAD-SUCCESS_COUNTER
        type: 0
        i18n:
          zh-CN: graphs-HEAD-SUCCESS_COUNTER
          en-US: graphs-HEAD-SUCCESS_COUNTER
+          ja-JP: graphs-HEAD成功カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: graphs-HEAD-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: graphs-HEAD-TOTAL_COUNTER
          en-US: graphs-HEAD-TOTAL_COUNTER
+          ja-JP: graphs-HEADカウンタ合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: graphs-hugegraph-graph-vertices-GET-SUCCESS_COUNTER
        type: 0
        i18n:
          zh-CN: graphs-hugegraph-graph-vertices-GET-SUCCESS_COUNTER
          en-US: graphs-hugegraph-graph-vertices-GET-SUCCESS_COUNTER
+          ja-JP: graphs-hugegraph-graph-vertices-GET成功カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: graphs-hugegraph-graph-vertices-GET-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: graphs-hugegraph-graph-vertices-GET-TOTAL_COUNTER
          en-US: graphs-hugegraph-graph-vertices-GET-TOTAL_COUNTER
+          ja-JP: graphs-hugegraph-graph-vertices-GETカウンタ合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: metircs-GET-FAILED_COUNTER
        type: 0
        i18n:
          zh-CN: metircs-GET-FAILED_COUNTER
          en-US: metircs-GET-FAILED_COUNTER
+          ja-JP: metircs-GET失敗カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: metircs-GET-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: metircs-GET-TOTAL_COUNTER
          en-US: metircs-GET-TOTAL_COUNTER
+          ja-JP: metircs-GETカウンタ合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: metrics-GET-SUCCESS_COUNTER
        type: 0
        i18n:
          zh-CN: metrics-GET-SUCCESS_COUNTER
          en-US: metrics-GET-SUCCESS_COUNTER
+          ja-JP: metircs-GET成功カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: metrics-GET-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: metrics-GET-TOTAL_COUNTER
          en-US: metrics-GET-TOTAL_COUNTER
+          ja-JP: metircs-GETカウンタ合計
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: metrics-gauges-GET-SUCCESS_COUNTER
        type: 0
        i18n:
          zh-CN: metrics-gauges-GET-SUCCESS_COUNTER
          en-US: metrics-gauges-GET-SUCCESS_COUNTER
+          ja-JP: metrics-gauges-GET成功カウンタ
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
      - field: metrics-gauges-GET-TOTAL_COUNTER
        type: 0
        i18n:
          zh-CN: metrics-gauges-GET-TOTAL_COUNTER
          en-US: metrics-gauges-GET-TOTAL_COUNTER
+          ja-JP: metrics-gauges-GETカウンタ合計
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
    aliasFields:
      - $.['//GET/SUCCESS_COUNTER'].['count']
@@ -705,126 +782,151 @@ metrics:
        i18n:
          zh-CN: mem
          en-US: mem
+          ja-JP: メモリ
      - field: mem_total
        type: 0
        i18n:
          zh-CN: mem_total
          en-US: mem_total
+          ja-JP: メモリ容量
      - field: mem_used
        type: 0
        i18n:
          zh-CN: mem_used
          en-US: mem_used
+          ja-JP: 使用したメモリ
      - field: mem_free
        type: 0
        i18n:
          zh-CN: mem_free
          en-US: mem_free
+          ja-JP: 利用可能なメモリ
      - field: mem_unit
        type: 1
        i18n:
          zh-CN: mem_unit
          en-US: mem_unit
+          ja-JP: メモリ単位
      - field: processors
        type: 0
        i18n:
-          zh-CN: processors
+          zh-CN: 处理器数
          en-US: processors
+          ja-JP: プロセッサ数
      - field: uptime
        type: 0
        i18n:
          zh-CN: uptime
          en-US: uptime
+          ja-JP: アップタイム
      - field: systemload_average
        type: 0
        i18n:
          zh-CN: systemload_average
          en-US: systemload_average
+          ja-JP: システムロードアベレージ
      - field: heap_committed
        type: 0
        i18n:
          zh-CN: heap_committed
          en-US: heap_committed
+          ja-JP: ヒープのコミットされたメモリ
      - field: heap_init
        type: 0
        i18n:
          zh-CN: heap_init
          en-US: heap_init
+          ja-JP: ヒープのイニシャルメモリ
      - field: heap_used
        type: 0
        i18n:
          zh-CN: heap_used
          en-US: heap_used
+          ja-JP: ヒープの使用したメモリ
      - field: heap_max
        type: 0
        i18n:
          zh-CN: heap_max
          en-US: heap_max
+          ja-JP: ヒープの最大メモリ
      - field: nonheap_committed
        type: 0
        i18n:
          zh-CN: nonheap_committed
          en-US: nonheap_committed
+          ja-JP: ノンヒープのコミットされたメモリ
      - field: nonheap_init
        type: 0
        i18n:
          zh-CN: nonheap_init
          en-US: nonheap_init
+          ja-JP: ノンヒープのイニシャルメモリ
      - field: nonheap_used
        type: 0
        i18n:
          zh-CN: nonheap_used
          en-US: nonheap_used
+          ja-JP: ノンヒープの使用したメモリ
      - field: nonheap_max
        type: 0
        i18n:
          zh-CN: nonheap_max
          en-US: nonheap_max
+          ja-JP: ノンヒープの最大メモリ
      - field: thread_peak
        type: 0
        i18n:
          zh-CN: thread_peak
          en-US: thread_peak
+          ja-JP: ピークスレッド数
      - field: thread_daemon
        type: 0
        i18n:
          zh-CN: thread_daemon
          en-US: thread_daemon
+          ja-JP: デーモンスレッド数
      - field: thread_total_started
        type: 0
        i18n:
          zh-CN: thread_total_started
          en-US: thread_total_started
+          ja-JP: スレッド開始数
      - field: thread_count
        type: 0
        i18n:
          zh-CN: thread_count
          en-US: thread_count
+          ja-JP: スレッド総数
      - field: garbage_collector_g1_young_generation_count
        type: 0
        i18n:
          zh-CN: garbage_collector_g1_young_generation_count
          en-US: garbage_collector_g1_young_generation_count
+          ja-JP: garbage_collector_g1若い領域GC回数
      - field: garbage_collector_g1_young_generation_time
        type: 0
        i18n:
          zh-CN: garbage_collector_g1_young_generation_time
          en-US: garbage_collector_g1_young_generation_time
+          ja-JP: garbage_collector_g1若い領域GC時間
      - field: garbage_collector_g1_old_generation_count
        type: 0
        i18n:
          zh-CN: garbage_collector_g1_old_generation_count
          en-US: garbage_collector_g1_old_generation_count
+          ja-JP: garbage_collector_g1古い領域GC回数
      - field: garbage_collector_g1_old_generation_time
        type: 0
        i18n:
          zh-CN: garbage_collector_g1_old_generation_time
          en-US: garbage_collector_g1_old_generation_time
+          ja-JP: garbage_collector_g1古い領域GC時間
      - field: garbage_collector_time_unit
        type: 1
        i18n:
          zh-CN: garbage_collector_time_unit
          en-US: garbage_collector_time_unit
+          ja-JP: garbage_collector時間単位
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
    aliasFields:
      - $.basic.mem
@@ -21,11 +21,13 @@ app: iceberg
 name:
  zh-CN: Apache Iceberg
  en-US: Apache Iceberg
+  ja-JP: Apache Iceberg
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 对 <a class='help_module_content' href='https://cwiki.apache.org/confluence/display/Hive/Hive+Metrics'> HServer2 </a> 暴露的通用性能指标(basic、environment、thread、code_cache)进行采集监控。<span class='help_module_span'>⚠️注意：如果要监控 Apache Iceberg 中的信息，需要您的 Apache Iceberg 应用集成并开启 Hive Server2, <a class='help_module_content'  href='https://hertzbeat.apache.org/zh-cn/docs/help/hive'>点击查看具体步骤</a>。</span>
  en-US: HertzBeat collects and monitors Apache Iceberg through general performance metric(health, environment, threads, memory_used) that exposed by the Hive Server2. <br><span class='help_module_span'>⚠️Note:You should make sure that your Apache Iceberg application have already integrated and enabled the Hive Server2, <a class='help_module_content'  href='https://hertzbeat.apache.org/docs/help/hive'>click here to see the specific steps.</a></span>
  zh-TW: HertzBeat 對<a class='help_module_content' href='https://cwiki.apache.org/confluence/display/Hive/Hive+Metrics'> HServer2 </a>暴露的通用性能指標（basic、environment、thread、code_cache）進行採集監控。< span class='help_module_span'> ⚠️ 注意：如果要監控Apache Iceberg 中的指標，需要您的Apache Iceberg 應用集成並開啟 Hive Server2，<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/hive'>點擊查看具體步驟</a>。</span>
+  ja-JP: HertzBeat は <a class='help_module_content' href='https://cwiki.apache.org/confluence/display/Hive/Hive+Metrics'> HServer2 </a> の一般的なパフォーマンスのメトリクスを監視します。<span class='help_module_span'>⚠️注意：Apache Iceberg で Hive Server2を有効にする必要があります。<a class='help_module_content'  href='https://hertzbeat.apache.org/docs/help/hive'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/iceberg
  en-US: https://hertzbeat.apache.org/docs/help/iceberg
@@ -37,6 +39,7 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    # type-param field type(most mapping the html input type)
    type: host
    # required-true or false
@@ -47,6 +50,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -61,6 +65,7 @@ params:
    name:
      zh-CN: 启动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
@@ -71,6 +76,7 @@ params:
    name:
      zh-CN: Base Path
      en-US: Base Path
+      ja-JP: Base Path
    # type-param field type(most mapping the html input type) The type "text" belongs to a text input field.
    type: text
    # default value
@@ -83,6 +89,10 @@ params:
 metrics:
  # metrics - available
  - name: available
+    i18n:
+      zh-CN: 可用性
+      en-US: Availability
+      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
@@ -93,6 +103,7 @@ metrics:
        i18n:
          zh-CN: 响应时间
          en-US: Response Time
+          ja-JP: 応答時間
        type: 0
        unit: ms
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
@@ -116,27 +127,32 @@ metrics:
    i18n:
      zh-CN: 基本信息
      en-US: Basic
+      ja-JP: 基礎情報
    priority: 1
    fields:
      - field: vm_name
        i18n:
          zh-CN: 虚拟机名称
          en-US: VM Name
+          ja-JP: 仮想マシン名
        type: 1
      - field: vm_vendor
        i18n:
          zh-CN: 虚拟机供应商
          en-US: VM Vendor
+          ja-JP: 仮想マシンベンダー
        type: 1
      - field: vm_version
        i18n:
          zh-CN: 虚拟机版本
          en-US: VM Version
+          ja-JP: 仮想マシンバージョン
        type: 1
      - field: up_time
        i18n:
          zh-CN: 运行时间
          en-US: Uptime
+          ja-JP: アップタイム
        type: 0
        unit: ms
    aliasFields:
@@ -164,6 +180,7 @@ metrics:
    i18n:
      zh-CN: 环境信息
      en-US: Environment
+      ja-JP: 環境
    priority: 2
    # collect metrics content
    fields:
@@ -172,31 +189,37 @@ metrics:
        i18n:
          zh-CN: https 代理端口
          en-US: https Proxy Port
+          ja-JP: https プロキシポート
        type: 0
      - field: os_name
        i18n:
          zh-CN: os 名称
          en-US: OS Name
+          ja-JP: OS名
        type: 1
      - field: os_version
        i18n:
          zh-CN: os 版本
          en-US: OS Version
+          ja-JP: OSバージョン
        type: 1
      - field: os_arch
        i18n:
          zh-CN: os 架构
          en-US: OS Arch
+          ja-JP: OSアーキテクチャ
        type: 1
      - field: java_runtime_name
        i18n:
          zh-CN: java 运行时名称
          en-US: Java Runtime Name
+          ja-JP: Java ランタイム名
        type: 1
      - field: java_runtime_version
        i18n:
          zh-CN: java 运行时版本
          en-US: Java Runtime Version
+          ja-JP: Java ランタイムバージョン
        type: 1
    # metric alias list, used to identify metrics in query results
    aliasFields:
@@ -237,27 +260,32 @@ metrics:
    i18n:
      zh-CN: 线程
      en-US: Thread
+      ja-JP: スレッド
    priority: 3
    fields:
      - field: thread_count
        i18n:
          zh-CN: 线程数
          en-US: Thread Count
+          ja-JP: スレッド総数
        type: 0
      - field: total_started_thread
        i18n:
          zh-CN: 启动线程数
          en-US: Total Started Thread
+          ja-JP: スレッド開始数
        type: 0
      - field: peak_thread_count
        i18n:
          zh-CN: 峰值线程数
          en-US: Peak Thread Count
+          ja-JP: ピークスレッド数
        type: 0
      - field: daemon_thread_count
        i18n:
          zh-CN: 守护线程数
          en-US: Daemon Thread Count
+          ja-JP: デーモンスレッド数
        type: 0
    aliasFields:
      - $.beans[?(@.name == 'java.lang:type=Threading')].ThreadCount
@@ -283,30 +311,35 @@ metrics:
    i18n:
      zh-CN: 代码缓存
      en-US: Code Cache
+      ja-JP: コードキャッシュ
    priority: 4
    fields:
      - field: committed
        i18n:
          zh-CN: 已提交
          en-US: Committed
+          ja-JP: コミット
        type: 1
        unit: MB
      - field: init
        i18n:
          zh-CN: 初始化
          en-US: Init
+          ja-JP: イニシャル
        type: 0
        unit: MB
      - field: max
        i18n:
          zh-CN: 最大
          en-US: Max
+          ja-JP: 最大
        type: 0
        unit: MB
      - field: used
        i18n:
          zh-CN: 已使用
          en-US: Used
+          ja-JP: 使用済み
        type: 0
        unit: MB
    aliasFields:
@@ -14,51 +14,44 @@
 # 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: bigdata
 # The monitoring type eg: linux windows tomcat mysql aws...
-# 监控类型 eg: linux windows tomcat mysql aws...
 app: influxdb
 # The monitoring i18n name
-# 监控类型国际化名称
 name:
  zh-CN: InfluxDB
  en-US: InfluxDB
+  ja-JP: InfluxDB
 # The description and help of this monitoring type
-# 监控类型的帮助描述信息
 help:
  zh-CN: HertzBeat 对 InfluxDB 时序数据库进行监控。<br><span class='help_module_span'><a class='help_module_content' href='https://docs.influxdata.com/platform/monitoring/influxdata-platform/tools/measurements-internal'>点击查看开启步骤</a>。</span>
  en-US: HertzBeat monitors the InfluxDB time series database. <br><span class='help_module_span'><a class='help_module_content' href='https://docs.influxdata.com/platform/monitoring/influxdata-platform/tools/measurements-internal '>Click to view the activation steps</a>. </span>
  zh-TW: HertzBeat 對 InfluxDB 時序資料庫進行監控。<br><span class='help_module_span'><a class='help_module_content' href='https://docs.influxdata.com/platform/monitoring/influxdata-platform/tools/measurements-internal'>點擊查看開啓步驟</a>。</span>
+  ja-JP: HertzBeat は InfluxDB 時系列データベースを監視します。<br><span class='help_module_span'><a class='help_module_content' href='https://docs.influxdata.com/platform/monitoring/influxdata-platform/tools/measurements-internal'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.com/zh-cn/docs/help/influxdb/
  en-US: https://hertzbeat.com/docs/help/influxdb/
-# 监控所需输入参数定义(根据定义渲染页面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: port
    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]'
    # default value
    defaultValue: 8086
@@ -67,45 +60,48 @@ params:
    name:
      zh-CN: 查询超时时间
      en-US: Query Timeout
+      ja-JP: クエリタイムアウト
    type: number
    required: false
    # hide param-true or false
-    # 是否隐藏字段 true or false
    hide: true
    defaultValue: 6000

 # collect metrics config list
-# 采集指标配置列表
 metrics:
  # metrics - cluster_node_status
-  # 监控指标 - cluster_node_status

  - name: influxdb_info
    i18n:
      zh-CN: influxdb 基本信息
      en-US: influxdb_info
+      ja-JP: influxdb基礎情報
    priority: 0
    fields:
      - field: build_date
        i18n:
          zh-CN: 创建日期
          en-US: build_date
+          ja-JP: 作成日
        type: 1
        label: true
      - field: os
        i18n:
          zh-CN: 操作系统
          en-US: os
+          ja-JP: オーエス
        type: 1
      - field: cpus
        i18n:
          zh-CN: cpus
          en-US: cpus
+          ja-JP: 使用可能のCPUコア数
        type: 1
      - field: version
        i18n:
          zh-CN: 版本
          en-US: version
+          ja-JP: バージョン
        type: 1
    aliasFields:
      - build_date
@@ -130,48 +126,50 @@ metrics:
    i18n:
      zh-CN: http 响应时间
      en-US: http_api_request_duration_seconds
+      ja-JP: http 応答時間
    # 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: 1
    # 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: handler
        i18n:
          zh-CN: handler
          en-US: handler
+          ja-JP: ハンドラ
        type: 1
      - field: path
        i18n:
          zh-CN: 路径
          en-US: path
+          ja-JP: パス
        type: 1
      - field: response_code
        i18n:
          zh-CN: 返回 code
          en-US: response_code
+          ja-JP: 応答コード
        type: 1
      - field: method
        i18n:
          zh-CN: 方法
          en-US: method
+          ja-JP: リクエストメソッド
        type: 1
      - field: user_agent
        i18n:
          zh-CN: 用户代理
          en-US: user_agent
+          ja-JP: ユーザーエージェント
        type: 1
      - field: status
        i18n:
          zh-CN: 状态
          en-US: status
+          ja-JP: ステータス
        type: 1
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
-    # (可选)监控指标别名, 做为中间字段与采集数据字段和指标字段映射转换
    aliasFields:
      - handler
      - path
@@ -180,7 +178,6 @@ metrics:
      - user_agent
      - status
    # mapping and conversion expressions, use these and aliasField above to calculate metrics value
-    # (可选)指标映射转换计算表达式,与上面的别名一起作用,计算出最终需要的指标值
    # eg: cores=core1+core2, usage=usage, waitTime=allTime-runningTime
    calculates:
      - handler=handler
@@ -203,50 +200,50 @@ metrics:
      # http method: GET POST PUT DELETE PATCH
      method: GET
      # http response data parse type: default-hertzbeat rule, jsonpath-jsonpath script, website-for website monitoring, prometheus-prometheus exporter rule
-      # http 响应数据解析方式: default-系统规则, jsonPath-jsonPath脚本, website-网站可用性指标监控, prometheus-Prometheus数据规则
      parseType: prometheus

  - name: storage_compactions_queued
    i18n:
      zh-CN: 正在排队的 TSM 数
      en-US: storage_compactions_queued
+      ja-JP: storage_compactions_queued
    # 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: 2
    # 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: bucket
        i18n:
          zh-CN: 存储桶
          en-US: bucket
+          ja-JP: バケット
        type: 1
      - field: engine
        i18n:
          zh-CN: 引擎类型
          en-US: engine
+          ja-JP: エンジン
        type: 1
      - field: id
        i18n:
          zh-CN: 标识符
          en-US: id
+          ja-JP: id
        type: 1
      - field: level
        i18n:
          zh-CN: 级别
          en-US: level
+          ja-JP: レベル
        type: 1
      - field: path
        i18n:
          zh-CN: 数据文件路径
          en-US: path
+          ja-JP: パス
        type: 1
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
-    # (可选)监控指标别名, 做为中间字段与采集数据字段和指标字段映射转换
    aliasFields:
      - bucket
      - engine
@@ -254,7 +251,6 @@ metrics:
      - level
      - path
    # mapping and conversion expressions, use these and aliasField above to calculate metrics value
-    # (可选)指标映射转换计算表达式,与上面的别名一起作用,计算出最终需要的指标值
    # eg: cores=core1+core2, usage=usage, waitTime=allTime-runningTime
    calculates:
      - bucket=bucket
@@ -276,46 +272,43 @@ metrics:
      # http method: GET POST PUT DELETE PATCH
      method: GET
      # http response data parse type: default-hertzbeat rule, jsonpath-jsonpath script, website-for website monitoring, prometheus-prometheus exporter rule
-      # http 响应数据解析方式: default-系统规则, jsonPath-jsonPath脚本, website-网站可用性指标监控, prometheus-Prometheus数据规则
      parseType: prometheus

  - name: http_write_request_bytes
    i18n:
      zh-CN: HTTP写入请求的字节数量
      en-US: http_write_request_bytes
+      ja-JP: http書き込みリクエストのバイト
    # 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: 3
    # 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: endpoint
        i18n:
          zh-CN: 终点
          en-US: endpoint
+          ja-JP: エンドポイント
        type: 1
      - field: org_id
        i18n:
          zh-CN: 组织标识符
          en-US: org_id
+          ja-JP: org_id
        type: 1
      - field: status
        i18n:
          zh-CN: 状态
          en-US: status
+          ja-JP: ステータス
        type: 1
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
-    # (可选)监控指标别名, 做为中间字段与采集数据字段和指标字段映射转换
    aliasFields:
      - endpoint
      - org_id
      - status
    # mapping and conversion expressions, use these and aliasField above to calculate metrics value
-    # (可选)指标映射转换计算表达式,与上面的别名一起作用,计算出最终需要的指标值
    # eg: cores=core1+core2, usage=usage, waitTime=allTime-runningTime
    calculates:
      - endpoint=endpoint
@@ -335,40 +328,36 @@ metrics:
      # http method: GET POST PUT DELETE PATCH
      method: GET
      # http response data parse type: default-hertzbeat rule, jsonpath-jsonpath script, website-for website monitoring, prometheus-prometheus exporter rule
-      # http 响应数据解析方式: default-系统规则, jsonPath-jsonPath脚本, website-网站可用性指标监控, prometheus-Prometheus数据规则
      parseType: prometheus

  - name: qc_requests_total
    i18n:
      zh-CN: 质量控制请求总数
      en-US: qc_requests_total
+      ja-JP: qcリクエスト
    # 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: 3
    # 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: result
        i18n:
          zh-CN: 结果
          en-US: result
+          ja-JP: 結果
        type: 1
      - field: org
        i18n:
          zh-CN: 组织标识符
          en-US: org
+          ja-JP: org
        type: 1
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
-    # (可选)监控指标别名, 做为中间字段与采集数据字段和指标字段映射转换
    aliasFields:
      - result
      - org
    # mapping and conversion expressions, use these and aliasField above to calculate metrics value
-    # (可选)指标映射转换计算表达式,与上面的别名一起作用,计算出最终需要的指标值
    # eg: cores=core1+core2, usage=usage, waitTime=allTime-runningTime
    calculates:
      - result=result
@@ -387,7 +376,6 @@ metrics:
      # http method: GET POST PUT DELETE PATCH
      method: GET
      # http response data parse type: default-hertzbeat rule, jsonpath-jsonpath script, website-for website monitoring, prometheus-prometheus exporter rule
-      # http 响应数据解析方式: default-系统规则, jsonPath-jsonPath脚本, website-网站可用性指标监控, prometheus-Prometheus数据规则
      parseType: prometheus


@@ -20,11 +20,13 @@ app: influxdb_promql
 name:
  zh-CN: InfluxDB-PromQL
  en-US: InfluxDB-PromQL
+  ja-JP: InfluxDB-PromQL
 # The description and help of this monitoring type
 help:
  zh-CN: Hertzbeat 使用 Prometheus PromQL 从 Prometheus 服务器中查询到 InfluxDB 的通用指标数据来进行监控。此方案适用于 Prometheus 已监控 InfluxDB，需要从 Prometheus 服务器抓取 InfluxDB 的监控数据。<br>您可以点击 “<i>新建 InfluxDB-PromQL</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: HertzBeat uses Prometheus PromQL query metrics data from Prometheus Server to monitoring InfluxDB. This solution is suitable for Prometheus to monitor InfluxDB, and it need to capture InfluxDB monitoring data from the Prometheus server. <br>You could click the "<i>New InfluxDB-PromQL</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 使用 Prometheus PromQL 從 Prometheus 服務器中查詢到 InfluxDB 的通用指標數據來進行監控。此方案適用于 Prometheus 已監控 InfluxDB，需要從 Prometheus 服務器抓取 InfluxDB 的監控數據。<br>您可以點擊 “<i>新建 InfluxDB-PromQL</i>” 並進行配置，或者選擇“<i>更多操作</i>”，導入已有配置。
+  ja-JP: Hertzbeat は Prometheus PromQL を介して Prometheus サーバーに InfluxDB の一般的なパフォーマンスのメトリクスをクエリして監視します。このシナリオは、PrometheusがすでにInfluxDBを監視しており、PrometheusサーバーからInfluxDBの監視データを取得する必要がある場合に適用されます。。<br>「<i>新規 InfluxDB-PromQL</i>」をクリックして設定しましょう。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/influxdb_promql
  en-US: https://hertzbeat.apache.org/docs/help/influxdb_promql
@@ -33,12 +35,14 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    type: host
    required: true
  - field: port
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    type: number
    range: '[0,65535]'
    required: true
@@ -47,6 +51,7 @@ params:
    name:
      zh-CN: 请求方式
      en-US: Method
+      ja-JP: リクエストメソッド
    type: radio
    required: true
    options:
@@ -63,6 +68,7 @@ params:
    name:
      zh-CN: 相对路径
      en-US: URI
+      ja-JP: URI
    type: text
    limit: 200
    required: true
@@ -72,12 +78,14 @@ params:
    name:
      zh-CN: 启动SSL
      en-US: SSL
+      ja-JP: SSL
    type: boolean
    required: false
  - field: headers
    name:
      zh-CN: 请求Headers
      en-US: Headers
+      ja-JP: ヘッダ
    type: key-value
    required: false
    keyAlias: Header Name
@@ -86,6 +94,7 @@ params:
    name:
      zh-CN: 查询Params
      en-US: Params
+      ja-JP: パラメータ
    type: key-value
    required: false
    keyAlias: Param Key
@@ -94,6 +103,7 @@ params:
    name:
      zh-CN: Content-Type
      en-US: Content-Type
+      ja-JP: コンテンツタイプ
    type: text
    placeholder: '请求BODY资源类型'
    required: false
@@ -102,6 +112,7 @@ params:
    name:
      zh-CN: 请求BODY
      en-US: BODY
+      ja-JP: ボディ
    type: textarea
    placeholder: 'POST PUT请求时有效'
    required: false
@@ -110,6 +121,7 @@ params:
    name:
      zh-CN: 认证方式
      en-US: Auth Type
+      ja-JP: 認証方法
    type: radio
    required: false
    hide: true
@@ -122,6 +134,7 @@ params:
    name:
      zh-CN: 用户名
      en-US: Username
+      ja-JP: ユーザー名
    type: text
    limit: 50
    required: false
@@ -130,6 +143,7 @@ params:
    name:
      zh-CN: 密码
      en-US: Password
+      ja-JP: パスワード
    type: password
    required: false
    hide: true
@@ -141,6 +155,7 @@ metrics:
    i18n:
      zh-CN: InfluxDB内存分配
      en-US: InfluxDB Memory Allocation
+      ja-JP: InfluxDBメモリの割り当て
    # metrics scheduling priority(0->127), 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
@@ -152,16 +167,19 @@ metrics:
        i18n:
          zh-CN: 实例
          en-US: Instance
+          ja-JP: インスタンス
      - field: timestamp
        type: 1
        i18n:
          zh-CN: 时间戳
          en-US: Timestamp
+          ja-JP: タイムスタンプ
      - field: value
        type: 1
        i18n:
          zh-CN: 值
          en-US: Value
+          ja-JP: 値
 # Monitoring protocol used for data collection, e.g. sql, ssh, http, telnet, wmi, snmp, sdk.
    protocol: http
 # When the protocol is HTTP, the specific collection configuration is as follows
@@ -200,6 +218,7 @@ metrics:
    i18n:
      zh-CN: InfluxDB数据库测量值
      en-US: InfluxDB Database Measurements
+      ja-JP: InfluxDBデータベース測定
    # 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
@@ -211,26 +230,31 @@ metrics:
        i18n:
          zh-CN: 任务
          en-US: Job
+          ja-JP: タスク
      - field: instance
        type: 1
        i18n:
          zh-CN: 实例
          en-US: Instance
+          ja-JP: インスタンス
      - field: database
        type: 1
        i18n:
          zh-CN: 数据库
          en-US: Database
+          ja-JP: データベース
      - field: timestamp
        type: 1
        i18n:
          zh-CN: 时间戳
          en-US: Timestamp
+          ja-JP: タイムスタンプ
      - field: value
        type: 1
        i18n:
          zh-CN: 值
          en-US: Value
+          ja-JP: 値
    # Monitoring protocol used for data collection, e.g. sql, ssh, http, telnet, wmi, snmp, sdk.
    protocol: http
    # When the protocol is HTTP, the specific collection configuration is as follows
@@ -269,6 +293,7 @@ metrics:
    i18n:
      zh-CN: 每秒查询速率
      en-US: Query Rate Per Second
+      ja-JP: QPS
    # metrics scheduling priority(0->127), 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
@@ -280,16 +305,19 @@ metrics:
        i18n:
          zh-CN: 实例
          en-US: Instance
+          ja-JP: インスタンス
      - field: timestamp
        type: 1
        i18n:
          zh-CN: 时间戳
          en-US: Timestamp
+          ja-JP: タイムスタンプ
      - field: value
        type: 1
        i18n:
          zh-CN: 值
          en-US: Value
+          ja-JP: 値
    # Monitoring protocol used for data collection, e.g. sql, ssh, http, telnet, wmi, snmp, sdk.
    protocol: http
    # When the protocol is HTTP, the specific collection configuration is as follows
@@ -329,6 +357,7 @@ metrics:
    i18n:
      zh-CN: 查询执行器每10秒查询完成数
      en-US: Query Executor Queries Finished Every 10 Seconds
+      ja-JP: クエリ実行10秒あたりのクエリ完了数
    # metrics scheduling priority(0->127), 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
@@ -340,16 +369,19 @@ metrics:
        i18n:
          zh-CN: 实例
          en-US: Instance
+          ja-JP: インスタンス
      - field: timestamp
        type: 1
        i18n:
          zh-CN: 时间戳
          en-US: Timestamp
+          ja-JP: タイムスタンプ
      - field: value
        type: 1
        i18n:
          zh-CN: 值
          en-US: Value
+          ja-JP: 値
    # Monitoring protocol used for data collection, e.g. sql, ssh, http, telnet, wmi, snmp, sdk.
    protocol: http
    # When the protocol is HTTP, the specific collection configuration is as follows
@@ -21,11 +21,13 @@ app: iotdb
 name:
  zh-CN: Apache IoTDB
  en-US: Apache IoTDB
+  ja-JP: Apache IoTDB
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 对 Apache IoTDB JVM相关的物联网时序数据库的运行状态，内存任务集群等相关指标(cluster node status、jvm memory committed bytes、jvm memory used bytes、jvm threads states threads、quantity、cache hit、queue、hrift connections) 进行监控。<br><span class='help_module_span'>⚠️注意：您需要在 IoTDB 开启 prometheus exporter metrics 接口，<a class='help_module_content' href='https://iotdb.apache.org/zh/UserGuide/V0.13.x/Maintenance-Tools/Metric-Tool.html'>点击查看开启步骤</a>。</span>
  en-US: HertzBeat monitoring the Apache IoTDB metrics such as operational status, memory, task, clusters, jvm etc. <br><span class='help_module_span'>⚠️Note:You should enable the prometheus metrics api in IoTDB. <a class='help_module_content' href='https://iotdb.apache.org/UserGuide/V0.13.x/Maintenance-Tools/Metric-Tool.html'>Click here to view the specific steps.</a></span>"
  zh-TW: HertzBeat 對 Apache IoTDB JVM相關的物聯網時序數據庫的運行狀態，內存任務集群等相關指標(cluster node status、jvm memory committed bytes、jvm memory used bytes、jvm threads states threads、quantity、cache hit、queue、hrift connections) 進行監控。<br><span class='help_module_span'>⚠️注意：您需要在 IoTDB 開啓 prometheus exporter metrics 接口，<a class='help_module_content' href='https://iotdb.apache.org/zh/UserGuide/V0.13.x/Maintenance-Tools/Metric-Tool.html'>點擊查看開啓步驟</a>。</span>
+  ja-JP: HertzBeat は Apache IoTDB Java仮想マシンについてのIoT時系列データベースを監視します。<br><span class='help_module_span'>⚠️注意：IoTDB で prometheus exporter metricsを有効にする必要があります。<a class='help_module_content' href='https://iotdb.apache.org/UserGuide/V0.13.x/Maintenance-Tools/Metric-Tool.html'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/iotdb/
  en-US: https://hertzbeat.apache.org/docs/help/iotdb/
@@ -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
@@ -45,6 +48,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
@@ -56,6 +60,7 @@ params:
    name:
      zh-CN: 查询超时时间
      en-US: Query Timeout
+      ja-JP: クエリタイムアウト
    type: number
    required: false
    # hide param-true or false
@@ -69,6 +74,7 @@ metrics:
    i18n:
      zh-CN: 集群节点状态
      en-US: Cluster Node Status
+      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
@@ -79,12 +85,14 @@ metrics:
        i18n:
          zh-CN: 名称
          en-US: name
+          ja-JP: 名前
        type: 1
        label: true
      - field: status
        i18n:
          zh-CN: 状态
          en-US: status
+          ja-JP: ステータス
        type: 0
    # (optional)metrics field alias name, it is used as an alias field to map and convert the collected data and metrics field
    aliasFields:
@@ -115,23 +123,27 @@ metrics:
    i18n:
      zh-CN: JVM内存已提交
      en-US: JVM memory committed bytes
+      ja-JP: Java仮想マシンコミットされたメモリのバイト
    priority: 1
    fields:
      - field: area
        i18n:
          zh-CN: 区域
          en-US: Area
+          ja-JP: エリア
        type: 1
      - field: id
        i18n:
          zh-CN: 内存块Id
          en-US: Memory Block Id
+          ja-JP: メモリブロックId
        type: 1
        label: true
      - field: value
        i18n:
          zh-CN: JVM请求内存大小(当前)
          en-US: JVM requests memory size (current)
+          ja-JP: Java仮想マシンが要求するメモリのサイズ
        type: 0
        unit: MB
    units:
@@ -149,23 +161,27 @@ metrics:
    i18n:
      zh-CN: JVM内存已使用
      en-US: JVM memory used bytes
+      ja-JP: Java仮想マシン使用したメモリのバイト
    priority: 2
    fields:
      - field: area
        i18n:
          zh-CN: 区域
          en-US: Area
+          ja-JP: エリア
        type: 1
      - field: id
        i18n:
          zh-CN: 内存块Id
          en-US: Memory Block Id
+          ja-JP: メモリブロックId
        type: 1
        label: true
      - field: value
        i18n:
          zh-CN: JVM已使用内存大小
          en-US: JVM used memory size
+          ja-JP: Java仮想マシン使用したメモリのサイズ
        type: 0
        unit: MB
    units:
@@ -183,18 +199,21 @@ metrics:
    i18n:
      zh-CN: JVM线程状态
      en-US: JVM thread state
+      ja-JP: Java仮想マシンスレッド状態
    priority: 3
    fields:
      - field: state
        i18n:
          zh-CN: 线程状态
          en-US: thread state
+          ja-JP: スレッド状態
        type: 1
        label: true
      - field: count
        i18n:
          zh-CN: 线程数量
          en-US: thread count
+          ja-JP: スレッド総数
        type: 0
    aliasFields:
      - state
@@ -214,28 +233,33 @@ metrics:
    i18n:
      zh-CN: 数量
      en-US: Quantity
+      ja-JP: 数量
    priority: 4
    fields:
      - field: id
        i18n:
          zh-CN: Id
          en-US: Id
+          ja-JP: Id
        type: 1
        label: true
      - field: name
        i18n:
          zh-CN: 名称
          en-US: Name
+          ja-JP: 名前
        type: 1
      - field: type
        i18n:
          zh-CN: 类型
          en-US: Type
+          ja-JP: タイプ
        type: 1
      - field: value
        i18n:
          zh-CN: 值
          en-US: Value
+          ja-JP: 値
        type: 0
    aliasFields:
      - name
@@ -256,18 +280,21 @@ metrics:
    i18n:
      zh-CN: 缓存命中率
      en-US: Cache hit rate
+      ja-JP: キャッシュ命中率
    priority: 5
    fields:
      - field: name
        i18n:
          zh-CN: 名称
          en-US: Name
+          ja-JP: 名前
        type: 1
        label: true
      - field: value
        i18n:
          zh-CN: 命中率
          en-US: Hit rate
+          ja-JP: 命中率
        type: 0
    protocol: http
    http:
@@ -282,28 +309,33 @@ metrics:
    i18n:
      zh-CN: 队列
      en-US: Queue
+      ja-JP: キュー
    priority: 6
    fields:
      - field: id
        i18n:
          zh-CN: ID
          en-US: ID
+          ja-JP: ID
        type: 1
        label: true
      - field: name
        i18n:
          zh-CN: 队列名称
          en-US: Queue name
+          ja-JP: キュー名
        type: 1
      - field: status
        i18n:
          zh-CN: 状态
          en-US: Status
+          ja-JP: ステータス
        type: 1
      - field: value
        i18n:
          zh-CN: 当前队列任务数量
          en-US: Number of tasks in queue
+          ja-JP: キューのタスク数
        type: 0
    aliasFields:
      - name
@@ -324,18 +356,21 @@ metrics:
    i18n:
      zh-CN: Thrift连接数
      en-US: Thrift connection number
+      ja-JP: Thrift接続数
    priority: 7
    fields:
      - field: name
        i18n:
          zh-CN: 连接名称
          en-US: Connection name
+          ja-JP: 接続名
        type: 1
        label: true
      - field: connection
        i18n:
          zh-CN: 连接数
          en-US: Connection number
+          ja-JP: 接続数
        type: 0
    aliasFields:
      - name
@@ -14,161 +14,146 @@
 # 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: ipmi
 # The monitoring i18n name
-# 监控类型国际化名称
 name:
  zh-CN: IPMI
  en-US: IPMI
+  ja-JP: IPMI
 # The description and help of this monitoring type
-# 监控类型的帮助描述信息
 help:
  zh-CN: Hertzbeat 对支持 IPMI 服务的服务器进行测量监控。<br>您可以点击 “<i>新建 IPMI</i>” 并进行配置，或者选择“<i>更多操作</i>”，导入已有配置。
  en-US: Hertzbeat monitoring servers supporting IPMI services. You could click the "<i>New IPMI</i>" button and proceed with the configuration or import an existing setup through the "<i>More Actions</i>" menu.
  zh-TW: Hertzbeat 對支援 IPMI 服務的伺服器進行測量監控。<br>您可以點擊“<i>IPMI</i>”並進行配寘，或者選擇“<i>更多操作</i>”，導入已有配寘。
+  ja-JP: Hertzbeat はIPMIサービスをサポートするサーバを監視します。<br>「<i>新規 IPMI</i>」をクリックしてパラメタを設定した後、新規することができます。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/ipmi
  en-US: https://hertzbeat.apache.org/docs/help/ipmi
-# 监控所需输入参数定义(根据定义渲染页面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: 623
  # 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: system_power
        type: 1
        i18n:
          zh-CN: 系统电源状态
          en-US: System Power
+          ja-JP: システム電源
      - field: power_overload
        type: 1
        i18n:
          zh-CN: 电源过载
          en-US: Power Overload
+          ja-JP: オーバーロード
      - field: power_interlock
        type: 1
        i18n:
          zh-CN: 电源互锁
          en-US: Power Interlock
+          ja-JP: インターロック
      - field: power_fault
        type: 1
        i18n:
          zh-CN: 主电源故障
          en-US: Main Power Fault
+          ja-JP: 主電源故障
      - field: power_control_fault
        type: 1
        i18n:
          zh-CN: 电源控制故障
          en-US: Power Control Fault
+          ja-JP: 電源制御故障
      - field: power_restore_policy
        type: 1
        i18n:
          zh-CN: 电源恢复策略
          en-US: Power Restore Policy
+          ja-JP: 電源復旧ポリシー
      - field: last_power_event
        type: 1
        i18n:
          zh-CN: 最后一次电源事件
          en-US: Last Power Event
+          ja-JP: 最後の電源イベント
      - field: fan_fault
        type: 1
        i18n:
          zh-CN: 风扇故障
          en-US: Cooling/Fan Fault
+          ja-JP: ファン故障
      - field: drive_fault
        type: 1
        i18n:
          zh-CN: 硬盘故障
          en-US: Drive Fault
+          ja-JP: ドライブ故障
      - field: front_panel_lockout_active
        type: 1
        i18n:
          zh-CN: 前面板锁定
          en-US: Front-Panel Lockout
+          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: ipmi
    # the config content when protocol is ipmi
@@ -186,36 +171,35 @@ metrics:
  - name: Sensor
    # 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: 1
    # 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: sensor_id
        type: 1
        i18n:
          zh-CN: 传感器标识
          en-US: Sensor ID
+          ja-JP: センサーID
      - field: entity_id
        type: 1
        i18n:
          zh-CN: 实体标识
          en-US: Entity ID
+          ja-JP: エンティティID
      - field: sensor_type
        type: 1
        i18n:
          zh-CN: 传感器类型
          en-US: Sensor Type
+          ja-JP: センサータイプ
      - field: sensor_reading
        type: 1
        i18n:
          zh-CN: 传感器读数
          en-US: Sensor Reading
+          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: ipmi
    # the config content when protocol is ipmi
@@ -21,11 +21,13 @@ app: jetty
 name:
  zh-CN: Jetty应用服务器
  en-US: Jetty AppServer
+  ja-JP: Jetty応用サーバー
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/advanced/extend-jmx'>JMX 协议</a> 对 Jetty 应用服务器的通用性能指标（内存信息，类加载，线程状态，JVM等）进行采集监控。<br><span class='help_module_span'>注意⚠️：您需要在 Jetty 应用开启 JMX 服务, <a class='help_module_content' href='https://eclipse.dev/jetty/documentation/jetty-10/operations-guide/index.html#og-jmx-remote'>点击查看开启步骤</a>。</span>
-  en-US: HertzBeat monitoring general performance metrics(memory pool, class loading, thread, jvm etc) of Jetty application server through <a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/advanced/extend-jmx'>JMX protocol</a>. <br><span class='help_module_span'>Note⚠️:You should enable the JMX service in Jetty application. <a class='help_module_content' href='https://eclipse.dev/jetty/documentation/jetty-10/operations-guide/index.html#og-jmx-remote'>Click here to view the specific steps.</a></span>
+  en-US: HertzBeat monitoring general performance metrics(memory pool, class loading, thread, jvm etc) of Jetty application server through <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'>JMX protocol</a>. <br><span class='help_module_span'>Note⚠️:You should enable the JMX service in Jetty application. <a class='help_module_content' href='https://eclipse.dev/jetty/documentation/jetty-10/operations-guide/index.html#og-jmx-remote'>Click here to view the specific steps.</a></span>
  zh-TW: HertzBeat 使用 <a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/advanced/extend-jmx'>JMX 協議</a> 對 Jetty 應用服務器的通用性能指標（內存信息，類加載，線程狀態，JVM等）進行采集監控。<br><span class='help_module_span'>注意⚠️：您需要在 Jetty 應用開啓 JMX 服務, <a class='help_module_content' href='https://eclipse.dev/jetty/documentation/jetty-10/operations-guide/index.html#og-jmx-remote'>點擊查看開啓步驟</a>。</span>
+  ja-JP: HertzBeatは <a class='help_module_content' href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMXプロトコルを介して</a> Jetty応用サーバーの一般的なパフォーマンスのメトリクスを監視します。<br><span class='help_module_span'> ⚠️注意：Jetty応用 で JMX サービスを有効にする必要があります。<a class='help_module_content' href='https://eclipse.dev/jetty/documentation/jetty-10/operations-guide/index.html#og-jmx-remote'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/jetty/
  en-US: https://hertzbeat.apache.org/docs/help/jetty/
@@ -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: JMX端口
      en-US: JMX Port
+      ja-JP: JMXポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -61,6 +65,7 @@ params:
    name:
      zh-CN: JMX URL
      en-US: JMX URL
+      ja-JP: JMX URL
    # type-param field type(most mapping the html input type)
    type: text
    # required-true or false
@@ -75,6 +80,7 @@ params:
    name:
      zh-CN: 用户名
      en-US: Username
+      ja-JP: ユーザー名
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -89,6 +95,7 @@ params:
    name:
      zh-CN: 密码
      en-US: Password
+      ja-JP: パスワード
    # type-param field type(most mapping the html input type)
    type: password
    # required-true or false
@@ -102,6 +109,7 @@ metrics:
    i18n:
      zh-CN: 虚拟机基础信息
      en-US: JVM Basic
+      ja-JP: Java仮想マシン基礎情報
    # metrics scheduling priority(0->127)->(high->low), metrics with the same priority will be scheduled in parallel
    # priority 0's metrics is availability metrics, it will be scheduled first, only availability metrics collect success will the scheduling continue
    priority: 0
@@ -113,22 +121,26 @@ metrics:
        i18n:
          zh-CN: 名称
          en-US: Vm Name
+          ja-JP: 仮想マシン名
      - field: VmVendor
        type: 1
        i18n:
          zh-CN: 厂商
          en-US: Vm Vendor
+          ja-JP: 仮想マシンベンダー
      - field: VmVersion
        type: 1
        i18n:
          zh-CN: 版本
          en-US: Vm Version
+          ja-JP: 仮想マシンバージョン
      - field: Uptime
        type: 0
        unit: ms
        i18n:
          zh-CN: 运行时长
          en-US: Up time
+          ja-JP: アップタイム
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jmx
    # the config content when protocol is http
@@ -147,6 +159,7 @@ metrics:
    i18n:
      zh-CN: Jetty Server
      en-US: Jetty Server
+      ja-JP: Jetty サーバー
    # 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
@@ -158,16 +171,19 @@ metrics:
        i18n:
          zh-CN: 版本
          en-US: Vm Version
+          ja-JP: 仮想マシンバージョン
      - field: state
        type: 1
        i18n:
          zh-CN: 运行状态
          en-US: Run State
+          ja-JP: 実行状態
      - field: startupTime
        type: 0
        i18n:
          zh-CN: 启动时间
          en-US: Startup Time
+          ja-JP: 起動時間
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jmx
    # the config content when protocol is http
@@ -186,6 +202,7 @@ metrics:
    i18n:
      zh-CN: 内存池
      en-US: Memory Pool
+      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
@@ -198,26 +215,31 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: Name
+          ja-JP: メトリクス名
      - field: committed
        type: 0
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        i18n:
          zh-CN: 初始化内存
          en-US: Init
+          ja-JP: イニシャルメモリ
      - field: max
        type: 0
        i18n:
          zh-CN: 最大内存
          en-US: Max
+          ja-JP: 最大メモリ
      - field: used
        type: 0
        i18n:
          zh-CN: 已使用内存
          en-US: Used
+          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:
      - Name
@@ -250,6 +272,7 @@ metrics:
    i18n:
      zh-CN: 类加载信息
      en-US: Class Loading
+      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
@@ -261,16 +284,19 @@ metrics:
        i18n:
          zh-CN: 已加载类总数
          en-US: Loaded Class Count
+          ja-JP: ロードされたクラス数
      - field: TotalLoadedClassCount
        type: 0
        i18n:
          zh-CN: 总加载类总数
          en-US: Total Loaded Class Count
+          ja-JP: ロードされたクラス総数
      - field: UnloadedClassCount
        type: 0
        i18n:
          zh-CN: 未加载类总数
          en-US: Unloaded Class Count
+          ja-JP: アンロードされたクラス総数
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jmx
    # the config content when protocol is http
@@ -288,6 +314,7 @@ metrics:
    i18n:
      zh-CN: 线程信息
      en-US: Thread
+      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
@@ -299,33 +326,39 @@ metrics:
        i18n:
          zh-CN: 已启动线程总数
          en-US: Total Started Thread Count
+          ja-JP: スレッド総数
      - field: ThreadCount
        type: 0
        i18n:
          zh-CN: 活跃线程数
          en-US: Thread Count
+          ja-JP: 活躍スレッド数
      - field: PeakThreadCount
        type: 0
        i18n:
          zh-CN: 最大峰值线程数
          en-US: Peak Thread Count
+          ja-JP: 最大スレッド数
      - field: DaemonThreadCount
        type: 0
        i18n:
          zh-CN: 活跃守护线程数
          en-US: Daemon Thread Count
+          ja-JP: デーモンスレッド数
      - field: CurrentThreadUserTime
        type: 0
        unit: s
        i18n:
          zh-CN: 线程占用的CPU时间(用户态)
          en-US: Current Thread User Time
+          ja-JP: 現在のスレッドユーザー時間
      - field: CurrentThreadCpuTime
        type: 0
        unit: s
        i18n:
          zh-CN: 线程占用的CPU时间
          en-US: Current Thread CPU Time
+          ja-JP: 現在のスレッドシステム時間
    units:
      - CurrentThreadUserTime=NS->S
      - CurrentThreadCpuTime=NS->S
@@ -346,6 +379,7 @@ metrics:
    i18n:
      zh-CN: Web应用
      en-US: Webapp
+      ja-JP: Web応用
    # 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
@@ -358,26 +392,31 @@ metrics:
        i18n:
          zh-CN: 应用名称
          en-US: App Name
+          ja-JP: 応用名
      - field: contextPath
        type: 1
        i18n:
          zh-CN: 上下文路径
          en-US: Context Path
+          ja-JP: コンテキストパス
      - field: state
        type: 1
        i18n:
          zh-CN: 状态
          en-US: State
+          ja-JP: 状態
      - field: resourceBase
        type: 1
        i18n:
          zh-CN: 资源
          en-US: Resource Base
+          ja-JP: リソース
      - field: shutdown
        type : 1
        i18n:
          zh-CN: 是否关闭
          en-US: Shutdown
+          ja-JP: シャットダウン
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jmx
    # the config content when protocol is http
@@ -21,11 +21,13 @@ app: jvm
 name:
  zh-CN: JVM虚拟机
  en-US: JVM
+  ja-JP: Java仮想マシン
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 使用 <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx">JMX 协议</a> 对 JVM 虚拟机的通用性能指标(基础信息，内存池，类加载，线程信息等)进行采集监控。<br>⚠️注意：您需要在 JVM 应用中开启 JMX 服务，应用启动时添加 JMX 参数, 可自定义暴露端口,对外IP。<a href="https://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote">点击查看开启步骤</a>。
  en-US: HertzBeat uses <a href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'>JMX Protocol</a> to monitoring and collect general performance metric of jvm application. <br>⚠️Note:You need to enable JMX services in JVM application, and add the JXM parameters when the application start. You can also customize external IP address and exposed port.<a href='https://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote'>Click here to view the activation steps.</a>"
  zh-TW: HertzBeat 使用 <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx">JMX 協議</a> 對 JVM 虛擬機的通用性能指標(基礎信息，內存池，類加載，線程信息等)進行采集監控。<br>⚠️注意：您需要在 JVM 應用中開啓 JMX 服務，應用啓動時添加 JMX 參數, 可自定義暴露端口,對外IP。<a href="https://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote">點擊查看開啓步驟</a>。
+  ja-JP: HertzBeat は <a href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMXプロトコルを介して</a> Java仮想マシンの一般的なパフォーマンスのメトリクスを監視します。<br>⚠️注意：Java仮想マシンの応用 で JMX サービスを有効にする必要があります。<a href='https://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote'>クリックしてガイドを見ます</a>。
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/jvm/
  en-US: https://hertzbeat.apache.org/docs/help/jvm/
@@ -37,6 +39,7 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    # type-param field type(most mapping the html input type)
    type: host
    # required-true or false
@@ -47,6 +50,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    # type-param field type(most mapping the html input type)
    type: number
    # when type is number, range is required
@@ -61,6 +65,7 @@ params:
    name:
      zh-CN: JMX URL
      en-US: JMX URL
+      ja-JP: JMX URL
    # type-param field type(most mapping the html input type)
    type: text
    # required-true or false
@@ -75,6 +80,7 @@ params:
    name:
      zh-CN: 用户名
      en-US: Username
+      ja-JP: ユーザー名
    # type-param field type(most mapping the html input type)
    type: text
    # when type is text, use limit to limit string length
@@ -89,6 +95,7 @@ params:
    name:
      zh-CN: 密码
      en-US: Password
+      ja-JP: パスワード
    # type-param field type(most mapping the html input tag)
    type: password
    # required-true or false
@@ -105,6 +112,7 @@ metrics:
    i18n:
      zh-CN: 虚拟机基础信息
      en-US: JVM Basic
+      ja-JP: Java仮想マシン基礎情報
    # 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
@@ -113,22 +121,26 @@ metrics:
        i18n:
          zh-CN: 名称
          en-US: Vm Name
+          ja-JP: 仮想マシン名
      - field: VmVendor
        type: 1
        i18n:
          zh-CN: 厂商
          en-US: Vm Vendor
+          ja-JP: 仮想マシンベンダー
      - field: VmVersion
        type: 1
        i18n:
          zh-CN: 版本
          en-US: Vm Version
+          ja-JP: 仮想マシンバージョン
      - field: Uptime
        type: 0
        unit: ms
        i18n:
          zh-CN: 运行时长
          en-US: Up time
+          ja-JP: アップタイム
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jmx
    # the config content when protocol is jmx
@@ -148,6 +160,7 @@ metrics:
    i18n:
      zh-CN: 内存池
      en-US: Memory Pool
+      ja-JP: メモリプール
    fields:
      - field: name
        type: 1
@@ -155,30 +168,35 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: Name
+          ja-JP: メトリクス名
      - field: committed
        type: 0
        unit: MB
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        unit: MB
        i18n:
          zh-CN: 初始化内存
          en-US: Init
+          ja-JP: イニシャルメモリ
      - field: max
        type: 0
        unit: MB
        i18n:
          zh-CN: 最大内存
          en-US: Max
+          ja-JP: 最大メモリ
      - field: used
        type: 0
        unit: MB
        i18n:
          zh-CN: 已使用内存
          en-US: Used
+          ja-JP: 使用したメモリ
    units:
      - committed=B->MB
      - init=B->MB
@@ -215,27 +233,32 @@ metrics:
    i18n:
      zh-CN: 本地代码缓冲区
      en-US: Code Cache
+      ja-JP: コードキャッシュ
    fields:
      - field: committed
        type: 0
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        i18n:
          zh-CN: 初始化内存
          en-US: Init
+          ja-JP: イニシャルメモリ
      - field: max
        type: 0
        i18n:
          zh-CN: 最大内存
          en-US: Max
+          ja-JP: 最大メモリ
      - field: used
        type: 0
        i18n:
          zh-CN: 已使用内存
          en-US: Used
+          ja-JP: 使用したメモリ
    aliasFields:
      - Usage->committed
      - Usage->init
@@ -262,6 +285,7 @@ metrics:
    i18n:
      zh-CN: 类加载信息
      en-US: Class Loading
+      ja-JP: クラスローディング情報
    # collect metrics content
    fields:
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
@@ -270,16 +294,19 @@ metrics:
        i18n:
          zh-CN: 当前已加载类数量
          en-US: Loaded Class Count
+          ja-JP: ロードされたクラス数
      - field: TotalLoadedClassCount
        type: 0
        i18n:
          zh-CN: 已加载类总数量
          en-US: Total Loaded Class Count
+          ja-JP: ロードされたクラス総数
      - field: UnloadedClassCount
        type: 0
        i18n:
          zh-CN: 未加载类总数量
          en-US: Unloaded Class Count
+          ja-JP: アンロードされたクラス総数
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -294,6 +321,7 @@ metrics:
    i18n:
      zh-CN: 线程信息
      en-US: Thread
+      ja-JP: スレッド情報
    # collect metrics content
    fields:
      # field-metric name, type-metric type(0-number,1-string), unit-metric unit('%','ms','MB'), label-whether it is a metrics label field
@@ -302,33 +330,39 @@ metrics:
        i18n:
          zh-CN: 已启动线程总数
          en-US: Total Started Thread Count
+          ja-JP: スレッド総数
      - field: ThreadCount
        type: 0
        i18n:
          zh-CN: 活跃线程数
          en-US: Thread Count
+          ja-JP: 活躍スレッド数
      - field: PeakThreadCount
        type: 0
        i18n:
          zh-CN: 最大峰值线程数
          en-US: Peak Thread Count
+          ja-JP: 最大スレッド数
      - field: DaemonThreadCount
        type: 0
        i18n:
          zh-CN: 活跃守护线程数
          en-US: Daemon Thread Count
+          ja-JP: デーモンスレッド数
      - field: CurrentThreadUserTime
        type: 0
        unit: s
        i18n:
          zh-CN: 线程占用的CPU时间(用户态)
          en-US: Current Thread User Time
+          ja-JP: 現在のスレッドユーザー時間
      - field: CurrentThreadCpuTime
        type: 0
        unit: s
        i18n:
          zh-CN: 线程占用的CPU时间
          en-US: Current Thread CPU Time
+          ja-JP: 現在のスレッドシステム時間
    units:
      - CurrentThreadUserTime=NS->S
      - CurrentThreadCpuTime=NS->S
@@ -21,11 +21,13 @@ app: kafka
 name:
  zh-CN: Kafka消息系统
  en-US: Kafka Message
+  ja-JP: Kafkaメッセージングシステム
 # The description and help of this monitoring type
 help:
  zh-CN: HertzBeat 使用 <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx">JMX 协议</a> 对 Kafka 的通用性能指标 (server info、code cache、active controller count、broker partition count、broker leader count、broker handler avg percent etc) 进行采集监控。<br><span class='help_module_span'>注意⚠️：您需要在 Kafka 开启 JMX 服务，应用启动时添加 JMX 参数，暴露端口，对外IP。下方配置的端口即为JMX暴露的端口，而非Kafka的server端口。<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/kafka'>点击查看开启步骤</a>。</span>
  en-US: HertzBeat uses <a href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'>JMX Protocol</a> to monitoring kafka general performance metrics (server info、code cache、active controller count、broker partition count、broker leader count、broker handler avg percent etc). <br><span class='help_module_span'>Note⚠️:You need to enable JMX service in Kafka, export JMX port and config params.The port configured below is the JMX exposed port, not the Kafka server port. <a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/kafka'>Click here to view the specific steps.</a></span>
  zh-TW: HertzBeat 使用 <a href="https://hertzbeat.apache.org/docs/advanced/extend-jmx">JMX 協議</a> 對 Kafka 的通用性能指標 (server info、code cache、active controller count、broker partition count、broker leader count、broker handler avg percent etc) 進行采集監控。<br><span class='help_module_span'>注意⚠️：您需要在 Kafka 開啓 JMX 服務，應用啓動時添加 JMX 參數，暴露端口，對外IP。下方配置的端口即為 JMX 暴露的端口，而非 Kafka 的伺服器端口。<a class='help_module_content' href='https://hertzbeat.apache.org/zh-cn/docs/help/kafka'>點擊查看開啓步驟</a>。</span>
+  ja-JP: HertzBeat は <a href='https://hertzbeat.apache.org/docs/advanced/extend-jmx'> JMXプロトコルを介して</a> Kafkaの一般的なパフォーマンスのメトリクスを監視します。<br><span class='help_module_span'>⚠️注意：Kafka で JMX サービスを有効にする必要があります。<a class='help_module_content' href='https://hertzbeat.apache.org/docs/help/kafka'>クリックしてガイドを見ます</a>。</span>
 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/kafka
  en-US: https://hertzbeat.apache.org/docs/help/kafka
@@ -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
@@ -45,6 +48,7 @@ params:
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    type: number
    # when type is number, range is required
    range: '[0,65535]'
@@ -54,6 +58,7 @@ params:
    name:
      zh-CN: JMX URL
      en-US: JMX URL
+      ja-JP: JMX URL
    type: text
    required: false
    hide: true
@@ -62,6 +67,7 @@ params:
    name:
      zh-CN: 用户名
      en-US: Username
+      ja-JP: ユーザー名
    type: text
    limit: 50
    required: false
@@ -70,6 +76,7 @@ params:
    name:
      zh-CN: 密码
      en-US: Password
+      ja-JP: パスワード
    type: password
    required: false
    hide: true
@@ -80,6 +87,7 @@ metrics:
    i18n:
      zh-CN: 服务器信息
      en-US: Server Info
+      ja-JP: サーバー情報
    # metrics scheduling priority(0->127)->(high->low), metrics with the same priority will be scheduled in parallel
    # priority 0's metrics is availability metrics, it will be scheduled first, only availability metrics collect success will the scheduling continue
    priority: 0
@@ -91,16 +99,19 @@ metrics:
        i18n:
          zh-CN: 版本
          en-US: Version
+          ja-JP: バージョン
      - field: StartTimeMs
        type: 1
        i18n:
          zh-CN: 启动时间
          en-US: Start Time
+          ja-JP: 起動時間
      - field: CommitId
        type: 1
        i18n:
          zh-CN: CommitId
          en-US: CommitId
+          ja-JP: CommitId
    # the protocol used for monitoring, eg: sql, ssh, http, telnet, wmi, snmp, sdk
    protocol: jmx
    # the config content when protocol is jmx
@@ -118,6 +129,7 @@ metrics:
    i18n:
      zh-CN: 虚拟机基础信息
      en-US: JVM Basic
+      ja-JP: Java仮想マシン基礎情報
    priority: 1
    fields:
      - field: VmName
@@ -125,22 +137,26 @@ metrics:
        i18n:
          zh-CN: 名称
          en-US: Vm Name
+          ja-JP: 仮想マシン名
      - field: VmVendor
        type: 1
        i18n:
          zh-CN: 厂商
          en-US: Vm Vendor
+          ja-JP: 仮想マシンベンダー
      - field: VmVersion
        type: 1
        i18n:
          zh-CN: 版本
          en-US: Vm Version
+          ja-JP: 仮想マシンバージョン
      - field: Uptime
        type: 0
        unit: ms
        i18n:
          zh-CN: 运行时长
          en-US: Up time
+          ja-JP: アップタイム
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -155,6 +171,7 @@ metrics:
    i18n:
      zh-CN: 内存池
      en-US: Memory Pool
+      ja-JP: メモリプール
    priority: 2
    fields:
      - field: name
@@ -163,26 +180,31 @@ metrics:
        i18n:
          zh-CN: 指标名称
          en-US: Name
+          ja-JP: メトリクス名
      - field: committed
        type: 0
        i18n:
          zh-CN: 已分配内存
          en-US: Committed
+          ja-JP: コミットされたメモリ
      - field: init
        type: 0
        i18n:
          zh-CN: 初始化内存
          en-US: Init
+          ja-JP: イニシャルメモリ
      - field: max
        type: 0
        i18n:
          zh-CN: 最大内存
          en-US: Max
+          ja-JP: 最大メモリ
      - field: used
        type: 0
        i18n:
          zh-CN: 已使用内存
          en-US: Used
+          ja-JP: 使用したメモリ
    aliasFields:
      - Name
      - Usage->committed
@@ -208,6 +230,7 @@ metrics:
    i18n:
      zh-CN: Kafka控制器指标
      en-US: Kafka Controller Metrics
+      ja-JP: Kafkaコントローラーのメトリクス
    priority: 3
    fields:
      - field: ActiveBrokerCount
@@ -215,66 +238,79 @@ metrics:
        i18n:
          zh-CN: 活跃代理数量
          en-US: Active Broker Count
+          ja-JP: 活動中のブローカー数
      - field: ActiveControllerCount
        type: 0
        i18n:
          zh-CN: 活跃控制器数量
          en-US: Active Controller Count
+          ja-JP: 活動中のコントローラー数
      - field: ControllerState
        type: 0
        i18n:
          zh-CN: 控制器状态
          en-US: Controller State
+          ja-JP: コントローラー状態
      - field: FencedBrokerCount
        type: 0
        i18n:
          zh-CN: 被隔离代理数量
          en-US: Fenced Broker Count
+          ja-JP: フェンスのブローカー数
      - field: GlobalPartitionCount
        type: 0
        i18n:
          zh-CN: 全局分区数量
          en-US: Global Partition Count
+          ja-JP: パーティション数
      - field: GlobalTopicCount
        type: 0
        i18n:
          zh-CN: 全局主题数量
          en-US: Global Topic Count
+          ja-JP: トピック数
      - field: OfflinePartitionsCount
        type: 0
        i18n:
          zh-CN: 离线分区数量
          en-US: Offline Partitions Count
+          ja-JP: オフラインのパーティション数
      - field: PreferredReplicaImbalanceCount
        type: 0
        i18n:
          zh-CN: 首选副本不平衡数量
          en-US: Preferred Replica Imbalance Count
+          ja-JP: 優先レプリカ不均衡数
      - field: ReplicasIneligibleToDeleteCount
        type: 0
        i18n:
          zh-CN: 不能删除的副本数量
          en-US: Replicas Ineligible To Delete Count
+          ja-JP: 削除できないレプリカ数
      - field: ReplicasToDeleteCount
        type: 0
        i18n:
          zh-CN: 待删除副本数量
          en-US: Replicas To Delete Count
+          ja-JP: 削除待ちのレプリカ数
      - field: TopicsIneligibleToDeleteCount
        type: 0
        i18n:
          zh-CN: 不能删除的主题数量
          en-US: Topics Ineligible To Delete Count
+          ja-JP: 削除できないトピック数
      - field: TopicsToDeleteCount
        type: 0
        i18n:
          zh-CN: 待删除主题数量
          en-US: Topics To Delete Count
+          ja-JP: 削除待ちのトピック数
      - field: ZkMigrationState
        type: 0
        i18n:
          zh-CN: ZooKeeper迁移状态
          en-US: Zk Migration State
+          ja-JP: ZooKeeperマイグレーション状態
    aliasFields:
      - Value->ActiveBrokerCount
      - Value->ActiveControllerCount
@@ -318,6 +354,7 @@ metrics:
    i18n:
      zh-CN: Broker处理器平均百分比
      en-US: Broker Handler Avg Percent
+      ja-JP: ブローカーハンドラの平均パーセント
    priority: 6
    fields:
      - field: EventType
@@ -325,36 +362,43 @@ metrics:
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -369,6 +413,7 @@ metrics:
    i18n:
      zh-CN: Kafka副本管理器指标
      en-US: Kafka Replica Manager Metrics
+      ja-JP: Kafkaレプリカマネジャーのメトリクス
    priority: 6
    fields:
      - field: AtMinIsrPartitionCount
@@ -376,61 +421,73 @@ metrics:
        i18n:
          zh-CN: 达到最小ISR的分区数
          en-US: At Min ISR Partition Count
+          ja-JP: 最小ISRパーティション数
      - field: FailedIsrUpdatesPerSec
        type: 0
        i18n:
          zh-CN: 每秒失败ISR更新数
          en-US: Failed ISR Updates Per Sec
+          ja-JP: 1秒あたりのISR更新失敗数
      - field: IsrExpandsPerSec
        type: 0
        i18n:
          zh-CN: 每秒ISR扩展数
          en-US: ISR Expands Per Sec
+          ja-JP: 1秒あたりのISR拡張数
      - field: IsrShrinksPerSec
        type: 0
        i18n:
          zh-CN: 每秒ISR收缩数
          en-US: ISR Shrinks Per Sec
+          ja-JP: 1秒あたりのISR収縮数
      - field: LeaderCount
        type: 0
        i18n:
          zh-CN: 领导者数量
          en-US: Leader Count
+          ja-JP: リーダー数
      - field: OfflineReplicaCount
        type: 0
        i18n:
          zh-CN: 离线副本数量
          en-US: Offline Replica Count
+          ja-JP: オフラインのレプリカ数
      - field: PartitionCount
        type: 0
        i18n:
          zh-CN: 分区总数
          en-US: Partition Count
+          ja-JP: パーティション数
      - field: PartitionsWithLateTransactionsCount
        type: 0
        i18n:
          zh-CN: 含有延迟交易的分区数
          en-US: Partitions With Late Transactions Count
+          ja-JP: 遅いトランザクションのあるパーティション数
      - field: ProducerIdCount
        type: 0
        i18n:
          zh-CN: 生产者ID数量
          en-US: Producer ID Count
+          ja-JP: 生産者ID数
      - field: ReassigningPartitions
        type: 0
        i18n:
          zh-CN: 正在重新分配的分区数
          en-US: Reassigning Partitions
+          ja-JP: 再割り当てのパーティション数
      - field: UnderMinIsrPartitionCount
        type: 0
        i18n:
          zh-CN: 低于最小ISR的分区数
          en-US: Under Min ISR Partition Count
+          ja-JP: 最小ISR未満のパーティション数
      - field: UnderReplicatedPartitions
        type: 0
        i18n:
          zh-CN: 副本数低于预期的分区数量
          en-US: Under Replicated Partitions
+          ja-JP: レプリカ未満のパーティション数
    aliasFields:
      - Value->LeaderCount
      - Value->AtMinIsrPartitionCount
@@ -472,6 +529,7 @@ metrics:
    i18n:
      zh-CN: 每秒主题流入字节
      en-US: Total Bytes In Per Second
+      ja-JP: 1秒あたりのトピック合計受信されたバイト
    priority: 7
    fields:
      - field: EventType
@@ -479,36 +537,43 @@ metrics:
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -523,6 +588,7 @@ metrics:
    i18n:
      zh-CN: 各主题每秒流入字节
      en-US: Bytes In Per Topic Per Second
+      ja-JP: 各トピックの1秒あたりの受信されたバイト
    priority: 7
    fields:
      - field: topic
@@ -530,41 +596,49 @@ metrics:
        i18n:
          zh-CN: 主题名称
          en-US: Topic Name
+          ja-JP: トピック名
      - field: EventType
        type: 1
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -579,6 +653,7 @@ metrics:
    i18n:
      zh-CN: 主题每秒流出字节
      en-US: Total Bytes Out Per Second
+      ja-JP: 1秒あたりのトピック合計転送されたバイト
    priority: 8
    fields:
      - field: EventType
@@ -586,36 +661,43 @@ metrics:
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -630,6 +712,7 @@ metrics:
    i18n:
      zh-CN: 各主题每秒流出字节
      en-US: Bytes Out Per Topic Per Second
+      ja-JP: 各トピックの1秒あたりの転送されたバイト
    priority: 9
    fields:
      - field: topic
@@ -637,41 +720,49 @@ metrics:
        i18n:
          zh-CN: 主题名称
          en-US: Topic Name
+          ja-JP: トピック名
      - field: EventType
        type: 1
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -686,6 +777,7 @@ metrics:
    i18n:
      zh-CN: 每秒生产消息转换
      en-US: Produce Message Conversions PerSec
+      ja-JP: 1秒あたりのメッセージ変換数
    priority: 9
    fields:
      - field: EventType
@@ -693,36 +785,43 @@ metrics:
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -737,6 +836,7 @@ metrics:
    i18n:
      zh-CN: 每秒生产总请求数
      en-US: Produce Total Requests PerSec
+      ja-JP: 1秒あたりの合計リクエスト数
    priority: 10
    fields:
      - field: EventType
@@ -744,36 +844,43 @@ metrics:
        i18n:
          zh-CN: 事件类型
          en-US: Event Type
+          ja-JP: イベントタイプ
      - field: RateUnit
        type: 1
        i18n:
          zh-CN: 速率单位
          en-US: Rate Unit
+          ja-JP: レート単位
      - field: MeanRate
        type: 0
        i18n:
          zh-CN: 平均速率
          en-US: Mean Rate
+          ja-JP: 平均レート
      - field: OneMinuteRate
        type: 0
        i18n:
          zh-CN: 一分钟速率
          en-US: One Minute Rate
+          ja-JP: 1分間のレート
      - field: FiveMinuteRate
        type: 0
        i18n:
          zh-CN: 五分钟速率
          en-US: Five Minute Rate
+          ja-JP: 5分間のレート
      - field: FifteenMinuteRate
        type: 0
        i18n:
          zh-CN: 十五分钟速率
          en-US: Fifteen Minute Rate
+          ja-JP: 15分間のレート
      - field: Count
        type: 0
        i18n:
          zh-CN: 计数
          en-US: Count
+          ja-JP: カウント
    protocol: jmx
    jmx:
      host: ^_^host^_^
@@ -788,6 +895,7 @@ metrics:
    i18n:
      zh-CN: Kafka消费者组指标
      en-US: Kafka Group Metrics
+      ja-JP: Kafka消費者グループメトリクス
    priority: 11
    fields:
      - field: NumGroups
@@ -795,36 +903,43 @@ metrics:
        i18n:
          zh-CN: 群组数量
          en-US: Num Groups
+          ja-JP: 消費者グループ総数
      - field: NumGroupsCompletingRebalance
        type: 0
        i18n:
          zh-CN: 正在完成重新平衡的群组数量
          en-US: Num Groups Completing Rebalance
+          ja-JP: リバランス中の消費者グループ数
      - field: NumGroupsDead
        type: 0
        i18n:
          zh-CN: 死亡群组数量
          en-US: Num Groups Dead
+          ja-JP: デッドの消費者グループ数
      - field: NumGroupsEmpty
        type: 0
        i18n:
          zh-CN: 空群组数量
          en-US: Num Groups Empty
+          ja-JP: 空の消費者グループ数
      - field: NumGroupsPreparingRebalance
        type: 0
        i18n:
          zh-CN: 正在准备重新平衡的群组数量
          en-US: Num Groups Preparing Rebalance
+          ja-JP: リバランス準備中の消費者グループ数
      - field: NumGroupsStable
        type: 0
        i18n:
          zh-CN: 稳定群组数量
          en-US: Num Groups Stable
+          ja-JP: 安定した消費者グループ数
      - field: NumOffsets
        type: 0
        i18n:
          zh-CN: 偏移量数量
          en-US: Num Offsets
+          ja-JP: オフセット数
    aliasFields:
      - Value->NumGroups
      - Value->NumGroupsCompletingRebalance
@@ -18,11 +18,13 @@ app: kafka_client
 name:
  zh-CN: Kafka消息系统（客户端）
  en-US: Kafka Message（Client）
+  ja-JP: Kafkaメッセージングシステム（クライアント）

 help:
  zh-CN: HertzBeat 使用 <a href="https://hertzbeat.apache.org/zh-cn/docs/help/kafka_client">Kafka Admin Client</a> 对 Kafka 的通用指标进行采集监控。</span>
  en-US: HertzBeat uses <a href='https://hertzbeat.apache.org/docs/help/kafka_client'>Kafka Admin Client</a> to monitoring kafka general metrics. </span>
  zh-TW: HertzBeat 使用 <a href="https://hertzbeat.apache.org/zh-cn/docs/help/kafka_client">Kafka Admin Client</a> 對 Kafka 的通用指標進行采集監控。</span>
+  ja-JP: HertzBeat は <a href="https://hertzbeat.apache.org/docs/help/kafka_client">Kafka Admin Clientを介して</a> Kafkaの一般的なパフォーマンスのメトリクスを監視します。</span>

 helpLink:
  zh-CN: https://hertzbeat.apache.org/zh-cn/docs/help/kafka_client
@@ -33,12 +35,14 @@ params:
    name:
      zh-CN: 目标Host
      en-US: Target Host
+      ja-JP: 目標ホスト
    type: host
    required: true
  - field: port
    name:
      zh-CN: 端口
      en-US: Port
+      ja-JP: ポート
    type: number
    range: '[0,65535]'
    required: true
@@ -47,6 +51,7 @@ params:
    name:
      zh-CN: 是否监控内部主题
      en-US: Monitor Internal Topic
+      ja-JP: 内部トピックを監視するかどうか
    type: boolean
    required: true
    defaultValue: false
@@ -56,6 +61,7 @@ metrics:
    i18n:
      zh-CN: 主题列表
      en-US: Topic List
+      ja-JP: トピック一覧
    priority: 0
    fields:
      - field: TopicName
@@ -63,6 +69,7 @@ metrics:
        i18n:
          zh-CN: 主题名称
          en-US: Topic Name
+          ja-JP: トピック名
    protocol: kclient
    kclient:
      host: ^_^host^_^
@@ -73,6 +80,7 @@ metrics:
    i18n:
      zh-CN: 主题详细信息
      en-US: Topic Detail Info
+      ja-JP: トピック詳細情報
    priority: 1
    fields:
      - field: TopicName
@@ -80,36 +88,43 @@ metrics:
        i18n:
          zh-CN: 主题名称
          en-US: Topic Name
+          ja-JP: トピック名
      - field: PartitionNum
        type: 1
        i18n:
          zh-CN: 分区数量
          en-US: Partition Num
+          ja-JP: パーティション数
      - field: PartitionLeader
        type: 1
        i18n:
          zh-CN: 分区领导者
          en-US: Partition Leader
+          ja-JP: パーティションリーダー
      - field: BrokerHost
        type: 1
        i18n:
          zh-CN: Broker主机
          en-US: Broker Host
+          ja-JP: ブローカーホスト
      - field: BrokerPort
        type: 1
        i18n:
          zh-CN: Broker端口
          en-US: Broker Port
+          ja-JP: ブローカーポート
      - field: ReplicationFactorSize
        type: 1
        i18n:
          zh-CN: 复制因子大小
          en-US: Replication Factor Size
+          ja-JP: レプリカファクターのサイズ
      - field: ReplicationFactor
        type: 1
        i18n:
          zh-CN: 复制因子
          en-US: Replication Factor
+          ja-JP: レプリカファクター
    protocol: kclient
    kclient:
      host: ^_^host^_^
@@ -120,6 +135,7 @@ metrics:
    i18n:
      zh-CN: 主题偏移量
      en-US: Topic Offset
+      ja-JP: トピックオフセット
    priority: 2
    # Kafka offset does not need to be obtained frequently, as getting it too quickly will affect performance
    interval: 300
@@ -130,22 +146,26 @@ metrics:
        i18n:
          zh-CN: 主题名称
          en-US: Topic Name
+          ja-JP: トピック名
      - field: PartitionNum
        label: true
        type: 1
        i18n:
          zh-CN: 分区号
          en-US: Partition Num
+          ja-JP: パーティション数
      - field: earliest
        type: 0
        i18n:
          zh-CN: 最早偏移量
          en-US: Earliest Offset
+          ja-JP: 最早オフセット
      - field: latest
        type: 0
        i18n:
          zh-CN: 最新偏移量
          en-US: Latest Offset
+          ja-JP: 最新オフセット
    protocol: kclient
    kclient:
      host: ^_^host^_^
@@ -156,6 +176,7 @@ metrics:
    i18n:
      zh-CN: 消费者组情况
      en-US: Consumer Detail Info
+      ja-JP: 消費者グループ詳細情報
    priority: 3
    # Kafka offset does not need to be obtained frequently, as getting it too quickly will affect performance
    interval: 300
@@ -166,27 +187,32 @@ metrics:
        i18n:
          zh-CN: 消费者组ID
          en-US: Consumer Group ID
+          ja-JP: 消費者グループID
      - field: Group Member Num
        type: 1
        i18n:
          zh-CN: 消费者实例数量
          en-US: Group Member Num
+          ja-JP: 消費者グループのメンバー数
      - field: Topic
        label: true
        type: 1
        i18n:
          zh-CN: 订阅主题名称
          en-US: Subscribed Topic Name
+          ja-JP: 購読されたトピック名
      - field: Offset of Each Partition
        type: 1
        i18n:
          zh-CN: 各分区偏移量
          en-US: Offset of Each Partition
+          ja-JP: 各パーティションのオフセット
      - field: Lag
        type: 0
        i18n:
          zh-CN: 落后偏移量
          en-US: Total Lag
+          ja-JP: ラグオフセット
    protocol: kclient
    kclient:
      host: ^_^host^_^
@@ -145,4 +145,18 @@ class MonitorsControllerTest {
                .andExpect(jsonPath("$.code").value("0"))
                .andExpect(jsonPath("$.msg").value("Import success"));
    }
+
+    @Test
+    void exportAll() throws Exception {
+        String type = "JSON";
+        
+        // Mock the behavior of monitorService.exportAll
+        doNothing().when(monitorService).exportAll(Mockito.anyString(), Mockito.any());
+        
+        // Perform the request and verify the response
+        this.mockMvc.perform(MockMvcRequestBuilders.get("/api/monitors/export/all")
+                        .param("type", type))
+                .andExpect(status().isOk())
+                .andReturn();
+    }
 }
@@ -745,6 +745,33 @@ class MonitorServiceTest {
        when(monitorDao.findById(1L)).thenReturn(Optional.of(monitor));
        when(paramDao.findParamsByMonitorId(1L)).thenReturn(params);
        assertDoesNotThrow(() -> monitorService.copyMonitor(1L));
+    }

+    @Test
+    void exportAll() throws Exception {
+        // Create some test monitors
+        Monitor monitor1 = Monitor.builder().id(1L).name("test1").app("app1").build();
+        Monitor monitor2 = Monitor.builder().id(2L).name("test2").app("app2").build();
+        List<Monitor> allMonitors = List.of(monitor1, monitor2);
+        
+        // Mock the behavior of monitorDao.findAll
+        when(monitorDao.findAll()).thenReturn(allMonitors);
+        
+        // Create a mock HttpServletResponse
+        jakarta.servlet.http.HttpServletResponse mockResponse = org.mockito.Mockito.mock(jakarta.servlet.http.HttpServletResponse.class);
+        
+        // Mock the ImExportService
+        org.apache.hertzbeat.manager.service.ImExportService mockImExportService = org.mockito.Mockito.mock(org.apache.hertzbeat.manager.service.ImExportService.class);
+        // Mock the getFileName method
+        when(mockImExportService.getFileName()).thenReturn("test.json");
+        // Set the field using reflection
+        java.lang.reflect.Field field = MonitorServiceImpl.class.getDeclaredField("imExportServiceMap");
+        field.setAccessible(true);
+        java.util.Map<String, org.apache.hertzbeat.manager.service.ImExportService> imExportServiceMap = new java.util.HashMap<>();
+        imExportServiceMap.put("JSON", mockImExportService);
+        field.set(monitorService, imExportServiceMap);
+        
+        // Test the exportAll method
+        assertDoesNotThrow(() -> monitorService.exportAll("JSON", mockResponse));
    }
 }
@@ -98,7 +98,7 @@ public abstract class PromqlQueryExecutor implements QueryExecutor {
            }
            HttpEntity<Void> httpEntity = new HttpEntity<>(headers);

-            UriComponentsBuilder uriComponentsBuilder = UriComponentsBuilder.fromHttpUrl(httpPromqlProperties.url + QUERY_PATH);
+            UriComponentsBuilder uriComponentsBuilder = UriComponentsBuilder.fromUriString(httpPromqlProperties.url + QUERY_PATH);
            uriComponentsBuilder.queryParam(HTTP_QUERY_PARAM, queryString);
            URI uri = uriComponentsBuilder.build().toUri();
            ResponseEntity<PromQlQueryContent> responseEntity = restTemplate.exchange(uri,
@@ -150,18 +150,18 @@ public abstract class PromqlQueryExecutor implements QueryExecutor {
            HttpEntity<Void> httpEntity = new HttpEntity<>(headers);
            URI uri;
            if (datasourceQuery.getTimeType().equals(RANGE)) {
-                uri = UriComponentsBuilder.fromHttpUrl(httpPromqlProperties.url() + QUERY_RANGE_PATH)
+                uri = UriComponentsBuilder.fromUriString(httpPromqlProperties.url() + QUERY_RANGE_PATH)
                        .queryParam(HTTP_QUERY_PARAM, datasourceQuery.getExpr())
                        .queryParam(HTTP_START_PARAM, datasourceQuery.getStart())
                        .queryParam(HTTP_END_PARAM, datasourceQuery.getEnd())
                        .queryParam(HTTP_STEP_PARAM, datasourceQuery.getStep())
                        .build().toUri();
            } else if (datasourceQuery.getTimeType().equals(INSTANT)) {
-                uri = UriComponentsBuilder.fromHttpUrl(httpPromqlProperties.url() + QUERY_PATH)
+                uri = UriComponentsBuilder.fromUriString(httpPromqlProperties.url() + QUERY_PATH)
                        .queryParam(HTTP_QUERY_PARAM, datasourceQuery.getExpr())
                        .build().toUri();
            } else {
-                throw new IllegalArgumentException(String.format("no such time type for query id {}.", datasourceQuery.getRefId()));
+                throw new IllegalArgumentException(String.format("no such time type for query id %s.", datasourceQuery.getRefId()));
            }
            ResponseEntity<PromQlQueryContent> responseEntity = restTemplate.exchange(uri, HttpMethod.GET, httpEntity,
                    PromQlQueryContent.class);
@@ -306,7 +306,7 @@ public class VictoriaMetricsClusterDataStorage extends AbstractHistoryDataStorag
            Duration duration = Duration.ofHours(Long.parseLong(history.replace("h", "")));
            Instant start = end.minus(duration);
            String exportUrl =  vmClusterProps.select().url() + VM_SELECT_BASE_PATH.formatted(vmClusterProps.accountID(), EXPORT_PATH);
-            URI uri = UriComponentsBuilder.fromHttpUrl(exportUrl)
+            URI uri = UriComponentsBuilder.fromUriString(exportUrl)
                    .queryParam("match", URLEncoder.encode("{" + timeSeriesSelector + "}", StandardCharsets.UTF_8))
                    .queryParam("start", String.valueOf(start.getEpochSecond()))
                    .queryParam("end", String.valueOf(end.getEpochSecond()))
@@ -404,7 +404,7 @@ public class VictoriaMetricsClusterDataStorage extends AbstractHistoryDataStorag
            }
            HttpEntity<Void> httpEntity = new HttpEntity<>(headers);
            String rangeUrl = VM_SELECT_BASE_PATH.formatted(vmClusterProps.accountID(), QUERY_RANGE_PATH);
-            URI uri = UriComponentsBuilder.fromHttpUrl(rangeUrl)
+            URI uri = UriComponentsBuilder.fromUriString(rangeUrl)
                    .queryParam("query", URLEncoder.encode("{" + timeSeriesSelector + "}", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -444,7 +444,7 @@ public class VictoriaMetricsClusterDataStorage extends AbstractHistoryDataStorag
                log.error("query metrics data from victoria-metrics failed. {}", responseEntity);
            }
            // max
-            uri = UriComponentsBuilder.fromHttpUrl(rangeUrl)
+            uri = UriComponentsBuilder.fromUriString(rangeUrl)
                    .queryParam("query", URLEncoder.encode("max_over_time({" + timeSeriesSelector + "})", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -482,7 +482,7 @@ public class VictoriaMetricsClusterDataStorage extends AbstractHistoryDataStorag
                }
            }
            // min
-            uri = UriComponentsBuilder.fromHttpUrl(rangeUrl)
+            uri = UriComponentsBuilder.fromUriString(rangeUrl)
                    .queryParam("query", URLEncoder.encode("min_over_time({" + timeSeriesSelector + "})", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -520,7 +520,7 @@ public class VictoriaMetricsClusterDataStorage extends AbstractHistoryDataStorag
                }
            }
            // avg
-            uri = UriComponentsBuilder.fromHttpUrl(rangeUrl)
+            uri = UriComponentsBuilder.fromUriString(rangeUrl)
                    .queryParam("query", URLEncoder.encode("avg_over_time({" + timeSeriesSelector + "})", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -279,7 +279,7 @@ public class VictoriaMetricsDataStorage extends AbstractHistoryDataStorage {
                headers.add(HttpHeaders.AUTHORIZATION,  NetworkConstants.BASIC + SignConstants.BLANK + encodedAuth);
            }
            HttpEntity<Void> httpEntity = new HttpEntity<>(headers);
-            URI uri = UriComponentsBuilder.fromHttpUrl(victoriaMetricsProp.url() + EXPORT_PATH)
+            URI uri = UriComponentsBuilder.fromUriString(victoriaMetricsProp.url() + EXPORT_PATH)
                    .queryParam(URLEncoder.encode("match[]", StandardCharsets.UTF_8), URLEncoder.encode("{" + timeSeriesSelector + "}", StandardCharsets.UTF_8))
                    .queryParam("start", URLEncoder.encode("now-" + history, StandardCharsets.UTF_8))
                    .queryParam("end", "now")
@@ -374,7 +374,7 @@ public class VictoriaMetricsDataStorage extends AbstractHistoryDataStorage {
                        + SignConstants.BLANK + encodedAuth);
            }
            HttpEntity<Void> httpEntity = new HttpEntity<>(headers);
-            URI uri = UriComponentsBuilder.fromHttpUrl(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
+            URI uri = UriComponentsBuilder.fromUriString(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
                    .queryParam(URLEncoder.encode("query", StandardCharsets.UTF_8), URLEncoder.encode("{" + timeSeriesSelector + "}", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -410,7 +410,7 @@ public class VictoriaMetricsDataStorage extends AbstractHistoryDataStorage {
                log.error("query metrics data from victoria-metrics failed. {}", responseEntity);
            }
            // max
-            uri = UriComponentsBuilder.fromHttpUrl(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
+            uri = UriComponentsBuilder.fromUriString(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
                    .queryParam(URLEncoder.encode("query", StandardCharsets.UTF_8), URLEncoder.encode("max_over_time({" + timeSeriesSelector + "})", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -445,7 +445,7 @@ public class VictoriaMetricsDataStorage extends AbstractHistoryDataStorage {
                }
            }
            // min
-            uri = UriComponentsBuilder.fromHttpUrl(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
+            uri = UriComponentsBuilder.fromUriString(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
                    .queryParam(URLEncoder.encode("query", StandardCharsets.UTF_8), URLEncoder.encode("min_over_time({" + timeSeriesSelector + "})", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -480,7 +480,7 @@ public class VictoriaMetricsDataStorage extends AbstractHistoryDataStorage {
                }
            }
            // avg
-            uri = UriComponentsBuilder.fromHttpUrl(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
+            uri = UriComponentsBuilder.fromUriString(victoriaMetricsProp.url() + QUERY_RANGE_PATH)
                    .queryParam(URLEncoder.encode("query", StandardCharsets.UTF_8), URLEncoder.encode("avg_over_time({" + timeSeriesSelector + "})", StandardCharsets.UTF_8))
                    .queryParam("step", "4h")
                    .queryParam("start", startTime)
@@ -0,0 +1,42 @@
+---
+title: Welcome HertzBeat's New Community Committer!
+author: MasamiYui
+author_title: Yijun Yin
+author_url: https://github.com/MasamiYui
+author_image_url: https://avatars.githubusercontent.com/u/22274133
+tags: [opensource, practice]
+keywords:
+  [
+    open source monitoring system,
+    alerting system,
+    Apache,
+    Apache Committer,
+    HertzBeat,
+  ]
+---
+
+> Hello everyone, it's a great honor to be invited by the community to become Apache HertzBeat Committer.
+
+## Self-Introduction
+
+I've been working in development since 2019, engaging in various fields such as blockchain, cybersecurity, big data, new energy, and video technology. I'm a jack-of-all-trades engineer who dabbles in a bit of everything.
+
+## My Journey with HertzBeat
+
+Initially, while setting up several services for myself, I needed a way to visualize metrics but didn't want to introduce overly complex monitoring systems. I hoped to find an out-of-the-box monitoring tool that was comprehensive and easy to extend – that’s when I discovered HertzBeat.
+
+As I used it more deeply, I began exploring its source code and developed a desire to contribute to the community. I still vividly remember the anticipation during my first pull request (PR), going through multiple rounds of debugging and verification, eagerly hoping it would be accepted into the main branch. With increased involvement, tracking community updates has gradually become a daily habit.
+
+## Welcoming Community Atmosphere
+
+The community thrives with activity, as code submissions and reviews pour in even during late-night hours. It embraces newcomers with open arms, ensuring that whether you're filing an ISSUE to report a bug or submitting a PR to contribute code, your efforts will spark thoughtful discussions and elicit detailed, actionable feedback.
+
+Currently, HertzBeat is in a phase of rapid development, with capabilities such as metrics, logs, and tracing requiring continuous enhancement and refinement. If you're interested in contributing to open-source, this is an excellent opportunity to get involved.
+
+## About Open Source
+
+For me, open source is a vessel for technical passion; growing alongside the community makes for a profoundly meaningful journey.
+
+## Conclusion
+
+A heartfelt thank you to [@tomsun28](https://github.com/tomsun28) for the nomination and guidance. I hope this encouragement drives me to make even more valuable contributions to the community. Finally, wishing Apache HertzBeat a smooth graduation from the Apache Incubator and may the community continue to grow and thrive!
@@ -141,7 +141,7 @@ git pull upstream master

 ### HertzBeat Improvement Proposal (HIP)

-If you have major new features(e.g., support metrics push gateway, support logs monitoring), you need to write a design document known as a HertzBeat Improvement Proposal (HIP). Before starting to write a HIP, make sure you follow the process [here](https://github.com/apache/hertzbeat/tree/master/hip).
+If you have major new features(e.g., support metrics push gateway, support logs monitoring), you need to write a design document known as a HertzBeat Improvement Proposal (HIP). Before starting to write a HIP, make sure you follow the process [guide](https://github.com/apache/hertzbeat/tree/master/hip).

 ### How to become a Committer?

@@ -0,0 +1,88 @@
+---
+id: maturity
+title: Maturity
+sidebar_position: 0
+---
+
+## Maturity Assessment for Apache HertzBeat™
+
+The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
+
+More details can be found [here](https://community.apache.org/apache-way/apache-project-maturity-model.html).
+
+## Status of this assessment
+
+This assessment is evaluated during HertzBeat's Incubating.
+
+## Maturity model assessment
+
+The following table is filled according to the [Apache Maturity Model](https://community.apache.org/apache-way/apache-project-maturity-model.html). Mentors and community members are welcome to comment and modify it.
+
+### CODE
+
+| **ID**   | **Description**                                                                                                                                                                                                                                                | **Status**                                                                                                                                                                                                          |
+| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **CD10** | The project produces Open Source software for distribution to the public, at no charge.                                                                                                                                                                        | **YES** The project source code is licensed under the `Apache License 2.0`.                                                                                                                                         |
+| **CD20** | Anyone can easily discover and access the project's code..                                                                                                                                                                                                     | **YES** The [official website](https://hertzbeat.apache.org/) includes `GitHub` link which can access the project's repository on GitHub directly.                                                                  |
+| **CD30** | Anyone using standard, widely-available tools, can build the code in a reproducible way.                                                                                                                                                                       | **YES**  Apache HertzBeat provide `how-to-build` document for every component to tell user how to compile on bare metal, such as the [core's](https://hertzbeat.apache.org/docs/community/development).    |
+| **CD40** | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version.                                                                                                            | **YES** It depends on git, and anyone can view the full history of the project via commit logs.                                                                                                                     |
+| **CD50** | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance. | **YES** The project uses GitHub and managed by Apache Infra, it ensuring provenance of each line of code to a committer. And the third-party contributions are accepted in accordance with the contributing guides. |
+
+### LICENSE
+
+| **ID**   | **Description**                                                                                                                                                                   | **Status**                                                                                                                                                                    |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **LC10** | The Apache License, version 2.0, covers the released code.                                                                                                                        | **YES** The [LICENSE](https://github.com/apache/hertzbeat/blob/master/LICENSE) is in GitHub repository. And all source files are with APLv2 header, checked by Github Action. |
+| **LC20** | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.                                                     | **YES** All dependencies are listed.                                                                                                                                          |
+| **LC30** | The libraries mentioned in LC20 are available as Open Source software.                                                                                                            | **YES** All dependencies are listed are available as Open Source software                                                                                                     |
+| **LC40** | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | **YES** All committers have iCLAs.                                                                                                                                            |
+| **LC50** | The project clearly defines and documents the copyright ownership of everything that the project produces.                                                                        | **YES** And all source files are with APLv2 header, checked by GitHub Action.                                                                                                 |
+
+### Releases
+
+| **ID**   | **Description**                                                                                                                                                        | **Status**                                                                                                                                                                                                |
+| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **RE10** | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.                              | **YES** Source release is distributed via [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/hertzbeat/) and linked from [download page](https://hertzbeat.apache.org/docs/download). |
+| **RE20** | The project's PPMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation.                      | **YES** All releases have been voted at <dev@hertzbeat.apache.org> and <general@incubator.apache.org>, and have at least 3 PPMC member's votes.                                                               |
+| **RE30** | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives.                                            | **YES** All releases are signed, and the [KEYS](https://dist.apache.org/repos/dist/release/incubator/hertzbeat/KEYS) are available.                                                                       |
+| **RE40** | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee.                          | **YES** User can easily build binaries from source code, and we do not provide binaries as Apache Releases.                                                                                               |
+| **RE50** | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | **YES** We can follow the [Release guide](https://hertzbeat.apache.org/docs/community/how_to_release) to make a new Apache HertzBeat release, and so far we had 4 different release managers.                |
+
+### Quality
+
+| **ID**   | **Description**                                                                                                                                                                               | **Status**                                                                                                                                                                             |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **QU10** | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. | **YES** We encourage user to [report issues](https://github.com/apache/hertzbeat/issues).                                                                                              |
+| **QU20** | The project puts a very high priority on producing secure software.                                                                                                                           | **YES** All security reports are actively handled.                                                                                                                                     |
+| **QU30** | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.                                              | **Yes** The official Github Repo provides a [security doc](https://github.com/apache/hertzbeat/blob/master/SECURITY.md)                                                                |
+| **QU40** | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features.       | **Yes** We follow semantic versions. As long as it's within one major version, it's backward compatible. And when any breaking changes added, we provide corresponding upgrade guides. |
+| **QU50** | The project strives to respond to documented bug reports in a timely manner.                                                                                                                  | **YES** The project has resolved 743+ issues and 2348+ pull requests so far, with very prompt response.                                                                                |
+
+### Community
+
+| **ID**   | **Description**                                                                                                                                                        | **Status**                                                                                                                                                                                                  |
+| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **CO10** | The project has a well-known homepage that points to all the information required to operate according to this maturity model.                                         | **YES** The [official website](https://hertzbeat.apache.org/) includes all information user need to run Apache HertzBeat.                                                                                   |
+| **CO20** | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project.                                 | **Yes** We provide contributing guides for every component. And we also have a [general contributing guide](https://hertzbeat.apache.org/docs/community/contribution)                                       |
+| **CO30** | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | **YES** All good contributions including code and non-code are welcomed.                                                                                                                                    |
+| **CO40** | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project.                          | **YES** The community has elected 2 new PPMC members and 12 new committers so far.                                                                                                                          |
+| **CO50** | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently.                        | **YES** The community has clear docs on nominating committers and PPMC members                                                                                                                              |
+| **CO60** | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects.         | **YES** All decisions are made after vote by community members.                                                                                                                                             |
+| **CO70** | The project strives to answer user questions in a timely manner.                                                                                                       | **YES** We use <dev@hertzbeat.apache.org>, [GitHub issue](https://github.com/apache/hertzbeat/issues) and [GitHub discussion](https://github.com/apache/hertzbeat/discussions) to do this in a timely manner. |
+
+### Consensus
+
+| **ID**   | **Description**                                                                                                                                                                                                           | **Status**                                                                                                   |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |--------------------------------------------------------------------------------------------------------------|
+| **CS10** | The project maintains a public list of its contributors who have decision power. The project's PPMC (Project Management Committee) consists of those contributors.                                                        | **Yes** See [members](https://hertzbeat.apache.org/team/) with all PPMC members and committers.              |
+| **CS20** | Decisions require a consensus among PPMC members and are documented on the project's main communications channel. The PPMC takes community opinions into account, but the PPMC has the final word.                        | **YES** All decisions are made by votes on <dev@hertzbeat.apache.org>, and with at least 3 +1 votes from PPMC. |
+| **CS30** | The project uses documented voting rules to build consensus when discussion is not sufficient.                                                                                                                            | **YES** The project uses the standard ASF voting rules.                                                      |
+| **CS40** | In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30.                                  | **YES** Apache HertzBeat community has not used the veto power yet except for code commits.                  |
+| **CS50** | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | **YES** All important discussions and conclusions are recorded in written form.                              |
+
+### Independence
+
+| **ID**   | **Description**                                                                          | **Status**                                                                                                                                                                |
+| -------- | ---------------------------------------------------------------------------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **IN10** | The project is independent from any corporate or organizational influence.               | **YES** The PPMC members and committer of Apache HertzBeat are from several different companies, and majority of them are NOT From the company that donated this project. |
+| **IN20** | Contributors act as themselves, not as representatives of a corporation or organization. | **YES** The contributors act on their own initiative without representing a corporation or organization.                                                                  |
@@ -21,11 +21,8 @@ Previous releases of HertzBeat may be affected by security issues, please use th
 :::

 | Version | Date       | Download                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Release                                                         |
-| ------- |------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
-| v1.7.1  | 2025.05.29 | [apache-hertzbeat-1.7.1-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-bin.tar.gz) (Server) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-collector-1.7.1-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.1/apache-hertzbeat-collector-1.7.1-incubating-bin.tar.gz) (Collector) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-collector-1.7.1-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-collector-1.7.1-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-1.7.1-incubating-src.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-src.tar.gz) (Source Code) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-src.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-src.tar.gz.sha512) )  <br/> [apache-hertzbeat-1.7.1-incubating-docker-compose.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-docker-compose.tar.gz) (Docker Compose) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-docker-compose.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.1/apache-hertzbeat-1.7.1-incubating-docker-compose.tar.gz.sha512) ) | [note](https://github.com/apache/hertzbeat/releases/tag/v1.7.1) |
-| v1.7.0  | 2025.04.02 | [apache-hertzbeat-1.7.0-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-bin.tar.gz) (Server) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-collector-1.7.0-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.0/apache-hertzbeat-collector-1.7.0-incubating-bin.tar.gz) (Collector) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-collector-1.7.0-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-collector-1.7.0-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-1.7.0-incubating-src.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-src.tar.gz) (Source Code) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-src.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-src.tar.gz.sha512) )  <br/> [apache-hertzbeat-1.7.0-incubating-docker-compose.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-docker-compose.tar.gz) (Docker Compose) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-docker-compose.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.0/apache-hertzbeat-1.7.0-incubating-docker-compose.tar.gz.sha512) ) | [note](https://github.com/apache/hertzbeat/releases/tag/v1.7.0) |
-| v1.6.1  | 2024.10.29 | [apache-hertzbeat-1.6.1-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-bin.tar.gz) (Server) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-collector-1.6.1-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.1/apache-hertzbeat-collector-1.6.1-incubating-bin.tar.gz) (Collector) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-collector-1.6.1-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-collector-1.6.1-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-1.6.1-incubating-src.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-src.tar.gz) (Source Code) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-src.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-src.tar.gz.sha512) )  <br/> [apache-hertzbeat-1.6.1-incubating-docker-compose.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-docker-compose.tar.gz) (Docker Compose) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-docker-compose.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.1/apache-hertzbeat-1.6.1-incubating-docker-compose.tar.gz.sha512) ) | [note](https://github.com/apache/hertzbeat/releases/tag/v1.6.1) |
-| v1.6.0  | 2024.06.10 | [apache-hertzbeat-1.6.0-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.0/apache-hertzbeat-1.6.0-incubating-bin.tar.gz) (Server) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.0/apache-hertzbeat-1.6.0-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.0/apache-hertzbeat-1.6.0-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.0/apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz) (Collector) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.0/apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.0/apache-hertzbeat-collector-1.6.0-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-1.6.0-incubating-src.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.6.0/apache-hertzbeat-1.6.0-incubating-src.tar.gz) (Source Code) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.6.0/apache-hertzbeat-1.6.0-incubating-src.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.6.0/apache-hertzbeat-1.6.0-incubating-src.tar.gz.sha512) )                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | [note](https://github.com/apache/hertzbeat/releases/tag/v1.6.0) |
+|---------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
+| v1.7.2  | 2025.07.05 | [apache-hertzbeat-1.7.2-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-bin.tar.gz) (Server) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-collector-1.7.2-incubating-bin.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.2/apache-hertzbeat-collector-1.7.2-incubating-bin.tar.gz) (Collector) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-collector-1.7.2-incubating-bin.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-collector-1.7.2-incubating-bin.tar.gz.sha512) ) <br/> [apache-hertzbeat-1.7.2-incubating-src.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-src.tar.gz) (Source Code) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-src.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-src.tar.gz.sha512) )  <br/> [apache-hertzbeat-1.7.2-incubating-docker-compose.tar.gz](https://www.apache.org/dyn/closer.lua/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-docker-compose.tar.gz) (Docker Compose) ( [signature](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-docker-compose.tar.gz.asc) , [sha512](https://downloads.apache.org/incubator/hertzbeat/1.7.2/apache-hertzbeat-1.7.2-incubating-docker-compose.tar.gz.sha512) ) | [note](https://github.com/apache/hertzbeat/releases/tag/v1.7.2) |

 ## Release Docker Image

@@ -211,7 +211,7 @@ alerter:

 3. Select a Specific AWS Region for SMS Messaging
   - Choose a region that supports AWS End User Messaging (SMS Service).
-   - You can check the supported regions [here](https://docs.aws.amazon.com/sms-voice/latest/userguide/phone-numbers-sms-by-country.html).
+   - You can check the supported regions [guide](https://docs.aws.amazon.com/sms-voice/latest/userguide/phone-numbers-sms-by-country.html).

 4. Move from the AWS SMS Sandbox to Production
   - By default, AWS SMS operates in sandbox mode, which restricts SMS delivery to verified phone numbers.
@@ -65,7 +65,10 @@ keywords: [open source monitoring tool, open source os monitoring tool, monitori

 #### Metric Set: Disk Information  - to be finished

- Disk information collection is not yet implemented, but will be added in future versions.
+| Metric Name   | Metric Unit | Metric Help Description                |
+|---------------|-------------|----------------------------------------|
+| disk_num      | None        | Total number of disks                  |
+| partition_num | None        | Total number of partitions             |

 #### Metric Set: Network Card Information

@@ -9,7 +9,8 @@ keywords: [open source monitoring tool, open source database monitoring tool, mo

 ### Attention, Need Add MYSQL jdbc driver jar

- Download the MYSQL jdbc driver jar package, such as mysql-connector-java-8.1.0.jar. <https://mvnrepository.com/artifact/com.mysql/mysql-connector-j/8.1.0>
+- Download the MYSQL jdbc driver jar package, such as mysql-connector-java-8.4.0.jar. <https://mvnrepository.com/artifact/com.mysql/mysql-connector-j/8.4.0>
+- It is recommended that you use the latest available mysql-connector-java version as there are regular security fixes to JDBC drivers.
 - Copy the jar package to the `hertzbeat/ext-lib` directory.
 - Restart the HertzBeat service.

@@ -5,7 +5,7 @@ sidebar_label: Apache ShenYu
 keywords: [open source monitoring tool, open source apache shenyu monitoring tool, monitoring apache shenyu metrics]
 ---

-> monitor ShenYu running status(JVM-related), include request response and other related metrics.
+> monitor ShenYu running status (JVM-related), include request response and other related metrics.

 ## Pre-monitoring operations

@@ -155,7 +155,7 @@ module.exports = {
            },
            {
              label: 'Events',
-              to: 'https://eu.communityovercode.org/',
+              to: 'https://www.apache.org/events/current-event.html',
            },
            {
              label: 'Security',
@@ -376,7 +376,7 @@ module.exports = {
          },
          {
            tagName: 'meta',
-            name: 'apple-mobile-web-app-capable',
+            name: 'mobile-web-app-capable',
            content: 'yes',
          },
          {
@@ -431,7 +431,7 @@
    "description": "The live editor label of the live codeblocks"
  },
  "convenient-content": {
-    "message": "{docker} {br}集监控-告警-通知为一体，支持应用服务，Web，数据库，缓存，操作系统，中间件，大数据，云原生，网络等监控阈值告警通知一步到位。{br} 易用友好，无需Agent，全WEB页面操作，鼠标点一点就能监控告警，零上手学习成本。{br}安全是最重要的，数据密钥全链路加密。"
+    "message": "{docker} {br}集监控-告警-通知为一体，支持应用服务，Web，数据库，缓存，操作系统，中间件，大数据，云原生，网络等监控阈值告警通知一步到位。{br} 易用友好，无需Agent，全WEB页面操作，鼠标点一点就能监控告警，无需学习成本。{br}安全是最重要的，数据密钥全链路加密。"
  },
  "custom-multi-support-content": {
    "message": "将 Http,Jmx,Ssh,Snmp,Jdbc 等协议规范可配置模板化，只需在线配置YML就可自定义监控指标。{br} 高性能，支持多采集器集群横向扩展，支持多隔离网络监控，云边协同。{br}自由的告警阈值规则，邮箱，短信，钉钉，企业微信，飞书，Webhook等消息及时送达。{br} 您相信只需配置下就能适配新K8s监控类型吗？"
@@ -15,7 +15,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring]
 ### HertzBeat 介绍

 > HertzBeat赫兹跳动 是一个拥有强大自定义监控能力，无需 Agent 的开源实时监控告警工具。
-> 致力于**易用友好**，全 WEB 页面操作，鼠标点一点就能监控告警，零上手学习成本。
+> 致力于**易用友好**，全 WEB 页面操作，鼠标点一点就能监控告警，无需学习成本。
 > 集 **监控+告警+通知** 为一体，支持对应用服务，应用程序，数据库，缓存，操作系统，大数据，中间件，Web服务器，云原生，网络，自定义等指标监控，阈值告警通知一步到位。
 > 支持更自由化的阈值规则(计算表达式)，`邮件` `Discord` `Slack` `Telegram` `钉钉` `微信` `飞书` `短信` `Webhook` 等方式及时送达。
 >
@@ -17,8 +17,8 @@ keywords: [open source monitoring system, alerting system, Linux monitoring]
 ### 特点

 - 集 **监控+告警+通知** 为一体，支持对应用服务，应用程序，数据库，缓存，操作系统，大数据，中间件，Web服务器，云原生，网络，自定义等监控阈值告警通知一步到位。
- 易用友好，无需 `Agent`，全 `WEB` 页面操作，鼠标点一点就能监控告警，零上手学习成本。
- 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需配置下就能立刻适配一款 `K8s` 或 `Docker` 等新的监控类型吗？
+- 易用友好，无需 `Agent`，全 `WEB` 页面操作，鼠标点一点就能监控告警，无需学习成本。
+- 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需简单配置即可快速适配一款 `K8s` 或 `Docker` 等新的监控类型吗？
 - 高性能，支持多采集器集群横向扩展，支持多隔离网络监控，云边协同。
 - 自由的告警阈值规则，`邮件` `Discord` `Slack` `Telegram` `钉钉` `微信` `飞书` `短信` `Webhook` 等方式消息及时送达。

--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
kangli	28f5410555	Merge branch 'master' into jackson-prop	2025-07-06 22:54:14 +08:00
Duansg Calvin 淞筱 aias00 shown Sherlock Yin kangli	553bdbaf9f	[refactor] `AlarmCacheManager` refactoring processing logic (#3525 ) 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> Co-authored-by: Sherlock Yin <sherlock.yin1994@gmail.com> Co-authored-by: kangli <likang@apache.org>	2025-07-06 22:06:30 +08:00
Carpe-Wang aias00 Calvin shown kangli tomsun28	40d3f1243b	feat: Add LogUtil wrapper and optimize logging comments (#3489 ) Co-authored-by: aias00 <liuhongyu@apache.org> Co-authored-by: Calvin <zhengqiwei@apache.org> Co-authored-by: shown <yuluo08290126@gmail.com> Co-authored-by: kangli <likang@apache.org> Co-authored-by: tomsun28 <tomsun28@outlook.com>	2025-07-06 20:57:39 +08:00
YxYL Calvin aias00 Logic shown kangli	740e3f8385	[feature] Support export all allmonitors (#3509 ) Co-authored-by: Calvin <zhengqiwei@apache.org> Co-authored-by: aias00 <liuhongyu@apache.org> Co-authored-by: Logic <zqr10159@dromara.org> Co-authored-by: shown <yuluo08290126@gmail.com> Co-authored-by: kangli <likang@apache.org>	2025-07-06 19:06:19 +08:00
tomsun28	d5d95307ba	Merge branch 'master' into jackson-prop	2025-07-06 15:12:57 +08:00
tomsun28	b6bca5a10d	[improve] make jackson serialize field all visibility Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-07-06 15:08:21 +08:00
Calvin	47d089dff7	[doc] japanese kafka client (#3550 )	2025-07-06 06:51:49 +08:00
Calvin	c6f1f07155	[doc] japanese jvm (#3545 )	2025-07-05 12:35:45 +08:00
Calvinandtomsun28	0ebd3499b7	[doc] japanese kafka (#3548 ) Co-authored-by: tomsun28 <tomsun28@outlook.com>	2025-07-05 12:04:24 +08:00
淞筱	c88d4a7b0e	[doc] update download page (#3549 )	2025-07-05 11:56:39 +08:00
tomsun28	8bebae9db6	[doc] add hertzbeat maturity and fix doc (#3544 )	2025-07-04 19:55:27 +08:00
PJ Fanning 淞筱 aias00 tomsun28	b6b1a48a5c	[doc] recommend newer mysql connector jar (#3541 ) Signed-off-by: PJ Fanning <pjfanning@users.noreply.github.com> Co-authored-by: 淞筱 <2030509072@qq.com> Co-authored-by: aias00 <liuhongyu@apache.org> Co-authored-by: tomsun28 <tomsun28@outlook.com>	2025-07-03 23:35:53 +08:00
Duansg Calvin 淞筱 aias00 shown	63ed50ef45	[doc] Fix some issues in the documentation (#3526 ) 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-07-03 23:04:31 +08:00
PJ Fanning	e63715d1b0	enable GitHub Dependabot to create PRs for security alerts but not for every dependency update (#3543 )	2025-07-03 21:27:48 +08:00
Calvin	edf3eac6d6	[doc] japanese jetty (#3539 )	2025-07-03 11:03:54 +08:00
Calvin	743f285c8d	[doc] japanese ipmi (#3537 )	2025-07-02 22:55:09 +08:00
Logicandaias00	458433464c	[doc]update download page text (#3532 ) Co-authored-by: aias00 <liuhongyu@apache.org>	2025-07-02 17:45:28 +08:00
淞筱	64740a4f85	[doc] update outdated links (#3535 )	2025-07-02 17:15:19 +08:00
淞筱andaias00	b5a2bce261	download version deal (#3531 ) Co-authored-by: aias00 <liuhongyu@apache.org>	2025-07-01 13:11:31 +08:00
Calvin	5e351c854b	[doc] japanese iotdb (#3530 )	2025-07-01 12:29:54 +08:00
aias00 Calvin 淞筱	0875bea046	fix: fix something (#3524 ) Co-authored-by: Calvin <zhengqiwei@apache.org> Co-authored-by: 淞筱 <2030509072@qq.com>	2025-06-30 10:56:55 +08:00
Calvin	9ad5f77816	[doc] japanese influxdb promql (#3527 )	2025-06-30 09:46:56 +08:00
aias00andCalvin	998f9059bc	[feat]parallel ci (#3523 ) Co-authored-by: Calvin <zhengqiwei@apache.org>	2025-06-30 00:04:10 +08:00
Liuxin aias00 Calvin	a1439c3ec2	[fix] fix i18n error and append two metrics about disk infos (#3514 ) Signed-off-by: aias00 <liuhongyu@apache.org> Co-authored-by: aias00 <liuhongyu@apache.org> Co-authored-by: Calvin <zhengqiwei@apache.org>	2025-06-29 20:20:05 +08:00
Sherlock Yin yinyijun 淞筱	742b6f6755	[doc] Add new commiter blog (#3522 ) Co-authored-by: yinyijun <yingey2011> Co-authored-by: 淞筱 <2030509072@qq.com>	2025-06-29 15:15:50 +08:00
Calvin aias00 淞筱	5fdb34598c	[doc] japanese hikvision (#3499 ) Co-authored-by: aias00 <liuhongyu@apache.org> Co-authored-by: 淞筱 <2030509072@qq.com>	2025-06-29 12:16:17 +08:00
Calvin	4f982d1ab0	[doc] japanese influxdb (#3521 )	2025-06-29 11:50:42 +08:00
Cyanty Calvin aias00	4a28056d9f	[fix] Update the correct replacement of outdated functions and placeholders (#3516 ) Co-authored-by: Calvin <zhengqiwei@apache.org> Co-authored-by: aias00 <liuhongyu@apache.org>	2025-06-28 22:31:18 +08:00
Calvinandaias00	3f2fa71e22	[doc] japanese iceberg (#3519 ) Co-authored-by: aias00 <liuhongyu@apache.org>	2025-06-28 22:25:22 +08:00
Jastandaias00	08c81bf62f	[Improve] Improve kafka e2e (#3520 ) Co-authored-by: aias00 <liuhongyu@apache.org>	2025-06-28 22:23:07 +08:00
Duansg Sherlock Yin Calvin	e16d6cb4ba	[feature] Support for Periodic Threshold preview (#3505 ) Co-authored-by: Sherlock Yin <sherlock.yin1994@gmail.com> Co-authored-by: Calvin <zhengqiwei@apache.org>	2025-06-28 20:38:38 +08:00
Calvin	a54d14e803	[doc] japanese hugeGraph (#3518 )	2025-06-28 07:24:44 +08:00
Calvinandaias00	01ae281769	[doc] japanese hive (#3506 ) Co-authored-by: aias00 <liuhongyu@apache.org>	2025-06-28 00:10:22 +08:00
Calvin	9cb10ff14d	[doc] japanese huawei switch (#3515 )	2025-06-27 20:55:27 +08:00
Calvin	62f40d3ad1	[doc] japanese hpe switch (#3511 )	2025-06-26 00:07:54 +08:00
tomsun28	57601ef989	[release] release new version 1.7.2 (#3510 ) Signed-off-by: tomsun28 <tomsun28@outlook.com>	2025-06-25 22:01:18 +08:00