From 71672594a4db8b5ddcd84a6afce7a32f78de94e2 Mon Sep 17 00:00:00 2001 From: Administrator <2787901285@qq.com> Date: Thu, 23 Apr 2026 20:40:27 +0800 Subject: [PATCH] [docs]fix: add missing Chinese translations and fix image reference paths - Add Chinese translations for 4 English-only help docs: - collector.md - mysql_account_expiry.md - registry.md - template_marketplace.md - Register new docs in sidebars.json - Fix image reference paths across multiple .md files --- home/blog/2023-01-05-monitor-iotdb.md | 26 +-- home/blog/2023-01-08-monitor-shenyu.md | 22 +-- home/blog/2023-02-02-monitor-dynamic-tp.md | 28 ++-- home/blog/2023-02-10-new-committer.md | 12 +- home/blog/2023-02-11-monitor-mysql.md | 18 +-- home/blog/2023-02-15-monitor-linux.md | 22 +-- home/blog/2023-03-22-monitor-springboot2.md | 28 ++-- home/blog/2023-05-09-hertzbeat-v1.3.1.md | 8 +- home/blog/2023-05-11-greptimedb-store.md | 6 +- home/blog/2023-07-05-hertzbeat-v1.3.2.md | 10 +- home/blog/2023-08-14-hertzbeat-v1.4.0.md | 16 +- home/blog/2023-09-26-hertzbeat-v1.4.1.md | 24 +-- home/blog/2023-11-12-hertzbeat-v1.4.2.md | 10 +- home/blog/2023-12-11-hertzbeat-v1.4.3.md | 10 +- home/blog/2024-01-18-hertzbeat-v1.4.4.md | 10 +- home/blog/2024-04-17-to-apache.md | 10 +- home/blog/2024-06-15-hertzbeat-v1.6.0.md | 16 +- home/blog/2024-07-07-new-committer.md | 2 +- home/blog/2024-07-08-new-committer.md | 6 +- home/blog/2024-07-15-new-committer.md | 4 +- home/blog/2024-07-27-new-committer.md | 2 +- home/blog/2024-07-28-new-committer.md | 2 +- home/blog/2024-07-29-new-committer.md | 4 +- home/blog/2025-08-24-hertzbeat-graduation.md | 2 +- .../advanced/extend-http-example-hertzbeat.md | 8 +- .../advanced/extend-http-example-token.md | 10 +- home/docs/advanced/extend-jmx.md | 2 +- home/docs/advanced/extend-push.md | 6 +- home/docs/advanced/extend-snmp.md | 2 +- home/docs/advanced/extend-telnet.md | 6 +- home/docs/advanced/extend-tutorial.md | 8 +- home/docs/help/alert_threshold.md | 2 +- home/docs/help/redis_cluster.md | 6 +- home/docs/help/status.md | 14 +- home/docs/introduce.md | 52 +++--- home/docs/start/baota-deploy.md | 16 +- home/docs/start/docker-deploy.md | 36 ++--- home/docs/start/package-deploy.md | 2 +- home/docs/start/rainbond-deploy.md | 8 +- home/docs/start/usecase/linux-os-practice.md | 16 +- .../start/usecase/springboot-auto-practice.md | 28 ++-- home/docs/start/usecase/sslcert-practice.md | 26 +-- home/docs/start/usecase/tdengine-practice.md | 34 ++-- home/docs/template.md | 8 +- .../2023-01-05-monitor-iotdb.md | 28 ++-- .../2023-01-08-monitor-shenyu.md | 32 ++-- .../2023-02-02-monitor-dynamic-tp.md | 30 ++-- .../2023-02-10-new-committer.md | 10 +- .../2023-02-11-monitor-mysql.md | 30 ++-- .../2023-02-15-monitor-linux.md | 32 ++-- .../2023-03-22-monitor-springboot2.md | 30 ++-- .../2023-07-05-hertzbeat-v1.3.2.md | 8 +- .../2023-08-14-hertzbeat-v1.4.0.md | 20 +-- .../2023-08-28-new-committer.md | 8 +- .../2023-09-26-hertzbeat-v1.4.1.md | 10 +- .../2023-11-12-hertzbeat-v1.4.2.md | 12 +- .../2024-01-11-new-committer.md | 2 +- .../2024-04-17-to-apache.md | 4 +- .../2024-06-15-hertzbeat-v1.6.0.md | 10 +- .../2024-07-07-new-committer.md | 2 +- .../2024-07-08-new-committer.md | 2 +- .../2024-07-15-new-committer.md | 2 +- .../2024-07-27-new-committer.md | 2 +- .../2024-07-28-new-committer.md | 2 +- .../2024-07-29-new-committer.md | 2 +- .../2025-08-24-hertzbeat-graduation.md | 2 +- .../advanced/extend-http-example-hertzbeat.md | 12 +- .../advanced/extend-http-example-token.md | 14 +- .../current/advanced/extend-http.md | 6 +- .../current/advanced/extend-jdbc.md | 6 +- .../current/advanced/extend-jmx.md | 6 +- .../current/advanced/extend-ngql.md | 20 +-- .../current/advanced/extend-point.md | 10 +- .../current/advanced/extend-push.md | 6 +- .../current/advanced/extend-snmp.md | 6 +- .../current/advanced/extend-ssh.md | 10 +- .../current/advanced/extend-telnet.md | 8 +- .../current/advanced/extend-tutorial.md | 12 +- .../community/new_committer_process.md | 48 +++--- .../current/help/alert_threshold.md | 2 +- .../current/help/collector.md | 131 +++++++++++++++ .../current/help/mysql_account_expiry.md | 24 +++ .../current/help/redis_cluster.md | 12 +- .../current/help/registry.md | 51 ++++++ .../current/help/status.md | 14 +- .../current/help/template_marketplace.md | 152 ++++++++++++++++++ .../current/introduce.md | 52 +++--- .../current/start/baota-deploy.md | 12 +- .../current/start/docker-deploy.md | 38 ++--- .../current/start/package-deploy.md | 2 +- .../current/start/rainbond-deploy.md | 8 +- .../start/usecase/linux-os-practice.md | 16 +- .../start/usecase/springboot-auto-practice.md | 28 ++-- .../current/start/usecase/sslcert-practice.md | 26 +-- .../start/usecase/tdengine-practice.md | 34 ++-- .../current/template.md | 8 +- .../advanced/extend-http-example-hertzbeat.md | 12 +- .../advanced/extend-http-example-token.md | 14 +- .../version-1.6.x/advanced/extend-http.md | 6 +- .../version-1.6.x/advanced/extend-jdbc.md | 6 +- .../version-1.6.x/advanced/extend-jmx.md | 6 +- .../version-1.6.x/advanced/extend-ngql.md | 20 +-- .../version-1.6.x/advanced/extend-point.md | 10 +- .../version-1.6.x/advanced/extend-push.md | 6 +- .../version-1.6.x/advanced/extend-snmp.md | 6 +- .../version-1.6.x/advanced/extend-ssh.md | 10 +- .../version-1.6.x/advanced/extend-telnet.md | 8 +- .../version-1.6.x/advanced/extend-tutorial.md | 12 +- .../version-1.6.x/community/contribution.md | 16 +- .../community/new_committer_process.md | 48 +++--- .../version-1.6.x/help/alert_threshold.md | 2 +- .../version-1.6.x/help/redis_cluster.md | 12 +- .../version-1.6.x/help/status.md | 14 +- .../version-1.6.x/introduce.md | 44 ++--- .../version-1.6.x/start/baota-deploy.md | 12 +- .../version-1.6.x/start/docker-deploy.md | 38 ++--- .../version-1.6.x/start/package-deploy.md | 22 +-- .../version-1.6.x/start/rainbond-deploy.md | 8 +- .../version-1.6.x/start/sslcert-practice.md | 22 +-- .../version-1.6.x/template.md | 8 +- .../advanced/extend-http-example-hertzbeat.md | 12 +- .../advanced/extend-http-example-token.md | 14 +- .../version-1.7.x/advanced/extend-http.md | 6 +- .../version-1.7.x/advanced/extend-jdbc.md | 6 +- .../version-1.7.x/advanced/extend-jmx.md | 6 +- .../version-1.7.x/advanced/extend-ngql.md | 20 +-- .../version-1.7.x/advanced/extend-point.md | 10 +- .../version-1.7.x/advanced/extend-push.md | 6 +- .../version-1.7.x/advanced/extend-snmp.md | 6 +- .../version-1.7.x/advanced/extend-ssh.md | 10 +- .../version-1.7.x/advanced/extend-telnet.md | 8 +- .../version-1.7.x/advanced/extend-tutorial.md | 12 +- .../community/new_committer_process.md | 48 +++--- .../version-1.7.x/help/alert_threshold.md | 10 +- .../version-1.7.x/help/redis_cluster.md | 12 +- .../version-1.7.x/help/status.md | 14 +- .../version-1.7.x/introduce.md | 58 +++---- .../version-1.7.x/start/baota-deploy.md | 12 +- .../version-1.7.x/start/docker-deploy.md | 38 ++--- .../version-1.7.x/start/package-deploy.md | 22 +-- .../version-1.7.x/start/rainbond-deploy.md | 8 +- .../start/usecase/linux-os-practice.md | 18 +-- .../start/usecase/springboot-auto-practice.md | 28 ++-- .../start/usecase/sslcert-practice.md | 26 +-- .../start/usecase/tdengine-practice.md | 34 ++-- .../version-1.7.x/template.md | 8 +- .../advanced/extend-http-example-hertzbeat.md | 12 +- .../advanced/extend-http-example-token.md | 14 +- .../version-1.8.0/advanced/extend-http.md | 6 +- .../version-1.8.0/advanced/extend-jdbc.md | 6 +- .../version-1.8.0/advanced/extend-jmx.md | 6 +- .../version-1.8.0/advanced/extend-ngql.md | 20 +-- .../version-1.8.0/advanced/extend-point.md | 10 +- .../version-1.8.0/advanced/extend-push.md | 6 +- .../version-1.8.0/advanced/extend-snmp.md | 6 +- .../version-1.8.0/advanced/extend-ssh.md | 10 +- .../version-1.8.0/advanced/extend-telnet.md | 8 +- .../version-1.8.0/advanced/extend-tutorial.md | 12 +- .../community/new_committer_process.md | 48 +++--- .../version-1.8.0/help/alert_threshold.md | 2 +- .../version-1.8.0/help/redis_cluster.md | 12 +- .../version-1.8.0/help/status.md | 14 +- .../version-1.8.0/introduce.md | 58 +++---- .../version-1.8.0/start/baota-deploy.md | 12 +- .../version-1.8.0/start/docker-deploy.md | 38 ++--- .../version-1.8.0/start/package-deploy.md | 22 +-- .../version-1.8.0/start/rainbond-deploy.md | 8 +- .../start/usecase/linux-os-practice.md | 16 +- .../start/usecase/springboot-auto-practice.md | 28 ++-- .../start/usecase/sslcert-practice.md | 26 +-- .../start/usecase/tdengine-practice.md | 34 ++-- .../version-1.8.0/template.md | 8 +- home/sidebars.json | 3 + .../advanced/extend-http-example-hertzbeat.md | 8 +- .../advanced/extend-http-example-token.md | 10 +- .../version-1.6.x/advanced/extend-jmx.md | 2 +- .../version-1.6.x/advanced/extend-push.md | 6 +- .../version-1.6.x/advanced/extend-snmp.md | 2 +- .../version-1.6.x/advanced/extend-telnet.md | 6 +- .../version-1.6.x/advanced/extend-tutorial.md | 8 +- .../version-1.6.x/community/contribution.md | 14 +- .../version-1.6.x/help/alert_threshold.md | 6 +- .../version-1.6.x/help/redis_cluster.md | 6 +- .../version-1.6.x/help/status.md | 14 +- .../versioned_docs/version-1.6.x/introduce.md | 44 ++--- .../version-1.6.x/start/baota-deploy.md | 16 +- .../version-1.6.x/start/docker-deploy.md | 36 ++--- .../version-1.6.x/start/package-deploy.md | 12 +- .../version-1.6.x/start/rainbond-deploy.md | 8 +- .../version-1.6.x/start/sslcert-practice.md | 24 +-- home/versioned_docs/version-1.6.x/template.md | 8 +- .../advanced/extend-http-example-hertzbeat.md | 8 +- .../advanced/extend-http-example-token.md | 10 +- .../version-1.7.x/advanced/extend-jmx.md | 2 +- .../version-1.7.x/advanced/extend-push.md | 6 +- .../version-1.7.x/advanced/extend-snmp.md | 2 +- .../version-1.7.x/advanced/extend-telnet.md | 6 +- .../version-1.7.x/advanced/extend-tutorial.md | 8 +- .../version-1.7.x/help/alert_threshold.md | 2 +- .../version-1.7.x/help/redis_cluster.md | 6 +- .../version-1.7.x/help/status.md | 14 +- .../versioned_docs/version-1.7.x/introduce.md | 52 +++--- .../version-1.7.x/start/baota-deploy.md | 16 +- .../version-1.7.x/start/docker-deploy.md | 36 ++--- .../version-1.7.x/start/package-deploy.md | 12 +- .../version-1.7.x/start/rainbond-deploy.md | 8 +- .../start/usecase/linux-os-practice.md | 18 +-- .../start/usecase/springboot-auto-practice.md | 28 ++-- .../start/usecase/sslcert-practice.md | 26 +-- .../start/usecase/tdengine-practice.md | 34 ++-- home/versioned_docs/version-1.7.x/template.md | 8 +- .../advanced/extend-http-example-hertzbeat.md | 8 +- .../advanced/extend-http-example-token.md | 10 +- .../version-1.8.0/advanced/extend-jmx.md | 2 +- .../version-1.8.0/advanced/extend-push.md | 6 +- .../version-1.8.0/advanced/extend-snmp.md | 2 +- .../version-1.8.0/advanced/extend-telnet.md | 6 +- .../version-1.8.0/advanced/extend-tutorial.md | 8 +- .../version-1.8.0/help/alert_threshold.md | 2 +- .../version-1.8.0/help/redis_cluster.md | 6 +- .../version-1.8.0/help/status.md | 14 +- .../versioned_docs/version-1.8.0/introduce.md | 52 +++--- .../version-1.8.0/start/baota-deploy.md | 16 +- .../version-1.8.0/start/docker-deploy.md | 36 ++--- .../version-1.8.0/start/package-deploy.md | 12 +- .../version-1.8.0/start/rainbond-deploy.md | 8 +- .../start/usecase/linux-os-practice.md | 16 +- .../start/usecase/springboot-auto-practice.md | 28 ++-- .../start/usecase/sslcert-practice.md | 26 +-- .../start/usecase/tdengine-practice.md | 34 ++-- home/versioned_docs/version-1.8.0/template.md | 8 +- 231 files changed, 2047 insertions(+), 1686 deletions(-) create mode 100644 home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/collector.md create mode 100644 home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/mysql_account_expiry.md create mode 100644 home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/registry.md create mode 100644 home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/template_marketplace.md diff --git a/home/blog/2023-01-05-monitor-iotdb.md b/home/blog/2023-01-05-monitor-iotdb.md index 4367cb6df2e..af7603c81f9 100644 --- a/home/blog/2023-01-05-monitor-iotdb.md +++ b/home/blog/2023-01-05-monitor-iotdb.md @@ -1,8 +1,8 @@ --- -title: Use HertzBeat Monitoring IoTDB -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: Use HertzBeat Monitoring IoTDB +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] --- @@ -33,7 +33,7 @@ tags: [opensource, practice] ```yaml # Whether to start the monitoring module, the default is false enableMetric: true - + # Data provision method, externally provide metrics data through jmx and prometheus protocol, optional parameters: [JMX, PROMETHEUS, IOTDB], IOTDB is closed by default. metricReporterList: - JMX @@ -48,26 +48,26 @@ tags: [opensource, practice] Path: Menu -> Database Monitoring -> IoTDB Monitoring -> Add IoTDB Monitoring - ![HertzBeat](/img/blog/monitor-iotdb-1.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-1.png) 2. Configure the parameters required for monitoring IoTDB Fill in the IoTDB **service IP** and **monitoring port** (default 9091) on the monitoring page, and finally click OK to add. For other parameters such as **collection interval**, **timeout period**, etc., please refer to [Help Documentation](https://hertzbeat.apache.org/docs/help/iotdb/) [https://hertzbeat.apache.org/docs/help](https://hertzbeat.apache.org/docs/help) /iotdb/ - ![HertzBeat](/img/blog/monitor-iotdb-2.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-2.png) 3. Complete ✅, now we have added the monitoring of IoTDB, check the monitoring list to see our added items. - ![HertzBeat](/img/blog/monitor-iotdb-3.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-3.png) 4. Click **Operation**->**Monitoring Details Icon** of the monitoring list item to browse the real-time monitoring metric data of IoTDB. - ![HertzBeat](/img/blog/monitor-iotdb-4.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-4.png) 5. Click **Monitoring History Details TAB** to browse IoTDB's historical monitoring metric data chart📈. - ![HertzBeat](/img/blog/monitor-iotdb-5.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-5.png) **Complete DONE! Through the above steps, it is actually two steps to sum up** @@ -87,7 +87,7 @@ tags: [opensource, practice] - Select the configured metric object. IotDB monitors many metrics, one of which is related to the status of the node `cluster_node_status` -> `status` (node status, 1=online 2=offline). - Here we configure to send an alarm when the metric `status==2`, the alarm level is **Critical Alarm**, which is triggered once, as shown in the figure below. - ![HertzBeat](/img/blog/monitor-iotdb-6.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-6.png) 2. Add message notification recipients @@ -100,11 +100,11 @@ tags: [opensource, practice] 【Alarm Notification】->【New Recipient】->【Select DingTalk Robot Notification Method】->【Set DingTalk Robot ACCESS_TOKEN】->【OK】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. Configure the associated alarm notification strategy ⚠️ [Add notification strategy] -> [Associate the recipient just set] -> [OK] - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### Finished, now wait for the warning message to come. ding ding ding ding diff --git a/home/blog/2023-01-08-monitor-shenyu.md b/home/blog/2023-01-08-monitor-shenyu.md index f07d6d178c2..2ac10731138 100644 --- a/home/blog/2023-01-08-monitor-shenyu.md +++ b/home/blog/2023-01-08-monitor-shenyu.md @@ -55,7 +55,7 @@ tags: [opensource, practice] shenyu: metrics: enabled: true #Set to true to enable - name: prometheus + name: prometheus host: 127.0.0.1 #exposed ip port: 8090 #Exposed port jmxConfig: #jmx configuration @@ -71,28 +71,28 @@ tags: [opensource, practice] Path: Menu -> Middleware Monitor -> ShenYu Monitor -> Add ShenYu Monitor - ![HertzBeat](/img/blog/monitor-shenyu-1.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-1.png) 2. Configure the parameters required for monitoring ShenYu On the monitor page, fill in ShenYu **service IP**, **monitor port** (default 8090), and click OK to add. For other parameters such as **collection interval**, **timeout**, etc., you can refer to the [help file](https://hertzbeat.apache.org/docs/help/shenyu/) [https://hertzbeat.apache.org/docs/help/shenyu/](https://hertzbeat.apache.org/docs/help/shenyu/) - ![HertzBeat](/img/blog/monitor-shenyu-1.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-1.png) 3. Done ✅, now we have added monitoring for ShenYu, check the monitor list to see our additions. - ![HertzBeat](/img/blog/monitor-shenyu-3.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-3.png) 4. Click **Options**->**Monitoring Details icon** in the monitor list to view ShenYu's real-time monitoring metrics. - ![HertzBeat](/img/blog/monitor-shenyu-4.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-4.png) 5. Click the **Monitor History TAB** to view ShenYu's historical monitoring metrics graphs 📈. - ![HertzBeat](/img/blog/monitor-shenyu-5.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-5.png) - ![HertzBeat](/img/blog/monitor-shenyu-6.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-6.png) **DONE! With the above steps, it's really only two steps** @@ -115,7 +115,7 @@ Of course, just looking at it is not perfect, monitoring is often accompanied by - There are a lot of metrics in ShenYu monitoring, for example, we will set the threshold for the `number of open file descriptors` `process_open_fds` -> `value` metric, which will alert you when the number of open file descriptors on the server side is greater than 3,000. - Here we configure an alert to be issued when the `value' of`process_open_fds` exceeds 3000, with an alert level of **Warning alert**, which is triggered three times, as shown in the following figure. - ![HertzBeat](/img/blog/monitor-shenyu-7.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-7.png) 2. Add message notification recipients @@ -130,13 +130,13 @@ Of course, just looking at it is not perfect, monitoring is often accompanied by [Alert Notification] -> [Add Recipient] -> [Select Nailed Bot Notification Method] -> [Set Nailed Bot ACCESS_TOKEN] -> [OK] - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. Configure the associated alert notification policy ⚠️ [Add Notification Policy] -> [Associate the recipient you just set] -> [OK] ! > Configure the alert notification policy to bind alert messages to recipients so that you can decide which alerts go to which person. - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### Over and out, now wait for the alert message to come through. Ding, ding, ding, ding @@ -153,7 +153,7 @@ Details : Please note that the number of file descriptors opened by ⚠️ ShenY ## Summary :::tip -This hands-on article takes us through how to use HertzBeat to monitor Apache ShenYu metrics data, and we can find that HertzBeat, which combines ``Monitoring-Alert-Notification``, is much more convenient to operate and use, and you can include ShenYu in the monitoring by simply clicking on a page. There is no need to deploy multiple components and write multiple YML configuration files. +This hands-on article takes us through how to use HertzBeat to monitor Apache ShenYu metrics data, and we can find that HertzBeat, which combines ``Monitoring-Alert-Notification``, is much more convenient to operate and use, and you can include ShenYu in the monitoring by simply clicking on a page. There is no need to deploy multiple components and write multiple YML configuration files. ::: Apache ShenYu Github: [https://github.com/apache/shenyu](https://github.com/apache/shenyu) diff --git a/home/blog/2023-02-02-monitor-dynamic-tp.md b/home/blog/2023-02-02-monitor-dynamic-tp.md index 0152c79bfb0..83bb9be7395 100644 --- a/home/blog/2023-02-02-monitor-dynamic-tp.md +++ b/home/blog/2023-02-02-monitor-dynamic-tp.md @@ -1,8 +1,8 @@ --- -title: Monitoring Practices for DynamicTp Thread Pooling Framework with HertzBeat -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: Monitoring Practices for DynamicTp Thread Pooling Framework with HertzBeat +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] --- @@ -83,28 +83,28 @@ tags: [opensource, practice] Path: Menu -> Middleware Monitor -> DynamicTp Monitor -> Add DynamicTp Monitor - ![HertzBeat](/img/blog/monitor-dynamic-tp-1.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-1.png) 2. Configure the parameters required for monitoring DynamicTp. On the monitor page, fill in DynamicTp **service IP**, **monitoring port** (default 8080), and finally click OK to add it. For other parameters such as **collection interval**, **timeout**, etc., you can refer to [help](https://hertzbeat.apache.org/docs/help/dynamic_tp/) [https://hertzbeat.apache.org/docs/help/dynamic_tp/](https://hertzbeat.apache.org/docs/help/dynamic_tp/) - ![HertzBeat](/img/blog/monitor-dynamic-tp-2.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-2.png) 3. Done ✅, now we have added monitoring for DynamicTp, check the monitor list to see our additions. - ![HertzBeat](/img/blog/monitor-dynamic-tp-1.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-1.png) 4. Click **Options**->**Monitor Details icon** in the Monitor list to view the real-time monitoring metrics of the DynamicTp thread pool. - ![HertzBeat](/img/blog/monitor-dynamic-tp-3.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-3.png) 5. Click the **Monitoring History TAB** to view a graphical representation of the historical monitoring metrics for the DynamicTp thread pool 📈. - ![HertzBeat](/img/blog/monitor-dynamic-tp-4.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-4.png) - ![HertzBeat](/img/blog/monitor-dynamic-tp-5.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-5.png) **DONE! With the above steps, it's really just two steps** @@ -127,7 +127,7 @@ Of course, just watching is not perfect, monitoring is often accompanied by alar - DynamicTp monitors some thread pool related metrics, for example, we set the threshold for the `run_timeout_count` `thread_pool_running` -> `run_timeout_count` metric, which will raise an alarm when the thread_timeout_count is greater than one. - Here we configure an alert to be issued when `thread_pool_running` has a `run_timeout_count>1`, with an alert level of **Serious Alert**, which is triggered three times, as shown in the following figure. - ![HertzBeat](/img/blog/monitor-dynamic-tp-6.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-6.png) 2. Add message notification recipients @@ -142,13 +142,13 @@ Of course, just watching is not perfect, monitoring is often accompanied by alar [Alert Notification] -> [Add Recipient] -> [Choose Dingtalk bot notification method] -> [Set Dingtalk bot ACCESS_TOKEN] -> [OK] - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. Configure the associated alert notification policy ⚠️ [Add Notification Policy] -> [Associate the recipient you just set] -> [OK] ! > Configure the alert notification policy to bind alert messages to recipients so that you can decide which alerts go to which person. - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### Over and out, now wait for the alert message to come through. Ding, ding, ding, ding @@ -165,7 +165,7 @@ Details : DynamicTp has run timeout thread, count is 2 ## Summary :::tip -This practical article takes us to experience how to use HertzBeat to monitor DynamicTp thread pool metrics data, and we can find that HertzBeat with ``monitoring-alerting-notification`` is much more convenient to operate and use, and you only need to point and click on a page to include DynamicTp thread pool into the monitoring and alert notification, and you don't need to deploy multiple components to write YML configuration files anymore. There is no need to deploy multiple components and write YML configuration files. +This practical article takes us to experience how to use HertzBeat to monitor DynamicTp thread pool metrics data, and we can find that HertzBeat with ``monitoring-alerting-notification`` is much more convenient to operate and use, and you only need to point and click on a page to include DynamicTp thread pool into the monitoring and alert notification, and you don't need to deploy multiple components to write YML configuration files anymore. There is no need to deploy multiple components and write YML configuration files. ::: DynamicTp Github: [https://github.com/dromara/dynamic-tp](https://github.com/dromara/dynamic-tp) diff --git a/home/blog/2023-02-10-new-committer.md b/home/blog/2023-02-10-new-committer.md index 587dc6be181..56534d96e46 100644 --- a/home/blog/2023-02-10-new-committer.md +++ b/home/blog/2023-02-10-new-committer.md @@ -1,12 +1,12 @@ --- -title: Welcome two new Committers from HertzBeat -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: Welcome two new Committers from HertzBeat +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) ## Welcome two new Committers from HertzBeat @@ -107,7 +107,7 @@ First of all, I am also a newcomer to Novice Village, but I can share some of my > [HertzBeat Hertz Beat](https://github.com/apache/hertzbeat) is a real-time monitoring and alarm system with powerful custom monitoring capabilities and no Agent required. Monitoring of application services, databases, operating systems, middleware, cloud native, etc., threshold alarms, and alarm notifications (email, WeChat, Dingding, Feishu, SMS, Discord, Slack, Telegram). > -> We make protocol specifications such as `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` configurable, and you only need to configure YML to use these protocols to customize and collect any metrics you want to collect. +> We make protocol specifications such as `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` configurable, and you only need to configure YML to use these protocols to customize and collect any metrics you want to collect. > Do you believe that you can immediately adapt to a new monitoring type such as K8s or Docker just by configuring YML? > > The powerful customization of `HertzBeat`, multi-type support, easy expansion, and low coupling, hope to help developers and small and medium-sized teams quickly build their own monitoring tools. diff --git a/home/blog/2023-02-11-monitor-mysql.md b/home/blog/2023-02-11-monitor-mysql.md index 8140895a55f..1c9695bdbf6 100644 --- a/home/blog/2023-02-11-monitor-mysql.md +++ b/home/blog/2023-02-11-monitor-mysql.md @@ -34,26 +34,26 @@ Keywords: [Open source monitoring tool, open source database monitoring, Mysql d Path: Menu -> Database Monitoring -> Mysql Database -> Add Mysql Database Monitoring - ![HertzBeat](/img/blog/monitor-mysql-1.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-1.png) 2. Configure the parameters required for the new monitoring Mysql database On the monitoring page, fill in Mysql **service IP**, **monitoring port** (default 3306), **account password, etc.**, and finally click OK to add. For other parameters such as **collection interval**, **timeout period**, etc., please refer to [Help Documentation](https://hertzbeat.apache.org/docs/help/mysql/) [https://hertzbeat.apache.org/docs/help](https://hertzbeat.apache.org/docs/help) /mysql/ - ![HertzBeat](/img/blog/monitor-mysql-2.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-2.png) 3. Complete ✅, now we have added the monitoring of the Mysql database, check the monitoring list to see our added items. - ![HertzBeat](/img/blog/monitor-mysql-1.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-1.png) 4. Click **Operation**->**Monitoring Details Icon** of the monitoring list item to browse the real-time monitoring metric data of the Mysql database. - ![HertzBeat](/img/blog/monitor-mysql-3.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-3.png) 5. Click **Monitoring History Details TAB** to browse the historical monitoring metric data chart of Mysql database📈. - ![HertzBeat](/img/blog/monitor-mysql-4.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-4.png) **DONE! Done! Through the above steps, in fact, it only takes one step to sum up** @@ -75,9 +75,9 @@ Of course, just looking at it is definitely not perfect. Monitoring is often acc - Select the configured metric object. Mysql database monitoring is mainly about database performance and other related metrics. For example, we set the threshold for the metric `query cache hit rate` `cache` -> `query_cache_hit_rate`. When the query cache hit rate of Mysql is very low An alarm is issued when it is less than 30%. - Here we configure to send an alarm when the `query_cache_hit_rate<30` of this metric `cache`, the alarm level is **serious alarm**, and it will be triggered after three times, as shown in the figure below. - ![HertzBeat](/img/blog/monitor-mysql-5.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-5.png) - ![HertzBeat](/img/blog/monitor-mysql-6.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-6.png) 2. Add message notification recipients @@ -92,13 +92,13 @@ Of course, just looking at it is definitely not perfect. Monitoring is often acc 【Alarm Notification】->【New Recipient】->【Select DingTalk Robot Notification Method】->【Set DingTalk Robot ACCESS_TOKEN】->【OK】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. Configure the associated alarm notification strategy ⚠️ [Add notification strategy] -> [Associate the recipient just set] -> [OK] > Configure the alarm notification policy to bind the alarm message with the receiver, so that you can decide which alarms to send to whom. - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### Finished, now wait for the warning message to come. ding ding ding ding diff --git a/home/blog/2023-02-15-monitor-linux.md b/home/blog/2023-02-15-monitor-linux.md index d0a3626c0d8..f8c136906be 100644 --- a/home/blog/2023-02-15-monitor-linux.md +++ b/home/blog/2023-02-15-monitor-linux.md @@ -31,30 +31,30 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea Path: Menu -> Operating System Monitoring -> Linux Operating System -> Add Linux Operating System Monitoring - ![HertzBeat](/img/blog/monitor-linux-1.png) + ![HertzBeat](home/static/img/blog/monitor-linux-1.png) 2. Configure the parameters required for new monitoring Linux Fill in the Linux **peer IP**, **SSH port** (default 22), **account password, etc.** on the monitoring page, and finally click OK to add. For other parameters such as **collection interval**, **timeout period**, etc., please refer to the help document [https://hertzbeat.apache.org/docs/help/mysql/](https://hertzbeat.apache.org/docs/help/mysql/) - ![HertzBeat](/img/blog/monitor-linux-2.png) + ![HertzBeat](home/static/img/blog/monitor-linux-2.png) 3. Complete ✅, now we have added the monitoring of Linux, check the monitoring list to see our added items. - ![HertzBeat](/img/blog/monitor-linux-3.png) + ![HertzBeat](home/static/img/blog/monitor-linux-3.png) 4. Click **Operation**->**Monitoring Details Icon** of the monitoring list item to browse the real-time monitoring metric data of Linux. - ![HertzBeat](/img/blog/monitor-linux-4.png) + ![HertzBeat](home/static/img/blog/monitor-linux-4.png) - ![HertzBeat](/img/blog/monitor-linux-7.png) + ![HertzBeat](home/static/img/blog/monitor-linux-7.png) 5. Click **Monitoring History Details TAB** to browse the historical monitoring metric data chart of Linux📈. - ![HertzBeat](/img/blog/monitor-linux-5.png) + ![HertzBeat](home/static/img/blog/monitor-linux-5.png) - ![HertzBeat](/img/blog/monitor-linux-6.png) + ![HertzBeat](home/static/img/blog/monitor-linux-6.png) **DONE! Done! To sum up, it only takes one step** @@ -76,9 +76,9 @@ Of course, just looking at it is definitely not perfect. Monitoring is often acc - Select the configured metric object. Linux monitors mainly related metrics such as cpu, memory, disk, network performance, etc. For example, we set the threshold for the metric `CPU utilization` `cpu` -> `usage`. When the Linux cpu utilization is greater than 90% When a warning is issued. - Here we configure to send an alarm when the `usage>90` of this metric `cpu`, the alarm level is **Warning Alarm**, which will be triggered after three times, as shown in the figure below. - ![HertzBeat](/img/blog/monitor-linux-8.png) + ![HertzBeat](home/static/img/blog/monitor-linux-8.png) - ![HertzBeat](/img/blog/monitor-linux-9.png) + ![HertzBeat](home/static/img/blog/monitor-linux-9.png) 2. Add message notification recipients @@ -93,13 +93,13 @@ Of course, just looking at it is definitely not perfect. Monitoring is often acc 【Alarm Notification】->【New Recipient】->【Select DingTalk Robot Notification Method】->【Set DingTalk Robot ACCESS_TOKEN】->【OK】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. Configure the associated alarm notification strategy ⚠️ [Add notification strategy] -> [Associate the recipient just set] -> [OK] > Configure the alarm notification policy to bind the alarm message with the receiver, so that you can decide which alarms to send to whom. - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### Finished, now wait for the warning message to come. ding ding ding ding diff --git a/home/blog/2023-03-22-monitor-springboot2.md b/home/blog/2023-03-22-monitor-springboot2.md index 3b76081c1d3..d71662ee1e4 100644 --- a/home/blog/2023-03-22-monitor-springboot2.md +++ b/home/blog/2023-03-22-monitor-springboot2.md @@ -1,8 +1,8 @@ --- title: Monitoring SpringBoot2 Metrics with HertzBeat in 5 minutes -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [opensource monitoring, SpringBoot monitoring, alert] --- @@ -88,33 +88,33 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea Path: Menu -> Application Service Monitoring -> SpringBoot2 -> Add SpringBoot2 Monitoring - ![HertzBeat](/img/blog/monitor-springboot2-1.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-1.png) 2. Configure the parameters required for new monitoring SpringBoot2 Fill in the SpringBoot2 application **peer IP**, **service port** (default 8080), **account password, etc.** on the monitoring page, and finally click OK to add. For other parameters such as **collection interval**, **timeout period**, etc., please refer to the help document [https://hertzbeat.apache.org/docs/help/](https://hertzbeat.apache.org/docs/help/) - ![HertzBeat](/img/blog/monitor-springboot2-2.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-2.png) 3. Complete ✅, now we have added the monitoring of the SpringBoot2 application, check the monitoring list to see our additions. - ![HertzBeat](/img/blog/monitor-springboot2-3.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-3.png) 4. Click **Operation**->**Monitoring Details Icon** of the monitoring list item to browse the real-time monitoring metric data of the SpringBoot2 application. - ![HertzBeat](/img/blog/monitor-springboot2-4.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-4.png) 5. Click **Monitoring History Details TAB** to browse the historical monitoring metric data chart of the SpringBoot2 application📈. - ![HertzBeat](/img/blog/monitor-springboot2-5.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-5.png) **DONE! Done! It doesn't require us to deploy agents or various cumbersome operations, isn't it very simple** - **Just one step to configure the IP port on the HertzBeat monitoring page and add SpringBoot2 application monitoring** :::tip -Through the above, we have completed the monitoring of the SpringBoot2 application. We can check the status and availability of various metrics of the SpringBoot2 application at any time in HertzBeat. +Through the above, we have completed the monitoring of the SpringBoot2 application. We can check the status and availability of various metrics of the SpringBoot2 application at any time in HertzBeat. Of course, it is impossible to manually check the metrics in real time. Monitoring is often accompanied by alarm thresholds. When the performance metrics of the SpringBoot2 application exceed our threshold or the SpringBoot2 application itself is abnormal, we can promptly notify our corresponding person in charge. The person in charge receives the notification and handles it. , this is a complete monitoring and alarm process. ::: @@ -129,9 +129,9 @@ Of course, it is impossible to manually check the metrics in real time. Monitori - Select the configured metric object. SpringBoot2 application monitoring mainly focuses on stack memory threads and other related metrics. For example, we set the threshold for the metric `threads` -> `threads`. When the number of threads in the `runnable` state is greater than At 300 an alert is issued. - Here we configure to send an alarm when `size`, `state` of `equals(state, "runnable"") && size>300` of this metric, the alarm level is **warning alarm**, which will be triggered three times, specifically As shown below. - ![HertzBeat](/img/blog/monitor-springboot2-6.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-6.png) - ![HertzBeat](/img/blog/monitor-springboot2-7.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-7.png) 2. Add message notification recipients @@ -146,13 +146,13 @@ Of course, it is impossible to manually check the metrics in real time. Monitori 【Alarm Notification】->【New Recipient】->【Select DingTalk Robot Notification Method】->【Set DingTalk Robot ACCESS_TOKEN】->【OK】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. Configure the associated alarm notification strategy ⚠️ [Add notification strategy] -> [Associate the recipient just set] -> [OK] > Configure the alarm notification policy to bind the alarm message with the receiver, so that you can decide which alarms to send to whom. - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### Finished, now wait for the warning message to come. ding ding ding ding @@ -180,7 +180,7 @@ This practical article took us to experience how to use the open source real-tim > Through the simple steps above, we have realized the monitoring of SpringBoot2, but the built-in metrics in it do not meet the needs. Can we customize and monitor more metrics of SpringBoot2? The answer is of course yes, through **Monitoring Definition**->**SpringBoot2** on the page, you can customize and modify the performance metrics you want to monitor by editing the following YML configuration file at any time. -![HertzBeat](/img/blog/monitor-springboot2-8.png) +![HertzBeat](home/static/img/blog/monitor-springboot2-8.png) ## What is HertzBeat? diff --git a/home/blog/2023-05-09-hertzbeat-v1.3.1.md b/home/blog/2023-05-09-hertzbeat-v1.3.1.md index d3b137ef303..5e4cee61c6a 100644 --- a/home/blog/2023-05-09-hertzbeat-v1.3.1.md +++ b/home/blog/2023-05-09-hertzbeat-v1.3.1.md @@ -1,15 +1,15 @@ --- title: Open source real-time monitoring tool HertzBeat v1.3.1 released -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- Website: hertzbeat.com | tancloud.cn -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## What is HertzBeat? > diff --git a/home/blog/2023-05-11-greptimedb-store.md b/home/blog/2023-05-11-greptimedb-store.md index bab74edca44..2251aae86a4 100644 --- a/home/blog/2023-05-11-greptimedb-store.md +++ b/home/blog/2023-05-11-greptimedb-store.md @@ -111,11 +111,11 @@ See the [official documentation](https://hertzbeat.apache.org/zh-cn/docs/start/d Here's the picture: ! -![HertzBeat](/img/blog/greptime-1.png) +![HertzBeat](home/static/img/blog/greptime-1.png) -![HertzBeat](/img/blog/greptime-2.png) +![HertzBeat](home/static/img/blog/greptime-2.png) -![HertzBeat](/img/blog/greptime-3.png) +![HertzBeat](home/static/img/blog/greptime-3.png) ## Summary diff --git a/home/blog/2023-07-05-hertzbeat-v1.3.2.md b/home/blog/2023-07-05-hertzbeat-v1.3.2.md index c1bc983fa7e..0a395ab45f6 100644 --- a/home/blog/2023-07-05-hertzbeat-v1.3.2.md +++ b/home/blog/2023-07-05-hertzbeat-v1.3.2.md @@ -1,15 +1,15 @@ --- -title: Open source monitoring HertzBeat v1.3.2 released, Easier to use -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: Open source monitoring HertzBeat v1.3.2 released, Easier to use +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- Website: hertzbeat.com | tancloud.cn -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## What is HertzBeat? > diff --git a/home/blog/2023-08-14-hertzbeat-v1.4.0.md b/home/blog/2023-08-14-hertzbeat-v1.4.0.md index db26e8083b7..3ab2b1a7b5c 100644 --- a/home/blog/2023-08-14-hertzbeat-v1.4.0.md +++ b/home/blog/2023-08-14-hertzbeat-v1.4.0.md @@ -1,13 +1,13 @@ --- -title: HertzBeat v1.4.0 released, cluster is coming! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat v1.4.0 released, cluster is coming! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## What is HertzBeat? @@ -23,7 +23,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] > HertzBeat's powerful customization, multi-type support, high performance, easy expansion, and low coupling, aims to help developers and teams quickly build their own monitoring system. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** @@ -42,7 +42,7 @@ The cluster version not only brings us more powerful monitoring performance, but * The monitoring task is self-scheduled in the collector cluster. A single collector hangs up and migrates the collection task without perceptual failure. Newly added collector nodes are automatically scheduled to share the collection pressure. * It is very convenient to switch between stand-alone mode and cluster mode and deploy without additional components. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) #### Cloud Edge Collaboration @@ -52,7 +52,7 @@ In the isolated network where multiple networks are not connected, in the previo HertzBeat provides cloud-edge collaboration capabilities. Edge collectors can be deployed on multiple isolated networks. When monitoring is added, collectors are specified. The collectors collect monitoring tasks within the isolated network, and report the collected data. The main HertzBeat service performs unified scheduling, management and display. This is mostly used in unified monitoring scenarios of multiple isolated data centers or cloud resources and resources under the cloud of different vendors. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Why open source cluster version? diff --git a/home/blog/2023-09-26-hertzbeat-v1.4.1.md b/home/blog/2023-09-26-hertzbeat-v1.4.1.md index db5a2eff994..a6fdc24fe25 100644 --- a/home/blog/2023-09-26-hertzbeat-v1.4.1.md +++ b/home/blog/2023-09-26-hertzbeat-v1.4.1.md @@ -1,13 +1,13 @@ --- -title: HertzBeat v1.4.1 released, better experience! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat v1.4.1 released, better experience! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## What is HertzBeat? @@ -23,7 +23,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] > HertzBeat's powerful customization, multi-type support, high performance, easy expansion, and low coupling, aims to help developers and teams quickly build their own monitoring system. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** @@ -33,23 +33,23 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] * new login page - ![HertzBeat](/img/blog/blog-new-login-page.png) + ![HertzBeat](home/static/img/blog/blog-new-login-page.png) - ![HertzBeat](/img/blog/blog-new-dashboard.png) + ![HertzBeat](home/static/img/blog/blog-new-dashboard.png) * collector manage - ![HertzBeat](/img/blog/blog-collector-manage.png) + ![HertzBeat](home/static/img/blog/blog-collector-manage.png) - ![HertzBeat](/img/blog/blog-collector-manage-form.png) + ![HertzBeat](home/static/img/blog/blog-collector-manage-form.png) * new help moudle - ![HertzBeat](/img/blog/blog-new-help-moudle.png) + ![HertzBeat](home/static/img/blog/blog-new-help-moudle.png) * monitor metrics dashboard name i18n - ![HertzBeat](/img/blog/blog-name-i18n.png) + ![HertzBeat](home/static/img/blog/blog-name-i18n.png) * refactor collector dispatcher and more diff --git a/home/blog/2023-11-12-hertzbeat-v1.4.2.md b/home/blog/2023-11-12-hertzbeat-v1.4.2.md index 38ff3177c81..ed9d697293f 100644 --- a/home/blog/2023-11-12-hertzbeat-v1.4.2.md +++ b/home/blog/2023-11-12-hertzbeat-v1.4.2.md @@ -1,8 +1,8 @@ --- -title: HertzBeat v1.4.2 released, custom notice template! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat v1.4.2 released, custom notice template! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- @@ -21,7 +21,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] > HertzBeat's powerful customization, multi-type support, high performance, easy expansion, and low coupling, aims to help developers and teams quickly build their own monitoring system. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/blog/2023-12-11-hertzbeat-v1.4.3.md b/home/blog/2023-12-11-hertzbeat-v1.4.3.md index d61e7ec5d49..2fabded0a7a 100644 --- a/home/blog/2023-12-11-hertzbeat-v1.4.3.md +++ b/home/blog/2023-12-11-hertzbeat-v1.4.3.md @@ -1,8 +1,8 @@ --- -title: HertzBeat v1.4.3 released, prometheus-compatible! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat v1.4.3 released, prometheus-compatible! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- @@ -22,7 +22,7 @@ keywords: [open source monitoring system, alerting system] > HertzBeat's powerful customization, multi-type support, high performance, easy expansion, and low coupling, aims to help developers and teams quickly build their own monitoring system. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/blog/2024-01-18-hertzbeat-v1.4.4.md b/home/blog/2024-01-18-hertzbeat-v1.4.4.md index cfbc1a36a23..2fe5633e1f6 100644 --- a/home/blog/2024-01-18-hertzbeat-v1.4.4.md +++ b/home/blog/2024-01-18-hertzbeat-v1.4.4.md @@ -1,8 +1,8 @@ --- -title: HertzBeat v1.4.4 released now! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat v1.4.4 released now! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- @@ -22,7 +22,7 @@ keywords: [open source monitoring system, alerting system] > HertzBeat's powerful customization, multi-type support, high performance, easy expansion, and low coupling, aims to help developers and teams quickly build their own monitoring system. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/blog/2024-04-17-to-apache.md b/home/blog/2024-04-17-to-apache.md index e121b18655c..2ab4ed243e8 100644 --- a/home/blog/2024-04-17-to-apache.md +++ b/home/blog/2024-04-17-to-apache.md @@ -1,8 +1,8 @@ --- title: The open-source real-time monitoring HertzBeat is donated to the Apache Incubator. -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- @@ -11,9 +11,9 @@ On April 5, 2024, the open-source real-time monitoring system HertzBeat official HertzBeat was officially open-sourced in January 2022 in the Dromara open-source community. After more than two years of continuous project maintenance and iteration by community members, along with sustained community growth, HertzBeat now proudly announces its inclusion in the Apache Incubator! -![HertzBeat](/img/blog/apache-incubator-1.png) +![HertzBeat](home/static/img/blog/apache-incubator-1.png) -![HertzBeat](/img/blog/apache-incubator-2.png) +![HertzBeat](home/static/img/blog/apache-incubator-2.png) Joining the Apache Incubator is not the end, but rather a fresh start for the project. After joining the Apache Incubator, HertzBeat will actively adhere to the "openness and collaboration" philosophy of Apache at the community level, continuously building a fair, diverse, and inclusive open-source community. At the product level, we will listen to user feedback, enhance and optimize the user experience, and create connections within the open-source ecosystem. diff --git a/home/blog/2024-06-15-hertzbeat-v1.6.0.md b/home/blog/2024-06-15-hertzbeat-v1.6.0.md index 7ce0a2f532a..5275f10e65b 100644 --- a/home/blog/2024-06-15-hertzbeat-v1.6.0.md +++ b/home/blog/2024-06-15-hertzbeat-v1.6.0.md @@ -1,17 +1,17 @@ --- -title: HertzBeat First Apache version v1.6.0 released now! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat First Apache version v1.6.0 released now! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source, monitoring, alerting] --- **Hi guys, We are excited to announce that Apache HertzBeat™ has released its first Apache version v1.6.0! 🎉.** -Through nearly five months of community development iteration and two months of Apache Incubator incubation process, Apache HertzBeat™ v1.6.0 is finally out. -In this version, we added monitoring for OpenAi, Redfish protocol servers, plugin mechanism, and support for NebulaGraph, Apache Yarn, HDFS, Hbase, Storm, and more functional features. -Due to license compatibility issues, we replaced multiple dependencies at the bottom layer, Hibernate -> EclipseLink, which is also a rare migration pitfall practice in the JPA ecosystem. +Through nearly five months of community development iteration and two months of Apache Incubator incubation process, Apache HertzBeat™ v1.6.0 is finally out. +In this version, we added monitoring for OpenAi, Redfish protocol servers, plugin mechanism, and support for NebulaGraph, Apache Yarn, HDFS, Hbase, Storm, and more functional features. +Due to license compatibility issues, we replaced multiple dependencies at the bottom layer, Hibernate -> EclipseLink, which is also a rare migration pitfall practice in the JPA ecosystem. At the same time, some bugs were fixed and some functions were optimized, and more complete documents. Welcome everyone to try to use, put forward valuable opinions and suggestions, and promote the development of HertzBeat together. **Of course, the most important thing is to give the best thanks to the contributors in the community!** @@ -36,7 +36,7 @@ Upgrade Guide: [https://hertzbeat.apache.org/blog/2024/06/11/hertzbeat-v1.6.0-up > HertzBeat's powerful customization, multi-type support, high performance, easy expansion, and low coupling, aims to help users quickly build their own monitoring system. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/blog/2024-07-07-new-committer.md b/home/blog/2024-07-07-new-committer.md index 572911db836..b1cc51bc6b7 100644 --- a/home/blog/2024-07-07-new-committer.md +++ b/home/blog/2024-07-07-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > 🎉 I am very pleased to become a Committer for the Apache HertzBeat™ project, and I have been invited by the community to introduce myself 🥰. diff --git a/home/blog/2024-07-08-new-committer.md b/home/blog/2024-07-08-new-committer.md index fba82ba2790..35fd392365f 100644 --- a/home/blog/2024-07-08-new-committer.md +++ b/home/blog/2024-07-08-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) ## First acquaintance with Apache HertzBeat @@ -15,7 +15,7 @@ I first came into contact with the Apache HertzBeat™ project by chance. At tha ### Start contributing -After having a preliminary understanding of the project, I found that it needed to complete the monitoring scope of the big data field, so I decided to start contributing some code. I started with supplementing big data monitoring. This not only helped me understand the project more deeply, but also gradually let other members of the community know me. +After having a preliminary understanding of the project, I found that it needed to complete the monitoring scope of the big data field, so I decided to start contributing some code. I started with supplementing big data monitoring. This not only helped me understand the project more deeply, but also gradually let other members of the community know me. I remember that the first Pull Request I submitted was to add a new Hbase cluster monitoring template. Although it seems insignificant, I was very excited when it was merged. This was a real interaction between me and the open source community and my first step towards greater contribution. ### In-depth participation @@ -46,5 +46,5 @@ This process made me understand the importance of cooperation and made me feel t ### Conclusion -Becoming a Committer of the Apache HertzBeat™ project is a challenging and rewarding journey. Through continuous learning and contribution, I have not only improved my technical ability, but also found a sense of belonging and accomplishment in the community. +Becoming a Committer of the Apache HertzBeat™ project is a challenging and rewarding journey. Through continuous learning and contribution, I have not only improved my technical ability, but also found a sense of belonging and accomplishment in the community. I hope that my experience can inspire more people to participate in the open source community and jointly promote the progress and development of technology. To borrow the words of Tom: Participating in open source should not affect everyone's work and life, otherwise it will go against the original intention. Everyone should participate in the free time after get off work. diff --git a/home/blog/2024-07-15-new-committer.md b/home/blog/2024-07-15-new-committer.md index e9b306c19c7..615f47651f9 100644 --- a/home/blog/2024-07-15-new-committer.md +++ b/home/blog/2024-07-15-new-committer.md @@ -7,13 +7,13 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) Hello everyone, I am very honored to receive an invitation from the community to be nominated as a Committer for Apache HertzBeat. Let me introduce myself briefly. I have been working as a backend developer since 2019, mainly using Java. Currently, I am working at a network security company, focusing on the backend development of network security-related products. ## Encounter -In my work, several physical servers are deployed, running various databases and middleware. Although we have deployed the Prometheus + Grafana monitoring combination, most services and servers require additional installation of exporters. +In my work, several physical servers are deployed, running various databases and middleware. Although we have deployed the Prometheus + Grafana monitoring combination, most services and servers require additional installation of exporters. As a result, this monitoring system does not cover the entire project. Sometimes, we only realize a service is down when it is too late. One day in April, I came across an article introducing HertzBeat. I was immediately attracted by its unique features, such as no need for agents and fully visualized configuration, along with support for one-click deployment via Docker. I quickly deployed HertzBeat and put it into use. ### Familiarization diff --git a/home/blog/2024-07-27-new-committer.md b/home/blog/2024-07-27-new-committer.md index 51a3ad24088..526cd5adeb0 100644 --- a/home/blog/2024-07-27-new-committer.md +++ b/home/blog/2024-07-27-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > It's an honor for me to become a Committer of Apache HertzBeat diff --git a/home/blog/2024-07-28-new-committer.md b/home/blog/2024-07-28-new-committer.md index 3012104782e..58b95c6dd2c 100644 --- a/home/blog/2024-07-28-new-committer.md +++ b/home/blog/2024-07-28-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > It's an honor for me to become a Committer of Apache HertzBeat > diff --git a/home/blog/2024-07-29-new-committer.md b/home/blog/2024-07-29-new-committer.md index 143635d3f73..6aced9da59f 100644 --- a/home/blog/2024-07-29-new-committer.md +++ b/home/blog/2024-07-29-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![HertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > It's an honor for me to become a Committer of Apache HertzBeat @@ -17,7 +17,7 @@ In the open-source community, every contribution not only pushes the project for ## Starting from the Details: Optimizing Visuals and Interactions -I firmly believe that details determine success or failure. When I first joined the project, I began by optimizing the interface to enhance the user's visual and interactive experience. I refined the modal window layout of the monitoring selection menu to better align with user operation habits. +I firmly believe that details determine success or failure. When I first joined the project, I began by optimizing the interface to enhance the user's visual and interactive experience. I refined the modal window layout of the monitoring selection menu to better align with user operation habits. I adjusted the header style and content layout of the monitoring details page to make information presentation clearer and more intuitive. Additionally, I unified the border-radius values of components and addressed issues such as missing internationalization translations, ensuring the consistency and completeness of the system interface. These seemingly minor changes significantly enhanced the overall aesthetics and user experience of the system. Through this process, I gained a profound understanding of the importance of interface design for user experience and honed my attention to detail. diff --git a/home/blog/2025-08-24-hertzbeat-graduation.md b/home/blog/2025-08-24-hertzbeat-graduation.md index fa7b30b3170..e49ce2d7590 100644 --- a/home/blog/2025-08-24-hertzbeat-graduation.md +++ b/home/blog/2025-08-24-hertzbeat-graduation.md @@ -17,7 +17,7 @@ tags: [opensource, apache] [Apache HertzBeat](https://github.com/apache/hertzbeat) is an easy-to-use, open-source, real-time monitoring and alerting system that requires no agent, features a high-performance cluster, is compatible with Prometheus, and offers powerful custom monitoring and status page building capabilities. -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) ### Features diff --git a/home/docs/advanced/extend-http-example-hertzbeat.md b/home/docs/advanced/extend-http-example-hertzbeat.md index 482712129b2..205f6c36eb8 100644 --- a/home/docs/advanced/extend-http-example-hertzbeat.md +++ b/home/docs/advanced/extend-http-example-hertzbeat.md @@ -191,19 +191,19 @@ metrics: **The addition is complete, now we save and apply. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/docs/advanced/extend-http-example-token.md b/home/docs/advanced/extend-http-example-token.md index 35a0c8cef65..c08ef5c8aa7 100644 --- a/home/docs/advanced/extend-http-example-token.md +++ b/home/docs/advanced/extend-http-example-token.md @@ -229,13 +229,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **After the addition is successful, we can see the `token`, `refreshToken` metric data we collected on the details page.** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### Use `token` as a variable parameter to collect and use the following metricss @@ -389,9 +389,9 @@ metrics: **After the configuration is complete, save and apply, and check the monitoring details page** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### Set threshold alarm notification diff --git a/home/docs/advanced/extend-jmx.md b/home/docs/advanced/extend-jmx.md index 29f1bc3ff44..eaf1a16d151 100644 --- a/home/docs/advanced/extend-jmx.md +++ b/home/docs/advanced/extend-jmx.md @@ -21,7 +21,7 @@ By configuring the monitoring template YML metrics `field`, `aliasFields`, `obje **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/docs/advanced/extend-push.md b/home/docs/advanced/extend-push.md index 1762fc7b751..e950a964608 100644 --- a/home/docs/advanced/extend-push.md +++ b/home/docs/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat DashBoard -> Service Monitor -> Push Style Monitor -> New Push Style M ### Monitor Configuration Example -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/docs/advanced/extend-snmp.md b/home/docs/advanced/extend-snmp.md index ce39f61ec80..345d46b97c3 100644 --- a/home/docs/advanced/extend-snmp.md +++ b/home/docs/advanced/extend-snmp.md @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields`, and `oids` under the `snmp` p **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/docs/advanced/extend-telnet.md b/home/docs/advanced/extend-telnet.md index c4a65f885db..c3710905b58 100644 --- a/home/docs/advanced/extend-telnet.md +++ b/home/docs/advanced/extend-telnet.md @@ -1,5 +1,5 @@ --- -id: extend-telnet +id: extend-telnet title: Telnet Protocol Custom Monitoring sidebar_label: Telnet Protocol Custom Monitoring --- @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields` the `Telnet` protocol of the m **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/docs/advanced/extend-tutorial.md b/home/docs/advanced/extend-tutorial.md index 6c774d84216..a254793ae3b 100644 --- a/home/docs/advanced/extend-tutorial.md +++ b/home/docs/advanced/extend-tutorial.md @@ -203,19 +203,19 @@ metrics: **The addition is complete, now we restart the hertzbeat system. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/docs/help/alert_threshold.md b/home/docs/help/alert_threshold.md index be8e90bc5f7..1d569645873 100644 --- a/home/docs/help/alert_threshold.md +++ b/home/docs/help/alert_threshold.md @@ -26,7 +26,7 @@ Support visual page configuration or more flexible expression rule configuration Configure the threshold, for example: Select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) Configuration item details: diff --git a/home/docs/help/redis_cluster.md b/home/docs/help/redis_cluster.md index e548d0eb91d..d030162e9da 100644 --- a/home/docs/help/redis_cluster.md +++ b/home/docs/help/redis_cluster.md @@ -98,7 +98,7 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to Add a redis monitor center, fill require parameters. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) final effect. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/docs/help/status.md b/home/docs/help/status.md index daf362a0f5c..fc8c7b91fc2 100644 --- a/home/docs/help/status.md +++ b/home/docs/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: Status Page -sidebar_label: Status Page +id: status +title: Status Page +sidebar_label: Status Page keywords: [Open Source Monitoring System, Open Source Website Monitoring, Status Page] --- @@ -24,7 +24,7 @@ The fields that need to be filled in are as follows: After filling in the organization information, click `Confirm`. -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. Add Component @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. Maintain Events @@ -59,7 +59,7 @@ When an event occurs, you can publish a notification on the status page. Click `Publish Event` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | Field Name | Field Description | Example | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -70,4 +70,4 @@ Click `Publish Event` > Note: You can publish messages multiple times to keep the team updated on the current status. -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/docs/introduce.md b/home/docs/introduce.md index c2380261256..1fdb40857f8 100644 --- a/home/docs/introduce.md +++ b/home/docs/introduce.md @@ -65,11 +65,11 @@ HertzBeat unifies four monitoring functions: HertzBeat itself did not create a data collection protocol for the monitoring client to adapt to. Instead, HertzBeat makes full use of the existing ecosystem, `SNMP protocol` to collect information from network switches and routers, `JMX specification` to collect information from Java applications, `JDBC specification` to collect information from datasets, `SSH` to directly connect to scripts to get the display information, `HTTP+ (JsonPath | prometheus, etc.)` to parse the information from API interfaces, `IPMI protocol` to collect server information, and so on. HertzBeat uses these existing standard protocols or specifications, makes them abstractly configurable, and finally makes them all available in the form of YML format monitoring templates that can be written to create templates that use these protocols to collect any desired metrics data. -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) Do you believe that users can just write a monitoring template on the UI page, click save and immediately adapt a new monitoring type like `K8s` or `Docker`? -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Built-in Monitoring Types @@ -120,7 +120,7 @@ Do you believe that users can just write a monitoring template on the UI page, c > Each monitor type is considered as a monitor template, no matter it is built-in or user-defined. You can easily add, modify and delete indicators by modifying the monitoring template. > The templates contain a series of functions such as protocol configuration, environment variables, metrics conversion, metrics calculation, units conversion, metrics collection, etc., which help users to collect the metrics they want. -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### No Agent Required @@ -143,7 +143,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t - Monitoring tasks are self-scheduled in the collector cluster, single collector hangs without sensing the failure to migrate the collection tasks, and the newly added collector nodes are automatically scheduled to share the collection pressure. - It is very easy to switch between stand-alone mode and cluster mode without additional component deployment. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Cloud Edge Collaboration @@ -152,7 +152,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t In an isolated network where multiple networks are not connected, we need to deploy a monitoring system in each network in the previous solution, which leads to data non-interoperability and inconvenient management, deployment and maintenance. `HertzBeat` provides the ability of cloud edge collaboration, can be deployed in multiple isolated networks edge collector, collector in the isolated network within the monitoring task collection, collection of data reported by the main service unified scheduling management display. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Easy to Use @@ -188,7 +188,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat - HertzBeat's user management is unified by the configuration file `sureness.yml`, which allows users to add, delete, and modify user information, user role permissions, and so on. Default password admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### Overview Page @@ -196,7 +196,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat - Show the status of currently registered collector clusters, including collector on-line status, monitoring tasks, startup time, IP address, name and so on. - Show the list of recent alarm messages, alarm level distribution etc. -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### Monitoring Center @@ -243,7 +243,7 @@ Built-in support for monitoring types include: [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### New Monitor @@ -251,7 +251,7 @@ Built-in support for monitoring types include: - The monitoring parameters configured on the page are defined by the monitoring template of the corresponding monitoring type, and users can modify the configuration parameters on the page by modifying the monitoring template. - Support associated tags to manage monitoring grouping, alarm matching, and so on. -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### Monitor Details @@ -260,16 +260,16 @@ Built-in support for monitoring types include: - Monitor Historical Data Report displays the historical values of the currently monitored metrics in the form of trend charts, supports querying hourly, daily and monthly historical data, and supports configuring the page refresh time. - ⚠️ Note that the monitoring history charts need to be configured with an external timing database in order to get the full functionality. -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### Alarm Center - The management display page of triggered alarm messages enables users to visualize the current alarm situation. - Support alarm processing, alarm marking unprocessed, alarm deletion, clearing and other batch operations. -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### Alarm Threshold @@ -277,29 +277,29 @@ Built-in support for monitoring types include: - Support real-time threshold and scheduled threshold, real-time threshold can directly trigger the alarm when monitoring data is collected, scheduled threshold supports PromQL and other expressions to calculate the trigger alarm within a specified time period. - Support visual page configuration or more flexible expression rule configuration, support configuring trigger times, alarm levels, notification templates, associated specified monitoring and so on. -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### Alarm Integration - Integration with third-party monitoring systems such as `Prometheus`, `WebHook`, `Skywalking`, `AlertManager`, etc. to receive alarm messages from these systems and perform alarm processing. -![HertzBeat](/img/home/11.png) +![HertzBeat](home/static/img/home/11.png) ### Alarm Grouping - Group convergence supports merging alarms for specified group labels by grouping. It deduplicates and converges the same repeated alarms in a time period. - When the threshold rule triggers an alarm or an external alarm is reported, it will enter the grouping convergence for alarm grouping and alarm deduplication to avoid alarm storms caused by a large number of alarm messages. -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) ### Alarm Inhibition - Alarm suppression is used to configure the suppression relationship between alarms. For example, high-level alarms suppress low-level alarms under the same instance. - When an alarm occurs, it can suppress the occurrence of other alarms. For example, when a server crashes, it can suppress all alarms on that server. -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### Alarm Silence @@ -307,7 +307,7 @@ Built-in support for monitoring types include: - This application scenario, such as users in the system maintenance, do not need to send known alarms. Users will only receive alarm messages on weekdays, and users need to avoid disturbances at night. - Alarm silence rules support one-time time period or periodic time period, support label matching and alarm level matching. -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### Message Notification @@ -317,20 +317,20 @@ Built-in support for monitoring types include: - The notification policy supports tag matching and alert level matching, which makes it convenient to assign alerts with different tags and alert levels to different receivers and handlers. - Support notification templates, users can customize the content format of the templates to meet their own personalized notification display needs. -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) ### Monitoring Template - HertzBeat makes `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` and other protocols configurable so that you can customize the metrics you want to collect using these protocols by simply configuring the monitoring template `YML` in your browser. Would you believe that you can instantly adapt a new monitoring type such as `K8s` or `Docker` just by configuring it? - All our built-in monitoring types (mysql, website, jvm, k8s) are also mapped to corresponding monitoring templates, so you can add and modify monitoring templates to customize your monitoring functions. -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Collector Cluster @@ -338,16 +338,16 @@ Built-in support for monitoring types include: - The collector cluster supports multi-node deployment, automatic load balancing, automatic failover, etc. - Supports unified management of multiple isolated networks, cloud-edge collaboration. -![HertzBeat](/img/home/18.png) +![HertzBeat](home/static/img/home/18.png) ### Status Page - Based on HertzBeat, quickly build an external status page for your own product and easily convey the real-time status of your product service to users. For example, the service status page provided by Github [https://www.githubstatus.com](https://www.githubstatus.com). - Support synchronization between the status of the status page component and the monitoring status, as well as the fault event maintenance management mechanism, etc. Improve your transparency, professionalism, and user trust, and reduce communication costs. -![HertzBeat](/img/home/19.png) +![HertzBeat](home/static/img/home/19.png) -![HertzBeat](/img/home/status.png) +![HertzBeat](home/static/img/home/status.png) --- diff --git a/home/docs/start/baota-deploy.md b/home/docs/start/baota-deploy.md index 9d7257d80f2..3673d63088e 100644 --- a/home/docs/start/baota-deploy.md +++ b/home/docs/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: Use aaPanel Deploy HertzBeat +id: baota-deploy +title: Use aaPanel Deploy HertzBeat sidebar_label: Install via aaPanel --- @@ -12,19 +12,19 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i ## Install -1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. +1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. - > Install the Docker service, skip if it already exists. + > Install the Docker service, skip if it already exists. - ![HertzBeat](/img/docs/start/install-to-aapanel-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-1.png) 2. Find `HertzBeat` in `One-Click Install` and click `Install` - ![HertzBeat](/img/docs/start/install-to-aapanel-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-2.png) 3. Config the domain, name and others, click `OK` - ![HertzBeat](/img/docs/start/install-to-aapanel-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-3.png) - Name: App name, default the `HertzBeat-random` - Version：Default `latest` - Domain：Config if you need domain access, please configure the domain name here and resolve the domain name to the server @@ -38,6 +38,6 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i - If you have set a domain name, please enter the domain name directly in the browser address bar to access, such as `http://demo.hertzbeat.apache.org`, you can access the `HertzBeat` console. - If you choose to access via `IP+Port`, please enter the domain name in the browser address bar to access `http://\:1157`, you can access the `HertzBeat` console. -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > Default account username: `admin` password: `hertzbeat` diff --git a/home/docs/start/docker-deploy.md b/home/docs/start/docker-deploy.md index 767baa99d9f..c0d5a850443 100644 --- a/home/docs/start/docker-deploy.md +++ b/home/docs/start/docker-deploy.md @@ -1,6 +1,6 @@ --- -id: docker-deploy -title: Install HertzBeat via Docker +id: docker-deploy +title: Install HertzBeat via Docker sidebar_label: Install via Docker --- @@ -53,7 +53,7 @@ It is necessary to have Docker environment in your environment. If not installed ::: -2. Start to explore HertzBeat +2. Start to explore HertzBeat Access [http://ip:1157/](http://ip:1157/) using browser. You can explore HertzBeat with default account `admin/hertzbeat` now! ### Deploy HertzBeat Collector Cluster(Optional) @@ -63,7 +63,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat By deploying multiple HertzBeat Collectors, high availability, load balancing, and cloud-edge collaboration of data can be achieved. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Execute the following command @@ -113,31 +113,31 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 1. MYSQL, TDENGINE, IoTDB and HertzBeat are deployed on the same host by Docker,HertzBeat use localhost or 127.0.0.1 connect to the database but fail The problems lies in Docker container failed to visit and connect localhost port. Because the docker default network mode is Bridge mode which can't access local machine through localhost. - > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. + > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. > Solution B：Use the Host network mode to start Docker, namely making Docker container and hosting share network. `docker run -d --network host .....` 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues： - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. - > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. + > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. 3. Historical monitoring charts have been missing data for a long time - > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. + > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. > 2: Check whether IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. 4. If the history chart on the monitoring page is not displayed，popup [please configure time series database] - > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. + > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. > Installation and initialization this database, please refer to [Using victoria-metrics to store metrics data](victoria-metrics-init) 5. The time series database is installed and configured, but the page still displays a pop-up [Unable to provide historical chart data, please configure dependent time series database] - > Please check if the configuration parameters are correct - > Is time-series database enable set to true - > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed + > Please check if the configuration parameters are correct + > Is time-series database enable set to true + > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed > You can check the startup logs according to the logs directory 6. What is the purpose of application.yml @@ -153,9 +153,9 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 7. What is the purpose of sureness.yml - > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. - > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` - > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. - > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` - > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. + > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` + > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. + > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` + > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) > For detail steps, please refer to [Configure Account Password](account-modify) diff --git a/home/docs/start/package-deploy.md b/home/docs/start/package-deploy.md index 4453269c6b0..76bd282435e 100644 --- a/home/docs/start/package-deploy.md +++ b/home/docs/start/package-deploy.md @@ -70,7 +70,7 @@ If your monitoring workload does not depend on external JDBC drivers from `ext-l Before choosing it, review the trade-offs in [Native Collector Guide](native-collector). ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Download installation package diff --git a/home/docs/start/rainbond-deploy.md b/home/docs/start/rainbond-deploy.md index 2183dd6b78f..91bf6fd36b8 100644 --- a/home/docs/start/rainbond-deploy.md +++ b/home/docs/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: Use Rainbond Deploy HertzBeat +id: rainbond-deploy +title: Use Rainbond Deploy HertzBeat sidebar_label: Install via Rainbond --- @@ -32,7 +32,7 @@ To install Rainbond, please refer to [Rainbond Quick Install](https://www.rainbo After logging in Rainbond, click Market in the left menu, switch to open source app store, and search HertzBeat in the search box, and click the Install button. -![HertzBeat](/img/docs/start/install-to-rainbond-en.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond-en.png) Fill in the following information, and click Confirm button to install. @@ -43,7 +43,7 @@ Fill in the following information, and click Confirm button to install. After installation, HertzBeat can be accessed via the Access button. -![HertzBeat](/img/docs/start/hertzbeat-topology-en.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology-en.png) :::tip HertzBeat installed via Rainbond, External Mysql database and Redis and IoTDB are used by default, The HertzBeat configuration file is also mounted, which can be modified in `Components -> Environment Configuration -> Configuration File Settings`. diff --git a/home/docs/start/usecase/linux-os-practice.md b/home/docs/start/usecase/linux-os-practice.md index 27f06ba6f51..d8e164845bd 100644 --- a/home/docs/start/usecase/linux-os-practice.md +++ b/home/docs/start/usecase/linux-os-practice.md @@ -32,7 +32,7 @@ The production environment recommends a complete deployment method, refer [Insta > HertzBeat Page -> Monitors -> New Monitor -> OS Monitor -> Add OS Linux -![HertzBeat](/img/docs/start/linux-os-practice-1.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-1.png) ### 2. Configure the monitoring parameters @@ -47,15 +47,15 @@ The production environment recommends a complete deployment method, refer [Insta Tasks can be managed using label classification, such as adding bind labels like `OS=Linux`. -![HertzBeat](/img/docs/start/linux-os-practice-2.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-2.png) ### 3. View the detection index data In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. -![HertzBeat](/img/docs/start/linux-os-practice-3.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-3.png) -![HertzBeat](/img/docs/start/linux-os-practice-4.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-4.png) ### 4. Set the threshold @@ -65,23 +65,23 @@ Here, we set a threshold rule to trigger an alert when **the usage rate of a cer > > Configure the threshold, configure the alarm expression-triggered when the metric`Disk Usage` greater than or equal to `50%`，set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/linux-os-practice-5.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-5.png) > Threshold rule has others function you can try e.g., associating thresholds with monitoring, trigger times so on. Finally, you can see the triggered alarm in the alarm center. -![HertzBeat](/img/docs/start/linux-os-practice-6.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-6.png) ### 5. Alarm notification > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Configure the Email Receiver -![HertzBeat](/img/docs/start/linux-os-practice-7.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-7.png) > HertzBeat Page -> Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured -![HertzBeat](/img/docs/start/linux-os-practice-8.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-8.png) When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. diff --git a/home/docs/start/usecase/springboot-auto-practice.md b/home/docs/start/usecase/springboot-auto-practice.md index 636aa6d95b1..0eb11b071ac 100644 --- a/home/docs/start/usecase/springboot-auto-practice.md +++ b/home/docs/start/usecase/springboot-auto-practice.md @@ -1,7 +1,7 @@ --- -id: springboot-auto-practice -title: SpringBoot Web Application Monitoring Practice -sidebar_label: SpringBoot Web Application Monitoring Practice +id: springboot-auto-practice +title: SpringBoot Web Application Monitoring Practice +sidebar_label: SpringBoot Web Application Monitoring Practice --- :::tip @@ -136,7 +136,7 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > HertzBeat Page -> Monitors -> New Monitor -> AUTO -> Prometheus Task - ![HertzBeat](/img/docs/start/springboot-auto-practice-1.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-1.png) 2. Fill in Key Parameters @@ -148,15 +148,15 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > > Tasks can be managed using label classification, such as adding Bind Labels like `env=test`. - ![HertzBeat](/img/docs/start/springboot-auto-practice-2.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-2.png) 3. View Detected Metric Data > Click on the newly created monitor to view detailed metric data, historical charts, etc. - ![HertzBeat](/img/docs/start/springboot-auto-practice-3.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-3.png) - ![HertzBeat](/img/docs/start/springboot-auto-practice-4.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-4.png) ## Grafana Visualization Integration (Optional) @@ -174,13 +174,13 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > > For example: In Grafana, select `hertzbeat-victoria-metrics` as the data source. Then click on the dashboard:「Share」→「Export」→「Save to file」to download the template and upload this file to the HertzBeat monitor. - ![HertzBeat](/img/docs/start/springboot-auto-practice-5.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-5.png) 3. View Grafana Dashboard > Go to the AUTO monitor page, click the Grafana icon button, and view the integrated Grafana dashboard. - ![HertzBeat](/img/docs/start/springboot-auto-practice-6.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-6.png) ## Alarm and Notification Interlinkage @@ -188,7 +188,7 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > HertzBeat Page -> Alerting -> Threshold -> New -> New Threshold Rule - ![HertzBeat](/img/docs/start/springboot-auto-practice-7.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-7.png) > HertzBeat provides two types of threshold rule settings: **RealTime Calculation** and **Periodically execute**. Here, we use the **Periodically execute** threshold rule as an example. > @@ -205,21 +205,21 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > >You can create many combinations of threshold rules. Users can set up richer alarm rules based on their specific needs. - ![HertzBeat](/img/docs/start/springboot-auto-practice-8.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-8.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/springboot-auto-practice-9.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-9.png) 3. Alarm Notification > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver - ![HertzBeat](/img/docs/start/springboot-auto-practice-10.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-10.png) > HertzBeat Page -> Notification -> Notice Policy -> New Notice Policy -> Select Recipient(s) and Enable Notification - ![HertzBeat](/img/docs/start/springboot-auto-practice-11.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-11.png) 4. OK! When the threshold is triggered, we will receive the corresponding alarm message. If no notification is configured, you can also view the alarm information in the alarm center. diff --git a/home/docs/start/usecase/sslcert-practice.md b/home/docs/start/usecase/sslcert-practice.md index 1219bb6e617..07aa0e47f05 100644 --- a/home/docs/start/usecase/sslcert-practice.md +++ b/home/docs/start/usecase/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL Certificate Monitoring Practice +id: ssl-cert-practice +title: SSL Certificate Monitoring Practice sidebar_label: SSL Certificate Monitoring Practice --- @@ -34,29 +34,29 @@ The production environment recommends a complete deployment method, refer [https > HertzBeat Page -> Monitors -> New Monitor -> Service Monitor -> Add SSL Certificate - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. Configure the monitoring website - > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. + > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. > Click OK Note - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. View the detection index data > In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. Set the threshold (triggered when the certificate expires) - > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule + > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule > Configure the threshold, select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > Threshold rule has others function you can try eg: associating thresholds with monitoring, trigger times so on. @@ -64,17 +64,17 @@ The production environment recommends a complete deployment method, refer [https > In the same way, switch coding threshold, add a new configuration threshold and configure an alarm expression - when the metric expires timestamp `end_timestamp`, the `now()` function is the current timestamp, if the configuration triggers an alarm one week in advance: `end_timestamp <= (now() + 604800000)` , where `604800000` is the 7-day total time difference in milliseconds. - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. Alarm notification (in time notification via Dingding WeChat Feishu, etc.) > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Config the Feishu Receiver - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) For token configuration such as Feishu, please refer to the help document @@ -82,7 +82,7 @@ The production environment recommends a complete deployment method, refer [https > Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. diff --git a/home/docs/start/usecase/tdengine-practice.md b/home/docs/start/usecase/tdengine-practice.md index 13831d1aa68..c58cf84c408 100644 --- a/home/docs/start/usecase/tdengine-practice.md +++ b/home/docs/start/usecase/tdengine-practice.md @@ -1,6 +1,6 @@ --- -id: tdengine-practice -title: TDengine Monitoring Practice +id: tdengine-practice +title: TDengine Monitoring Practice sidebar_label: TDengine Monitoring Practice --- @@ -40,7 +40,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Monitoring Center -> Add Monitoring -> Custom Monitoring -> TDengine-PromQL Task - ![HertzBeat](/img/docs/start/tdengine_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1.png) 2. Fill in key parameters @@ -52,15 +52,15 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > You can use tags to categorize tasks, such as adding business-related tags like `env=test`. - ![HertzBeat](/img/docs/start/tdengine_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_2.png) 3. View inspection indicator data > You can view task statuses in the monitoring list and view metric data charts and other information in the monitoring details. - ![HertzBeat](/img/docs/start/tdengine_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_3.png) - ![HertzBeat](/img/docs/start/tdengine_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_4.png) ## Monitor TDengine(Prometheus) @@ -68,7 +68,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Monitoring Center -> Add Monitoring -> AUTO -> Prometheus Task - ![HertzBeat](/img/docs/start/tdengine_1_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_1.png) 2. Fill in key parameters @@ -80,15 +80,15 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > You can use tags to categorize tasks, such as adding business-related tags like `env=test`. - ![HertzBeat](/img/docs/start/tdengine_1_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_2.png) 3. View inspection indicator data > You can view task statuses in the monitoring list and view metric data charts and other information in the monitoring details. - ![HertzBeat](/img/docs/start/tdengine_1_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_3.png) - ![HertzBeat](/img/docs/start/tdengine_1_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_4.png) ### Grafana visualization integration (optional) @@ -106,13 +106,13 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > For example: Select the Grafana data source `hertzbeat-victoria-metrics`, then click "Share" → "Export" → "Save to file" on the dashboard to download the template and upload it to HertzBeat monitoring. For reference, see: [taoskeeper-prometheus-dashboard](https://grafana.com/grafana/dashboards/15164-taoskeeper-prometheus-dashboard/) - ![HertzBeat](/img/docs/start/tdengine_1_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_5.png) 3. View Grafana charts > Go to the new AUTO monitoring page, click the Grafana icon button to view the Grafana chart. - ![HertzBeat](/img/docs/start/tdengine_1_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_6.png) ## Alarm and notification linkage @@ -120,7 +120,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Alerts -> Threshold Rules -> Add -> Add Threshold - ![HertzBeat](/img/docs/start/tdengine_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_5.png) > HertzBeat provides two types of threshold rule settings: **real-time calculation** and **scheduled cycle**. Here, we will use the **scheduled cycle** threshold rule as an example. > @@ -137,21 +137,21 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > There are many combinations of threshold rules that can be set, and users can set more detailed alert rules according to their needs. - ![HertzBeat](/img/docs/start/tdengine_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_6.png) > Finally, you can see the triggered alerts in the Alert Center. - ![HertzBeat](/img/docs/start/tdengine_7.png) + ![HertzBeat](home/static/img/docs/start/tdengine_7.png) 3. Alert notification > System Page -> Message Notifications -> Notification Media -> Add New Recipient - ![HertzBeat](/img/docs/start/tdengine_8.png) + ![HertzBeat](home/static/img/docs/start/tdengine_8.png) > System Page -> Message Notifications -> Notification Policies -> Add Notification Policy -> Select recipients and enable notifications - ![HertzBeat](/img/docs/start/tdengine_9.png) + ![HertzBeat](home/static/img/docs/start/tdengine_9.png) 4. OK! When the threshold rule is triggered, we will receive the corresponding alert message. If no notification is configured, you can also view the alert information in the alert center. diff --git a/home/docs/template.md b/home/docs/template.md index b88ebcd9325..80ea874935a 100644 --- a/home/docs/template.md +++ b/home/docs/template.md @@ -1,6 +1,6 @@ --- -id: template -title: Monitoring Template Here +id: template +title: Monitoring Template Here sidebar_label: Monitoring Template --- @@ -11,11 +11,11 @@ sidebar_label: Monitoring Template Here is the architecture. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **We define all monitoring collection types (mysql, website, jvm, k8s) as yml templates, and users can import these templates into the hertzbeat system to support corresponding types of monitoring, which is very convenient!** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **Welcome everyone to contribute your customized general monitoring type YML template during use. The available templates are as follows:** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-05-monitor-iotdb.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-05-monitor-iotdb.md index f4c7f6eaaad..c4d9aecf2a3 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-05-monitor-iotdb.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-05-monitor-iotdb.md @@ -1,8 +1,8 @@ --- -title: 使用 HertzBeat 对物联网数据库 IoTDB 进行监控实践 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: 使用 HertzBeat 对物联网数据库 IoTDB 进行监控实践 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [开源监控系统, 开源数据库监控, IotDB数据库监控] --- @@ -34,7 +34,7 @@ keywords: [开源监控系统, 开源数据库监控, IotDB数据库监控] ```yaml # 是否启动监控模块，默认为false enableMetric: true - + # 数据提供方式，对外部通过jmx和prometheus协议提供metrics的数据, 可选参数：[JMX, PROMETHEUS, IOTDB],IOTDB是默认关闭的。 metricReporterList: - JMX @@ -49,28 +49,28 @@ keywords: [开源监控系统, 开源数据库监控, IotDB数据库监控] 路径：菜单 -> 数据库监控 -> IoTDB监控 -> 新增IoTDB监控 - ![HertzBeat](/img/blog/monitor-iotdb-1.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-1.png) 2. 配置监控IoTDB所需参数 在监控页面填写 IoTDB **服务IP**，**监控端口**(默认9091)，最后点击确定添加即可。 其他参数如**采集间隔**，**超时时间**等可以参考[帮助文档](https://hertzbeat.apache.org/docs/help/iotdb/) [https://hertzbeat.apache.org/docs/help/iotdb/](https://hertzbeat.apache.org/docs/help/iotdb/) - ![HertzBeat](/img/blog/monitor-iotdb-2.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-2.png) 3. 完成✅,现在我们已经添加好对 IoTDB 的监控了，查看监控列表即可看到我们的添加项。 - ![HertzBeat](/img/blog/monitor-iotdb-3.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-3.png) 4. 点击监控列表项的**操作**->**监控详情图标** 即可浏览 IoTDB的实时监控指标数据。 - ![HertzBeat](/img/blog/monitor-iotdb-4.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-4.png) 5. 点击**监控历史详情TAB** 即可浏览 IoTDB的历史监控指标数据图表📈。 - ![HertzBeat](/img/blog/monitor-iotdb-5.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-5.png) -**完成DONE！通过上面几步，总结起来其实也就是两步** +**完成DONE！通过上面几步，总结起来其实也就是两步** - **一步开启 IoTDB 端`metrics`功能** - **另一步在 HertzBeat 监控页面配置IP端口添加监控即可** @@ -88,7 +88,7 @@ keywords: [开源监控系统, 开源数据库监控, IotDB数据库监控] - 选择配置的指标对象，IotDB监控有非常多的指标，其中有个指标关系到节点的状态 `cluster_node_status` -> `status` (节点状态，1=online 2=offline)。 - 这里我们就配置当此指标 `status==2` 时发出告警，告警级别为**紧急告警**，一次即触发，具体如下图。 - ![HertzBeat](/img/blog/monitor-iotdb-6.png) + ![HertzBeat](home/static/img/blog/monitor-iotdb-6.png) 2. 新增消息通知接收人 @@ -101,11 +101,11 @@ keywords: [开源监控系统, 开源数据库监控, IotDB数据库监控] 【告警通知】->【新增接收人】 ->【选择钉钉机器人通知方式】->【设置钉钉机器人ACCESS_TOKEN】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. 配置关联的告警通知策略⚠️ 【新增通知策略】-> 【将刚设置的接收人关联】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### 完毕，现在坐等告警消息过来了。叮叮叮叮 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-08-monitor-shenyu.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-08-monitor-shenyu.md index 21315bf4476..531da296ef8 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-08-monitor-shenyu.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-01-08-monitor-shenyu.md @@ -1,8 +1,8 @@ --- -title: 使用 HertzBeat 对 API 网关 Apache ShenYu 的监控实践 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: 使用 HertzBeat 对 API 网关 Apache ShenYu 的监控实践 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] --- @@ -55,7 +55,7 @@ tags: [opensource, practice] shenyu: metrics: enabled: true #设置为 true 表示开启 - name : prometheus + name : prometheus host: 127.0.0.1 #暴露的ip port: 8090 #暴露的端口 jmxConfig: #jmx配置 @@ -71,30 +71,30 @@ tags: [opensource, practice] 路径：菜单 -> 中间件监控 -> ShenYu监控 -> 新增ShenYu监控 - ![HertzBeat](/img/blog/monitor-shenyu-1.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-1.png) 2. 配置监控 ShenYu 所需参数 在监控页面填写 ShenYu **服务IP**，**监控端口**(默认8090)，最后点击确定添加即可。 其他参数如**采集间隔**，**超时时间**等可以参考[帮助文档](https://hertzbeat.apache.org/docs/help/shenyu/) [https://hertzbeat.apache.org/docs/help/shenyu/](https://hertzbeat.apache.org/docs/help/shenyu/) - ![HertzBeat](/img/blog/monitor-shenyu-1.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-1.png) 3. 完成✅,现在我们已经添加好对 ShenYu 的监控了，查看监控列表即可看到我们的添加项。 - ![HertzBeat](/img/blog/monitor-shenyu-3.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-3.png) 4. 点击监控列表项的**操作**->**监控详情图标** 即可浏览 ShenYu 的实时监控指标数据。 - ![HertzBeat](/img/blog/monitor-shenyu-4.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-4.png) 5. 点击**监控历史详情TAB** 即可浏览 ShenYu 的历史监控指标数据图表📈。 - ![HertzBeat](/img/blog/monitor-shenyu-5.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-5.png) - ![HertzBeat](/img/blog/monitor-shenyu-6.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-6.png) -**DONE！完成啦！通过上面几步，总结起来其实也就只用两步** +**DONE！完成啦！通过上面几步，总结起来其实也就只用两步** - **第一步开启 ShenYu 端`metrics`插件功能** - **第二步在 HertzBeat 监控页面配置IP端口添加监控即可** @@ -115,7 +115,7 @@ tags: [opensource, practice] - 选择配置的指标对象，ShenYu 监控有非常多的指标，我们举例对 `打开的文件描述符的数量` `process_open_fds` -> `value` 这个指标进行阈值设置， 当服务端打开文件描述符数量大于3000时发出告警。 - 这里我们就配置当此指标`process_open_fds` 的 `value>3000` 时发出告警，告警级别为**警告告警**，三次即触发，具体如下图。 - ![HertzBeat](/img/blog/monitor-shenyu-7.png) + ![HertzBeat](home/static/img/blog/monitor-shenyu-7.png) 2. 新增消息通知接收人 @@ -130,13 +130,13 @@ tags: [opensource, practice] 【告警通知】->【新增接收人】 ->【选择钉钉机器人通知方式】->【设置钉钉机器人ACCESS_TOKEN】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. 配置关联的告警通知策略⚠️ 【新增通知策略】-> 【将刚设置的接收人关联】-> 【确定】 > 配置告警通知策略，让告警消息与接收人绑定，这样就能决定哪些告警发给哪个人。 - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### 完毕，现在坐等告警消息过来啦。叮叮叮叮 @@ -153,7 +153,7 @@ tags: [opensource, practice] ## 小结 :::tip -这篇实践文章带我们体验了如何使用 HertzBeat 监控 Apache ShenYu 指标数据，可以发现将 `监控-告警-通知` 集一体的 HertzBeat 在操作与使用方面更加的便捷，在页面上简单点一点就能把 ShenYu 纳入监控，再也不需要部署多个组件，写多个有门槛的YML配置文件了。 +这篇实践文章带我们体验了如何使用 HertzBeat 监控 Apache ShenYu 指标数据，可以发现将 `监控-告警-通知` 集一体的 HertzBeat 在操作与使用方面更加的便捷，在页面上简单点一点就能把 ShenYu 纳入监控，再也不需要部署多个组件，写多个有门槛的YML配置文件了。 ::: Apache ShenYu Github: [https://github.com/apache/shenyu](https://github.com/apache/shenyu) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-02-monitor-dynamic-tp.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-02-monitor-dynamic-tp.md index 2b97b48bc8b..b90bb69929f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-02-monitor-dynamic-tp.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-02-monitor-dynamic-tp.md @@ -1,8 +1,8 @@ --- -title: 使用 HertzBeat 对 线程池框架 DynamicTp 的监控实践 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: 使用 HertzBeat 对 线程池框架 DynamicTp 的监控实践 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] --- @@ -83,30 +83,30 @@ tags: [opensource, practice] 路径：菜单 -> 中间件监控 -> DynamicTp监控 -> 新增DynamicTp监控 - ![HertzBeat](/img/blog/monitor-dynamic-tp-1.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-1.png) 2. 配置监控 DynamicTp 所需参数 在监控页面填写 DynamicTp **服务IP**，**监控端口**(默认8080)，最后点击确定添加即可。 其他参数如**采集间隔**，**超时时间**等可以参考[帮助文档](https://hertzbeat.apache.org/docs/help/dynamic_tp/) [https://hertzbeat.apache.org/docs/help/dynamic_tp/](https://hertzbeat.apache.org/docs/help/dynamic_tp/) - ![HertzBeat](/img/blog/monitor-dynamic-tp-2.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-2.png) 3. 完成✅,现在我们已经添加好对 DynamicTp 的监控了，查看监控列表即可看到我们的添加项。 - ![HertzBeat](/img/blog/monitor-dynamic-tp-1.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-1.png) 4. 点击监控列表项的**操作**->**监控详情图标** 即可浏览 DynamicTp线程池 的实时监控指标数据。 - ![HertzBeat](/img/blog/monitor-dynamic-tp-3.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-3.png) 5. 点击**监控历史详情TAB** 即可浏览 DynamicTp线程池 的历史监控指标数据图表📈。 - ![HertzBeat](/img/blog/monitor-dynamic-tp-4.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-4.png) - ![HertzBeat](/img/blog/monitor-dynamic-tp-5.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-5.png) -**DONE！完成啦！通过上面几步，总结起来其实也就只用两步** +**DONE！完成啦！通过上面几步，总结起来其实也就只用两步** - **第一步暴露 DynamicTp 端`metrics`端点`/actuator/dynamic-tp`** - **第二步在 HertzBeat 监控页面配置IP端口添加监控即可** @@ -127,7 +127,7 @@ tags: [opensource, practice] - 选择配置的指标对象，DynamicTp监控主要是一些线程池相关指标，我们举例对 `运行超时线程数量` `thread_pool_running` -> `run_timeout_count` 这个指标进行阈值设置， 当线程运行超时数量大于1时发出告警。 - 这里我们就配置当此指标`thread_pool_running` 的 `run_timeout_count>1` 时发出告警，告警级别为**严重告警**，三次即触发，具体如下图。 - ![HertzBeat](/img/blog/monitor-dynamic-tp-6.png) + ![HertzBeat](home/static/img/blog/monitor-dynamic-tp-6.png) 2. 新增消息通知接收人 @@ -142,13 +142,13 @@ tags: [opensource, practice] 【告警通知】->【新增接收人】 ->【选择钉钉机器人通知方式】->【设置钉钉机器人ACCESS_TOKEN】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. 配置关联的告警通知策略⚠️ 【新增通知策略】-> 【将刚设置的接收人关联】-> 【确定】 > 配置告警通知策略，让告警消息与接收人绑定，这样就能决定哪些告警发给哪个人。 - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### 完毕，现在坐等告警消息过来啦。叮叮叮叮 @@ -165,7 +165,7 @@ tags: [opensource, practice] ## 小结 :::tip -这篇实践文章带我们体验了如何使用 HertzBeat 监控 DynamicTp线程池 指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 DynamicTp线程池 纳入监控并告警通知，再也不需要部署多个组件写YML配置文件那些繁琐操作了。 +这篇实践文章带我们体验了如何使用 HertzBeat 监控 DynamicTp线程池 指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 DynamicTp线程池 纳入监控并告警通知，再也不需要部署多个组件写YML配置文件那些繁琐操作了。 ::: DynamicTp Github: [https://github.com/dromara/dynamic-tp](https://github.com/dromara/dynamic-tp) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-10-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-10-new-committer.md index 17ce0248194..21af137f092 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-10-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-10-new-committer.md @@ -1,12 +1,12 @@ --- -title: 恭喜 HertzBeat 又迎来了两位新晋社区 Committer -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: 恭喜 HertzBeat 又迎来了两位新晋社区 Committer +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) ## 欢迎 HertzBeat 新晋两位 Committer diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-11-monitor-mysql.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-11-monitor-mysql.md index ce735d7d195..9dd7144e715 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-11-monitor-mysql.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-11-monitor-mysql.md @@ -1,8 +1,8 @@ --- -title: 使用开源实时监控工具 HertzBeat 对 Mysql 数据库监控告警实践 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: 使用开源实时监控工具 HertzBeat 对 Mysql 数据库监控告警实践 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [开源监控系统, 开源数据库监控, Mysql数据库监控] --- @@ -34,33 +34,33 @@ keywords: [开源监控系统, 开源数据库监控, Mysql数据库监控] 路径：菜单 -> 数据库监控 -> Mysql数据库 -> 新增Mysql数据库监控 - ![HertzBeat](/img/blog/monitor-mysql-1.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-1.png) 2. 配置新增监控 Mysql 数据库所需参数 在监控页面填写 Mysql **服务IP**，**监控端口**(默认3306)，**账户密码等**，最后点击确定添加即可。 其他参数如**采集间隔**，**超时时间**等可以参考[帮助文档](https://hertzbeat.apache.org/docs/help/mysql/) [https://hertzbeat.apache.org/docs/help/mysql/](https://hertzbeat.apache.org/docs/help/mysql/) - ![HertzBeat](/img/blog/monitor-mysql-2.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-2.png) 3. 完成✅,现在我们已经添加好对 Mysql数据库 的监控了，查看监控列表即可看到我们的添加项。 - ![HertzBeat](/img/blog/monitor-mysql-1.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-1.png) 4. 点击监控列表项的**操作**->**监控详情图标** 即可浏览 Mysql数据库 的实时监控指标数据。 - ![HertzBeat](/img/blog/monitor-mysql-3.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-3.png) 5. 点击**监控历史详情TAB** 即可浏览 Mysql数据库 的历史监控指标数据图表📈。 - ![HertzBeat](/img/blog/monitor-mysql-4.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-4.png) **DONE！完成啦！通过上面几步，总结起来其实也就只用一步即可** - **在 HertzBeat 监控页面配置IP端口账户密码添加 Mysql 监控即可** :::tip -通过上面的两步我们就完成了对 Mysql数据库 的监控，我们可以在 HertzBeat 随时查看监控详情指标信息来观测其服务状态。 +通过上面的两步我们就完成了对 Mysql数据库 的监控，我们可以在 HertzBeat 随时查看监控详情指标信息来观测其服务状态。 当然只是看肯定是不完美的，监控往往伴随着告警阈值，当 Mysql 数据库的指标超出我们的期望值或异常时，能及时的通知到我们对应的负责人，负责人收到通知处理问题，这样才是一个完整的监控告警流程。 ::: @@ -75,9 +75,9 @@ keywords: [开源监控系统, 开源数据库监控, Mysql数据库监控] - 选择配置的指标对象，Mysql 数据库监控主要是数据库性能等相关指标，我们举例对 `查询缓存命中率` `cache` -> `query_cache_hit_rate` 这个指标进行阈值设置， 当Mysql的查询缓存命中率很低小于30%时发出告警。 - 这里我们就配置当此指标`cache` 的 `query_cache_hit_rate<30` 时发出告警，告警级别为**严重告警**，三次即触发，具体如下图。 - ![HertzBeat](/img/blog/monitor-mysql-5.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-5.png) - ![HertzBeat](/img/blog/monitor-mysql-6.png) + ![HertzBeat](home/static/img/blog/monitor-mysql-6.png) 2. 新增消息通知接收人 @@ -92,13 +92,13 @@ keywords: [开源监控系统, 开源数据库监控, Mysql数据库监控] 【告警通知】->【新增接收人】 ->【选择钉钉机器人通知方式】->【设置钉钉机器人ACCESS_TOKEN】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. 配置关联的告警通知策略⚠️ 【新增通知策略】-> 【将刚设置的接收人关联】-> 【确定】 > 配置告警通知策略，让告警消息与接收人绑定，这样就能决定哪些告警发给哪个人。 - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### 完毕，现在坐等告警消息过来啦。叮叮叮叮 @@ -115,7 +115,7 @@ keywords: [开源监控系统, 开源数据库监控, Mysql数据库监控] ## 小结 :::tip -这篇实践文章带我们体验了如何使用开源实时监控工具 HertzBeat 来监控 Mysql 数据库指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 Mysql 数据库纳入监控并告警通知，再也不需要部署多个组件编写配置文件那些繁琐操作了。 +这篇实践文章带我们体验了如何使用开源实时监控工具 HertzBeat 来监控 Mysql 数据库指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 Mysql 数据库纳入监控并告警通知，再也不需要部署多个组件编写配置文件那些繁琐操作了。 ::: Mysql Github: [https://github.com/mysql/mysql-server](https://github.com/mysql/mysql-server) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-15-monitor-linux.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-15-monitor-linux.md index 838001a3499..4cef289b678 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-15-monitor-linux.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-02-15-monitor-linux.md @@ -1,8 +1,8 @@ --- title: 使用开源实时监控 HertzBeat 监控 Linux 操作系统 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [开源监控系统, 操作系统监控, Linux监控] --- @@ -31,30 +31,30 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 路径：菜单 -> 操作系统监控 -> Linux操作系统 -> 新增Linux操作系统监控 - ![HertzBeat](/img/blog/monitor-linux-1.png) + ![HertzBeat](home/static/img/blog/monitor-linux-1.png) 2. 配置新增监控 Linux 所需参数 在监控页面填写 Linux **对端IP**，**SSH端口**(默认22)，**账户密码等**，最后点击确定添加即可。 其他参数如**采集间隔**，**超时时间**等可以参考帮助文档 [https://hertzbeat.apache.org/docs/help/mysql/](https://hertzbeat.apache.org/docs/help/mysql/) - ![HertzBeat](/img/blog/monitor-linux-2.png) + ![HertzBeat](home/static/img/blog/monitor-linux-2.png) 3. 完成✅,现在我们已经添加好对 Linux 的监控了，查看监控列表即可看到我们的添加项。 - ![HertzBeat](/img/blog/monitor-linux-3.png) + ![HertzBeat](home/static/img/blog/monitor-linux-3.png) 4. 点击监控列表项的**操作**->**监控详情图标** 即可浏览 Linux 的实时监控指标数据。 - ![HertzBeat](/img/blog/monitor-linux-4.png) + ![HertzBeat](home/static/img/blog/monitor-linux-4.png) - ![HertzBeat](/img/blog/monitor-linux-7.png) + ![HertzBeat](home/static/img/blog/monitor-linux-7.png) 5. 点击**监控历史详情TAB** 即可浏览 Linux 的历史监控指标数据图表📈。 - ![HertzBeat](/img/blog/monitor-linux-5.png) + ![HertzBeat](home/static/img/blog/monitor-linux-5.png) - ![HertzBeat](/img/blog/monitor-linux-6.png) + ![HertzBeat](home/static/img/blog/monitor-linux-6.png) **DONE！完成啦！不需要我们去部署agent或者各种繁琐操作，是不是很简单** @@ -121,7 +121,7 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea | mounted | 无 | 挂载点目录 | :::tip -通过上面我们就完成了对 Linux 的监控，我们可以在 HertzBeat 随时查看Linux的各种指标状态和可用性。 +通过上面我们就完成了对 Linux 的监控，我们可以在 HertzBeat 随时查看Linux的各种指标状态和可用性。 当然不可能人工一直实时查看指标，监控往往伴随着告警阈值，当 Linux 的性能指标超出我们的阈值或Linux本身异常时，能及时的通知到我们对应的负责人，负责人收到通知处理，这样才是一个完整的监控告警流程。 ::: @@ -136,9 +136,9 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea - 选择配置的指标对象，Linux 监控主要是cpu 内存 磁盘 网络性能等相关指标，我们举例对 `CPU利用率` `cpu` -> `usage` 这个指标进行阈值设置， 当Linux cpu利用率大于90%时发出告警。 - 这里我们就配置当此指标`cpu` 的 `usage>90` 时发出告警，告警级别为**警告告警**，三次即触发，具体如下图。 - ![HertzBeat](/img/blog/monitor-linux-8.png) + ![HertzBeat](home/static/img/blog/monitor-linux-8.png) - ![HertzBeat](/img/blog/monitor-linux-9.png) + ![HertzBeat](home/static/img/blog/monitor-linux-9.png) 2. 新增消息通知接收人 @@ -153,13 +153,13 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 【告警通知】->【新增接收人】 ->【选择钉钉机器人通知方式】->【设置钉钉机器人ACCESS_TOKEN】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. 配置关联的告警通知策略⚠️ 【新增通知策略】-> 【将刚设置的接收人关联】-> 【确定】 > 配置告警通知策略，让告警消息与接收人绑定，这样就能决定哪些告警发给哪个人。 - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### 完毕，现在坐等告警消息过来啦。叮叮叮叮 @@ -176,7 +176,7 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea ## 小结 :::tip -这篇实践文章带我们体验了如何使用开源实时监控工具 HertzBeat 来监控 Linux 指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 Linux 纳入监控并告警通知，再也不需要部署多个组件编写配置文件那些繁琐操作了。 +这篇实践文章带我们体验了如何使用开源实时监控工具 HertzBeat 来监控 Linux 指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 Linux 纳入监控并告警通知，再也不需要部署多个组件编写配置文件那些繁琐操作了。 ::: > 只需要一条docker命令即可安装体验heartbeat: diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-03-22-monitor-springboot2.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-03-22-monitor-springboot2.md index 3585be3b951..96657062e22 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-03-22-monitor-springboot2.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-03-22-monitor-springboot2.md @@ -1,8 +1,8 @@ --- title: 使用 HertzBeat 5分钟搞定 SpringBoot2 监控告警 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [开源监控系统, SpringBoot监控, 监控告警] --- @@ -84,33 +84,33 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 路径：菜单 -> 应用服务监控 -> SpringBoot2 -> 新增SpringBoot2监控 - ![HertzBeat](/img/blog/monitor-springboot2-1.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-1.png) 2. 配置新增监控 SpringBoot2 所需参数 在监控页面填写 SpringBoot2应用 **对端IP**，**服务端口**(默认8080)，**账户密码等**，最后点击确定添加即可。 其他参数如**采集间隔**，**超时时间**等可以参考帮助文档 [https://hertzbeat.apache.org/docs/help/](https://hertzbeat.apache.org/docs/help/) - ![HertzBeat](/img/blog/monitor-springboot2-2.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-2.png) 3. 完成✅,现在我们已经添加好对 SpringBoot2应用 的监控了，查看监控列表即可看到我们的添加项。 - ![HertzBeat](/img/blog/monitor-springboot2-3.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-3.png) 4. 点击监控列表项的**操作**->**监控详情图标** 即可浏览 SpringBoot2应用 的实时监控指标数据。 - ![HertzBeat](/img/blog/monitor-springboot2-4.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-4.png) 5. 点击**监控历史详情TAB** 即可浏览 SpringBoot2应用 的历史监控指标数据图表📈。 - ![HertzBeat](/img/blog/monitor-springboot2-5.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-5.png) **DONE！完成啦！不需要我们去部署agent或者各种繁琐操作，是不是很简单** - **只需一步在 HertzBeat 监控页面配置IP端口添加 SpringBoot2应用 监控即可** :::tip -通过上面我们就完成了对 SpringBoot2应用 的监控，我们可以在 HertzBeat 随时查看SpringBoot2应用的各种指标状态和可用性。 +通过上面我们就完成了对 SpringBoot2应用 的监控，我们可以在 HertzBeat 随时查看SpringBoot2应用的各种指标状态和可用性。 当然不可能人工一直实时查看指标，监控往往伴随着告警阈值，当 SpringBoot2应用 的性能指标超出我们的阈值或SpringBoot2应用本身异常时，能及时的通知到我们对应的负责人，负责人收到通知处理，这样才是一个完整的监控告警流程。 ::: @@ -125,9 +125,9 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea - 选择配置的指标对象，SpringBoot2应用 监控主要是 堆栈内存 线程等相关指标，我们举例对 `状态线程数` `threads` -> `threads` 这个指标进行阈值设置， 当`runnable`状态的线程数量大于300时发出告警。 - 这里我们就配置当此指标`size`,`state` 的 `equals(state,"runnable"") && size>300` 时发出告警，告警级别为**警告告警**，三次即触发，具体如下图。 - ![HertzBeat](/img/blog/monitor-springboot2-6.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-6.png) - ![HertzBeat](/img/blog/monitor-springboot2-7.png) + ![HertzBeat](home/static/img/blog/monitor-springboot2-7.png) 2. 新增消息通知接收人 @@ -142,13 +142,13 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 【告警通知】->【新增接收人】 ->【选择钉钉机器人通知方式】->【设置钉钉机器人ACCESS_TOKEN】-> 【确定】 - ![HertzBeat](/img/blog/alert-notice-1.png) + ![HertzBeat](home/static/img/blog/alert-notice-1.png) 3. 配置关联的告警通知策略⚠️ 【新增通知策略】-> 【将刚设置的接收人关联】-> 【确定】 > 配置告警通知策略，让告警消息与接收人绑定，这样就能决定哪些告警发给哪个人。 - ![HertzBeat](/img/blog/alert-notice-2.png) + ![HertzBeat](home/static/img/blog/alert-notice-2.png) ### 完毕，现在坐等告警消息过来啦。叮叮叮叮 @@ -165,7 +165,7 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea ## 小结 :::tip -这篇实践文章带我们体验了如何使用开源实时监控工具 HertzBeat 来监控 SpringBoot2应用 指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 SpringBoot2应用 纳入监控并告警通知，再也不需要部署多个组件编写配置文件那些繁琐操作了。 +这篇实践文章带我们体验了如何使用开源实时监控工具 HertzBeat 来监控 SpringBoot2应用 指标数据，可以发现集 `监控-告警-通知` 的 HertzBeat 在操作与使用方面更加的便捷，只需页面上简单点一点就能把 SpringBoot2应用 纳入监控并告警通知，再也不需要部署多个组件编写配置文件那些繁琐操作了。 ::: > 只需要一条docker命令即可安装体验heartbeat: @@ -176,7 +176,7 @@ Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 通过上面的简单步骤我们实现了对SpringBoot2的监控，但里面的内置指标固定不满足需要，是否能自定义监控更多SpringBoot2的指标呢？答案当然是可以的，通过在页面上的**监控定义**->**SpringBoot2**随时通过编辑如下的YML配置文件自定义添加修改想要监控的性能指标。 -![HertzBeat](/img/blog/monitor-springboot2-8.png) +![HertzBeat](home/static/img/blog/monitor-springboot2-8.png) ## What is HertzBeat? diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-07-05-hertzbeat-v1.3.2.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-07-05-hertzbeat-v1.3.2.md index 0fa264af00a..aad3f516e93 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-07-05-hertzbeat-v1.3.2.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-07-05-hertzbeat-v1.3.2.md @@ -1,15 +1,15 @@ --- title: 开源实时监控 HertzBeat v1.3.2 发布, 更稳定更易用 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- 官网: hertzbeat.com | tancloud.cn -![hertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## HertzBeat 介绍 > diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-14-hertzbeat-v1.4.0.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-14-hertzbeat-v1.4.0.md index 148e9cad50b..563fd48286e 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-14-hertzbeat-v1.4.0.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-14-hertzbeat-v1.4.0.md @@ -1,13 +1,13 @@ --- -title: 重磅更新，HertzBeat 集群版发布，易用友好的开源实时监控系统! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: 重磅更新，HertzBeat 集群版发布，易用友好的开源实时监控系统! +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- -![hertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## 什么是 HertzBeat? @@ -23,7 +23,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] > `HertzBeat`的强大自定义，多类型支持，高性能，易扩展，低耦合，希望能帮助开发者和团队快速搭建自有监控系统。 -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** @@ -42,17 +42,17 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] - 监控任务在采集器集群中自调度，单采集器挂掉无感知故障迁移采集任务，新加入采集器节点自动调度分担采集压力。 - 单机模式与集群模式相互切换部署非常方便，无需额外组件部署。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) #### 云边协同 > 支持部署边缘采集器集群，与主 HertzBeat 服务云边协同提升采集能力。 -在多个网络不相通的隔离网络中，在以往的方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 -HertzBeat 提供云边协同能力，可以在多个隔离网络部署边缘采集器，添加监控时指定采集器，采集器在隔离网络内部进行监控任务采集，采集数据上报，由主 HertzBeat 服务统一调度管理展示。 +在多个网络不相通的隔离网络中，在以往的方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 +HertzBeat 提供云边协同能力，可以在多个隔离网络部署边缘采集器，添加监控时指定采集器，采集器在隔离网络内部进行监控任务采集，采集数据上报，由主 HertzBeat 服务统一调度管理展示。 这多用于多个隔离数据中心或不同厂商云资源和云下资源的统一监控场景。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 为什么要开源集群版? diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-28-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-28-new-committer.md index f4c98f326a6..13a2dc71f3f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-28-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-08-28-new-committer.md @@ -1,13 +1,13 @@ --- title: 热烈欢迎 HertzBeat 小伙伴新晋社区 Committer! -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) 很高兴迎来了新的社区`Committer`，和其它贡献者不一样的是`logicz`来自讯飞的运维实施岗位而不是开发岗位，但不管是代码还是文档等贡献质量都非常高👍。这也是我们`HertzBeat`与其它开源项目不一样的地方，因为用户群体更多面向运维开发，在我们139位贡献者中运维工程师的占比超30%，这打破了开源项目的协作贡献对象都是开发岗位的固有认知，这说明不管是运维工程师还是测试工程师对开源项目的贡献参与都是非常热情的，而不仅仅只是作为开源协作的旁观者。开源项目的参与并不是只专属于某一类人群，而是面向所有的想来参与的人，可能是一篇文档，一个脚本或者一段代码，想象一下你参与的开源项目被部署到成千上万的服务器上运行跑起来，帮助到他人被使用或者浏览Review讨论，git记录永留存，这也许就是参与开源项目的意义。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-09-26-hertzbeat-v1.4.1.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-09-26-hertzbeat-v1.4.1.md index 319e80135a0..023f3e121bc 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-09-26-hertzbeat-v1.4.1.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-09-26-hertzbeat-v1.4.1.md @@ -1,8 +1,8 @@ --- title: 更好的用户体验, 开源实时监控 HertzBeat v1.4.1 发布 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- @@ -10,7 +10,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] 哈喽大家好，时间很快两个月又过去了，HertzBeat 经过近两个月的迭代终于发布了 v1.4.1 版本。为什么是终于，因为有点难哈哈。我们参考 rocketmq 重构了 netty 的 server client 端模块，重构了采集器集群调度。比起上一版本有了更优雅的通讯代码，更完善全面的集群。 采集任务一致性hash调度，集群心跳保活，断开主动重连，主动上线下线，主动停机等等这些都有。设计了新的控制台登陆界面和欢迎页面，支持了采集器集群的UI管理，合并了开源之夏两位同学的帮助提示头特性和阈值表达式特性，很多用户需要的监控指标名称国际化等等，最重要的当然是修复若干BUG，体验下来确实增强了用户体验。 -![hertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## 总结起来如下 @@ -59,7 +59,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] > `HertzBeat`的强大自定义，多类型支持，高性能，易扩展，低耦合，希望能帮助开发者和团队快速搭建自有监控系统。 -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-11-12-hertzbeat-v1.4.2.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-11-12-hertzbeat-v1.4.2.md index 1bfa2b064fb..a805541fcd6 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-11-12-hertzbeat-v1.4.2.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-11-12-hertzbeat-v1.4.2.md @@ -1,15 +1,15 @@ --- -title: HertzBeat v1.4.2 版本发布，自定义消息通知模板 -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat v1.4.2 版本发布，自定义消息通知模板 +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source monitoring system, alerting system, Linux monitoring] --- 哈喽大家好，开源实时监控 HertzBeat 新版本 v1.4.2 发布，欢迎了解使用。 -![hertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ## 总结起来如下 @@ -36,7 +36,7 @@ keywords: [open source monitoring system, alerting system, Linux monitoring] > `HertzBeat`的强大自定义，多类型支持，高性能，易扩展，低耦合，希望能帮助开发者和团队快速搭建自有监控系统。 -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-01-11-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-01-11-new-committer.md index 17b1c6394e5..4347c3876de 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-01-11-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-01-11-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > 热烈欢迎 HertzBeat 有三位小伙伴新晋社区 Committer, 让我们来了解下他们的开源经历吧！ diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-04-17-to-apache.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-04-17-to-apache.md index 971229a8244..676b18facb3 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-04-17-to-apache.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-04-17-to-apache.md @@ -11,9 +11,9 @@ keywords: [open source monitoring system, alerting system] HertzBeat 于 2022 年 1 月在 Dromara 开源社区正式开源，经过两年多的社区小伙伴们的不间断项目维护迭代，持续的社区成长，现在，HertzBeat 正式官宣加入 Apache 孵化器！ -![HertzBeat](/img/blog/apache-incubator-1.png) +![HertzBeat](home/static/img/blog/apache-incubator-1.png) -![HertzBeat](/img/blog/apache-incubator-2.png) +![HertzBeat](home/static/img/blog/apache-incubator-2.png) 加入 Apache 孵化器不是终点，这是项目的全新起点。加入 Apache 孵化器后，在社区层面，HertzBeat 将积极践行『开放、协作』 的 Apache 之道，持续构建一个公平，多元，包容的开源社区。在开源产品层面，倾听用户声音，提升优化产品使用体验，打造对接开源生态。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-06-15-hertzbeat-v1.6.0.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-06-15-hertzbeat-v1.6.0.md index 60a21e8725a..c0cdebd4c07 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-06-15-hertzbeat-v1.6.0.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-06-15-hertzbeat-v1.6.0.md @@ -1,8 +1,8 @@ --- -title: HertzBeat 的第一个 Apache 版本 v1.6.0 发布！ -author: tom -author_title: tom -author_url: https://github.com/tomsun28 +title: HertzBeat 的第一个 Apache 版本 v1.6.0 发布！ +author: tom +author_title: tom +author_url: https://github.com/tomsun28 tags: [opensource, practice] keywords: [open source, monitoring, alerting] --- @@ -36,7 +36,7 @@ keywords: [open source, monitoring, alerting] > `HertzBeat`的强大自定义，多类型支持，高性能，易扩展，低耦合，希望能帮助用户快速搭建自有监控系统。 -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-07-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-07-new-committer.md index a35e5764f22..630ab13f043 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-07-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-07-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > 🎉非常高兴成为 Apache HertzBeat™ 项目的 Committer，受社区邀请来做一个自我介绍🥰。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-08-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-08-new-committer.md index 450cfd17572..862186426a3 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-08-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-08-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) ## 初识 Apache HertzBeat diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-15-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-15-new-committer.md index 0287a62b28b..cb9968332a3 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-15-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-15-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) 大家好，非常荣幸可以收到社区邀请被提名为 Apache HertzBeat™ 的 Committer。我先做一个简单的自我介绍，从2019年工作开始，一直从事后端开发工作，主要使用Java语言，目前在一家网络安全公司从事网络安全相关产品后端开发工作。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-27-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-27-new-committer.md index 69f4a70fa2b..03c42e5e624 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-27-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-27-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > 非常荣幸能成为Apache HertzBeat的Committer diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-28-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-28-new-committer.md index 14a603a8cc9..9c62bedbdc6 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-28-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-28-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > 非常荣幸能成为Apache HertzBeat的Committer > diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-29-new-committer.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-29-new-committer.md index fe607d839a0..9aae7bb5aba 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-29-new-committer.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2024-07-29-new-committer.md @@ -7,7 +7,7 @@ tags: [opensource, practice] keywords: [open source monitoring system, alerting system] --- -![hertzBeat](/img/blog/new-committer.png) +![HertzBeat](home/static/img/blog/new-committer.png) > 非常荣幸能成为Apache HertzBeat的Committer diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-08-24-hertzbeat-graduation.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-08-24-hertzbeat-graduation.md index 2ddf951ecc1..c55a05c6e48 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-08-24-hertzbeat-graduation.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-08-24-hertzbeat-graduation.md @@ -17,7 +17,7 @@ tags: [opensource, apache] [Apache HertzBeat](https://github.com/apache/hertzbeat) 是一个易用友好的开源实时监控告警系统，无需 Agent，高性能集群，兼容 Prometheus，提供强大的自定义监控和状态页构建能力。 -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) ### 特点 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-hertzbeat.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-hertzbeat.md index f99807576ba..db74cfbd148 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-hertzbeat.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-hertzbeat.md @@ -1,6 +1,6 @@ --- id: extend-http-example-hertzbeat -title: 教程一:适配一款基于HTTP协议的监控类型 +title: 教程一:适配一款基于HTTP协议的监控类型 sidebar_label: 教程一:适配一款HTTP协议监控 --- @@ -188,25 +188,25 @@ metrics: **新增完毕，现在我们重启hertzbeat系统。我们可以看到系统页面已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 系统页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常的设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-token.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-token.md index 674f2b56e02..e7b2bdd14f0 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-token.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http-example-token.md @@ -1,6 +1,6 @@ --- id: extend-http-example-token -title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 +title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 sidebar_label: 教程二:获取TOKEN后续认证使用 --- @@ -221,13 +221,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **新增成功后我们就可以在详情页面看到我们采集的 `token`, `refreshToken`指标数据。** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### 将`token`作为变量参数给后面的监控指标采集使用 @@ -381,15 +381,15 @@ metrics: **配置完成后，再次重启 `hertzbeat` 系统，查看监控详情页面** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http.md index 65a740c5a4c..e8aa27520be 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-http.md @@ -1,6 +1,6 @@ --- -id: extend-http -title: HTTP协议自定义监控 +id: extend-http +title: HTTP协议自定义监控 sidebar_label: HTTP协议自定义监控 --- @@ -20,7 +20,7 @@ HTTP协议支持我们自定义HTTP请求路径，请求header，请求参数， **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jdbc.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jdbc.md index c1e6545e4f4..50a56c366ca 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jdbc.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jdbc.md @@ -1,6 +1,6 @@ --- -id: extend-jdbc -title: JDBC协议自定义监控 +id: extend-jdbc +title: JDBC协议自定义监控 sidebar_label: JDBC协议自定义监控 --- @@ -57,7 +57,7 @@ SQL响应数据： **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jmx.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jmx.md index b4dadf8cfde..b906de82547 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jmx.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-jmx.md @@ -1,6 +1,6 @@ --- -id: extend-jmx -title: JMX协议自定义监控 +id: extend-jmx +title: JMX协议自定义监控 sidebar_label: JMX协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: JMX协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ngql.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ngql.md index 23b404986c5..93751b7a678 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ngql.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ngql.md @@ -13,18 +13,18 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 ### **filterCount** > -> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 -> commands字段语法格式: aliasField#NGQL#filterName#filterValue -> `aliasField`: 对应监控模板中的`aliasFields`中的值 -> `NGQL`: 查询语句 -> `filterName`: 过滤属性名称（可选） +> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 +> commands字段语法格式: aliasField#NGQL#filterName#filterValue +> `aliasField`: 对应监控模板中的`aliasFields`中的值 +> `NGQL`: 查询语句 +> `filterName`: 过滤属性名称（可选） > `filterValue`: 过滤属性值（可选） 例如： -- online_meta_count#SHOW HOSTS META#Status#ONLINE +- online_meta_count#SHOW HOSTS META#Status#ONLINE 对 `SHOW HOSTS META` 返回的结果中统计滤Status==ONLINE的数量 -- online_meta_count#SHOW HOSTS META## +- online_meta_count#SHOW HOSTS META## 统计 `SHOW HOSTS META` 返回的行数 #### **oneRow** @@ -50,7 +50,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 例如： -- 查询的指标字段为：a,b +- 查询的指标字段为：a,b - 查询NGQL：match (v:metrics) return v.metrics.a as a,v.metrics.b as b; 这里指标字段就能和响应数据一一映射为多行采集数据。 @@ -71,7 +71,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -168,7 +168,7 @@ metrics: parseType: columns # 定义采集数据使用的查询语句 commands: - - match (v:tag1) return "tag1" as name ,count(v) as cnt + - match (v:tag1) return "tag1" as name ,count(v) as cnt - match (v:tag2) return "tag2" as name ,count(v) as cnt timeout: ^_^timeout^_^ ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-point.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-point.md index 45e56692693..e4476822739 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-point.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-point.md @@ -1,17 +1,17 @@ --- -id: extend-point -title: 自定义监控 +id: extend-point +title: 自定义监控 sidebar_label: 自定义监控 --- -> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 +> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 > 目前自定义监控支持[HTTP协议](extend-http)，[JDBC协议](extend-jdbc)，[SSH协议](extend-ssh)，[JMX协议](extend-jmx)，[SNMP协议](extend-snmp)，后续会支持更多通用协议。 ## 自定义流程 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ### 自定义监控指标刷新时间 @@ -139,7 +139,7 @@ params: # hide param-true or false # 是否隐藏字段 true or false hide: true - + metrics: # metrics - summary, inner monitoring metrics (responseTime - response time, keyword - number of keywords) # 监控指标 - summary, 内置监控指标有 (responseTime - 响应时间, keyword - 关键字数量) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-push.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-push.md index d938b5cddfb..6b1d59b4112 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-push.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat页面 -> 应用服务监控 -> 推送方式监控 -> 新建推送方 ### 监控配置示例 -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-snmp.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-snmp.md index 018feed6f46..b24c30c5e9c 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-snmp.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-snmp.md @@ -1,6 +1,6 @@ --- -id: extend-snmp -title: SNMP协议自定义监控 +id: extend-snmp +title: SNMP协议自定义监控 sidebar_label: SNMP协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: SNMP协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ssh.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ssh.md index 9b19f2ae987..b1e2020c294 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ssh.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-ssh.md @@ -1,6 +1,6 @@ --- -id: extend-ssh -title: SSH协议自定义监控 +id: extend-ssh +title: SSH协议自定义监控 sidebar_label: SSH协议自定义监控 --- @@ -31,7 +31,7 @@ SHELL脚本查询回来的数据字段和我们需要的指标映射，就能获 ```shell tombook -14:00:15 up 72 days +14:00:15 up 72 days ``` 则最后采集到的指标数据一一映射为： @@ -54,7 +54,7 @@ Mem: 7962 4065 333 1 3562 3593 Swap: 8191 33 8158 ``` -在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： +在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： `free -m | grep Mem | awk 'BEGIN{print "total used free buff_cache available"} {print $2,$3,$4,$6,$7}'` 控制台响应为： @@ -69,7 +69,7 @@ total used free buff_cache available **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-telnet.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-telnet.md index dfaf2a5a714..34185e8e3c4 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-telnet.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-telnet.md @@ -1,6 +1,6 @@ --- -id: extend-telnet -title: Telnet协议自定义监控 +id: extend-telnet +title: Telnet协议自定义监控 sidebar_label: Telnet协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: Telnet协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-tutorial.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-tutorial.md index eecf853395c..2cd49874487 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-tutorial.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/advanced/extend-tutorial.md @@ -1,6 +1,6 @@ --- id: extend-tutorial -title: 自定义适配一款基于HTTP协议的新监控类型 +title: 自定义适配一款基于HTTP协议的新监控类型 sidebar_label: 教程案例 --- @@ -227,25 +227,25 @@ metrics: **点击保存并应用。我们可以看到系统页面的自定义监控菜单已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/new_committer_process.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/new_committer_process.md index aa4cb00058d..4180ddb8024 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/new_committer_process.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/new_committer_process.md @@ -355,15 +355,15 @@ hi, i accept. Thanks for invitaion. 找到`CLAs`点击进入页面 - ![HertzBeat](/img/docs/community/clas-web.png) + ![HertzBeat](home/static/img/docs/community/clas-web.png) 找到`ICLA(个人贡献者许可协议)`，点击[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) - ![HertzBeat](/img/docs/community/icla-web.png) + ![HertzBeat](home/static/img/docs/community/icla-web.png) 跳转后，会显示需要签署的协议，这里可以在网页上直接填写，也可以下载后填写。 - ![HertzBeat](/img/docs/community/icla-pdf.png) + ![HertzBeat](home/static/img/docs/community/icla-pdf.png) 2. 填写iCLA @@ -371,8 +371,8 @@ hi, i accept. Thanks for invitaion. 需要填写的内容： - ![HertzBeat](/img/docs/community/icla-content-1.png) - ![HertzBeat](/img/docs/community/icla-content-2.png) + ![HertzBeat](home/static/img/docs/community/icla-content-1.png) + ![HertzBeat](home/static/img/docs/community/icla-content-2.png) 在PDF中需要填写的字段： @@ -386,12 +386,12 @@ hi, i accept. Thanks for invitaion. - `Date` > 填写样例 - > ![HertzBeat](/img/docs/community/icla-content-3.png) - > ![HertzBeat](/img/docs/community/icla-content-4.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-3.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-4.png) 3. 打印并签署 - ![HertzBeat](/img/docs/community/icla-content-5.png) + ![HertzBeat](home/static/img/docs/community/icla-content-5.png) `Please sign`字段需要将文件打印出来然后手写签名，内容为自己姓名的全拼。 @@ -423,7 +423,7 @@ hi, i accept. Thanks for invitaion. 在网站 [https://id.apache.org/reset/enter](https://id.apache.org/reset/enter) 输入您的Apache ID -![HertzBeat](/img/docs/community/account-1.png) +![HertzBeat](home/static/img/docs/community/account-1.png) 点击`Send Email`后会提示发送成功。 @@ -437,44 +437,44 @@ hi, i accept. Thanks for invitaion. 登录后可以看到这个内容`Link GitHub username to ASF id`，点击跳转 -![HertzBeat](/img/docs/community/account-2.png) +![HertzBeat](home/static/img/docs/community/account-2.png) 输入您的Apache的账号和密码并登录 -![HertzBeat](/img/docs/community/account-3.png) +![HertzBeat](home/static/img/docs/community/account-3.png) 点击 `Authenticate with GitHub` -![HertzBeat](/img/docs/community/account-4.png) +![HertzBeat](home/static/img/docs/community/account-4.png) 点击`Authorize apache`授权给Apache -![HertzBeat](/img/docs/community/account-5.png) +![HertzBeat](home/static/img/docs/community/account-5.png) 点击`Send GitHub Invitation!` 发送GitHub邀请邮件 -![HertzBeat](/img/docs/community/account-6.png) +![HertzBeat](home/static/img/docs/community/account-6.png) 邮箱中会收到一封邮件，点击`Join @apache` > 这里邮箱指的是您提供给PMC的那个邮箱地址 -![HertzBeat](/img/docs/community/account-7.png) +![HertzBeat](home/static/img/docs/community/account-7.png) 点击`Join The Apache Software Foundation`，加入GitHub加入Apache组织，会自动跳转到GitHub页面 -![HertzBeat](/img/docs/community/account-8.png) -![HertzBeat](/img/docs/community/account-9.png) +![HertzBeat](home/static/img/docs/community/account-8.png) +![HertzBeat](home/static/img/docs/community/account-9.png) 回到Apache页面，提示GitHub启用多重身份认证，在GitHub页面启用双重身份认证 > GitHub双重身份认证介绍，[点击跳转官方文档](https://docs.github.com/zh/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication) -![HertzBeat](/img/docs/community/account-10.png) +![HertzBeat](home/static/img/docs/community/account-10.png) 启动完成之后等几分钟，提示已经绑定完成 -![HertzBeat](/img/docs/community/account-11.png) +![HertzBeat](home/static/img/docs/community/account-11.png) 至此您的GitHub账号与Apache账号就绑定完成了。 @@ -488,17 +488,17 @@ hi, i accept. Thanks for invitaion. 进入设置页面，并点击`添加其他电子邮件地址`` -![HertzBeat](/img/docs/community/email-1.png) +![HertzBeat](home/static/img/docs/community/email-1.png) 填写您的apache邮箱，按照指引点击下一步 -![HertzBeat](/img/docs/community/email-2.png) -![HertzBeat](/img/docs/community/email-3.png) -![HertzBeat](/img/docs/community/email-4.png) +![HertzBeat](home/static/img/docs/community/email-2.png) +![HertzBeat](home/static/img/docs/community/email-3.png) +![HertzBeat](home/static/img/docs/community/email-4.png) 设置为默认发送邮箱(可选) -![HertzBeat](/img/docs/community/email-5.png) +![HertzBeat](home/static/img/docs/community/email-5.png) 配置完成。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_threshold.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_threshold.md index 050ef5d7296..1caaa7eb96a 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_threshold.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/alert_threshold.md @@ -24,7 +24,7 @@ sidebar_label: 阈值规则 配置阈值，例如: 选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) 配置项说明： diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/collector.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/collector.md new file mode 100644 index 00000000000..0b89bc3a6fd --- /dev/null +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/collector.md @@ -0,0 +1,131 @@ +--- +id: collector +title: HertzBeat 采集器 +sidebar_label: 采集器 +keywords: [监控, 可观测性, 采集器, 指标] +--- + +> HertzBeat 采集器是一个轻量级数据采集模块，支持指标采集、高可用部署和云边协同。 + +## 简介 + +HertzBeat 采集器是 Apache HertzBeat™ 监控系统中一个多功能且轻量级的指标采集模块。它负责从各类监控目标采集数据，并将采集到的指标发送至 HertzBeat 主服务器进行加工、告警和可视化。 + +借助采集器模块，您可以实现： + +- **高可用**：部署多个采集器，即使部分实例故障也能持续监控 +- **负载均衡**：将监控任务分发到多个采集器，提升性能 +- **云边协同**：在隔离网络中监控资源，同时从中央 HertzBeat 服务器统一管理 + +## 采集器架构 + +采集器模块采用模块化设计，便于扩展以适配各种监控场景。其架构包括： + +1. **采集器入口**：采集器模块的主入口，启动后执行采集任务。 + +2. **collector-basic**：包含 HTTP、JDBC、SSH、SNMP 等常见协议的实现。这类采集器通常不需要额外的专有依赖，可满足大部分基础监控需求。 + +3. **collector-common**：提供通用工具类和方法，如连接池、缓存机制等，供其他模块复用。 + +4. **collector-xxx**：针对特定服务或协议的扩展模块（MongoDB、RocketMQ、Kafka、NebulaGraph 等）。这些模块通常需要引入对应服务的特定依赖。 + +## 支持的协议 + +HertzBeat 采集器支持丰富的监控协议： + +| 协议类别 | 协议 | +| ---------- | ----------------------------------------------------------------- | +| Web/API | `http`, `ssl_cert`, `websocket` | +| 数据库 | `jdbc`, `redis`, `mongodb`, `memcached` | +| 操作系统 | `ssh`, `ipmi` | +| 网络 | `icmp` (ping), `telnet`, `snmp`, `modbus` | +| 消息队列 | `mqtt`, `rocketmq`, `kafka` | +| 邮件 | `pop3`, `smtp`, `imap` | +| 云服务 | `prometheus`, `nebulagraph`, `ngql` | +| 其他 | `jmx`, `dns`, `ftp`, `ntp`, `udp`, `nginx`, `redfish`, `script`, `registry`, `httpsd` | + +## 部署方式 + +登录 HertzBeat Web 界面后进入采集器页面，即可查看部署选项。根据您的环境和需求，可通过以下方式部署 HertzBeat 采集器： + +参数说明： + +- `-e IDENTITY=custom-collector-name`：（可选）为采集器设置唯一标识，所有采集器中必须唯一。 +- `-e MODE=public`：设置运行模式（public 或 private），分别用于公共集群或私有云边模式。 +- `-e MANAGER_HOST=192.168.1.100`：**重要！** 设置 HertzBeat 主服务器的 IP 地址，请替换为实际 IP。 +- `-e MANAGER_PORT=1158`：（可选）设置 HertzBeat 主服务器端口，默认 1158。 +- `-v $(pwd)/logs:/opt/hertzbeat-collector/logs`：（可选）将日志文件挂载到本地主机。 + +## 运行模式 + +HertzBeat 采集器支持两种运行模式： + +### 公共模式（集群模式） + +公共模式下，采集器与 HertzBeat 主服务器组成集群。任务会自动在采集器间分发，实现高可用和负载均衡。 + +- 部署时设置 `MODE=public` +- 所有采集器必须与 HertzBeat 主服务器网络连通 +- 适合通过水平扩展处理大量监控任务 + +### 私有模式（云边模式） + +私有模式下，采集器在隔离网络中运行，但仍向中央 HertzBeat 服务器上报数据。可实现对多个独立网络资源的监控。 + +- 部署时设置 `MODE=private` +- 采集器需要能出网访问 HertzBeat 服务器，但无需入网连通 +- 适合跨数据中心、多云提供商或不同网段的资源监控 + +## 配置参数 + +| 参数 | 说明 | 默认值 | +| -------------- | ------------------------ | ------------------ | +| `identity` | 采集器唯一标识 | 未设置时自动生成 | +| `mode` | 运行模式（public/private）| public | +| `manager-host` | HertzBeat 服务器 IP 地址 | IP | +| `manager-port` | HertzBeat 服务器端口 | 1158 | + +## 采集器管理 + +您可通过 HertzBeat Web 界面管理采集器： + +1. 进入概览页面查看所有已注册采集器 +2. 监控采集器状态（在线/离线）、指标任务和系统信息 +3. 按需启用或禁用采集器 + +## 高可用配置 + +使用 HertzBeat 采集器实现高可用： + +1. 在不同服务器或容器中部署多个采集器实例 +2. 确保所有采集器使用相同的 `mode` 设置 +3. 将所有采集器连接到同一个 HertzBeat 服务器 +4. HertzBeat 会自动分发监控任务并处理故障转移 + +若某个采集器离线，其任务将被重新分配给其他可用采集器。当该采集器恢复在线后，会根据当前负载重新接收新任务。 + +## 云边协同 + +跨隔离网络监控的配置步骤： + +1. 在中心管理网络部署 HertzBeat 服务器 +2. 在每个需要监控的隔离网络中部署采集器 +3. 配置采集器参数： + - `MODE=private` + - `MANAGER_HOST=` 指向中心 HertzBeat 服务器 +4. 确保每个隔离网络到中心服务器的出网连通 +5. 在中心 HertzBeat 仪表板统一管理所有监控任务 + +## 高级功能 + +### 自定义协议支持 + +HertzBeat 的架构支持扩展采集器以支持自定义协议。开发者可按照项目的模块化设计创建新的采集器模块。 + +### 任务调度 + +采集器根据任务优先级、可用资源和当前系统负载自动进行任务调度。通过智能优先级确保关键监控优先执行。 + +### 资源利用 + +采集器设计轻量高效，适合从小型边缘设备到高性能服务器等各种硬件环境部署。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/mysql_account_expiry.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/mysql_account_expiry.md new file mode 100644 index 00000000000..3cc9359efd1 --- /dev/null +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/mysql_account_expiry.md @@ -0,0 +1,24 @@ +--- +id: mysql_account_expiry +title: "监控：MySQL 账户过期" +sidebar_label: "MySQL 账户过期" +keywords: + - mysql 账户过期 + - mysql 密码过期 + - mysql 安全监控 +--- + +> 监控 MySQL 数据库账户密码过期信息。 + +## 采集指标 + +### 指标集合：account_expiry + +| 指标名称 | 指标单位 | 指标帮助说明 | +|-----------------------|----------|------------------------------------------| +| user | 无 | MySQL 账户用户名 | +| host | 无 | 允许该账户连接的主机 | +| password_lifetime | 天 | 密码有效期（天） | +| password_last_changed | 时间戳 | 上次修改密码的时间 | +| password_expired | 无 | 账户密码是否已过期（true/false） | +| days_left | 天 | 距离密码过期的剩余天数 | diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/redis_cluster.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/redis_cluster.md index 7d20acff065..17e8ddd513f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/redis_cluster.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/redis_cluster.md @@ -1,7 +1,7 @@ --- -id: redis_cluster -title: 监控：Redis Cluster 数据库监控 -sidebar_label: Redis Cluster数据库 +id: redis_cluster +title: 监控：Redis Cluster 数据库监控 +sidebar_label: Redis Cluster数据库 keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监控] --- @@ -98,7 +98,7 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 添加监控节点时填入所需要的参数. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) 最终的效果. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/registry.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/registry.md new file mode 100644 index 00000000000..c51991a0765 --- /dev/null +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/registry.md @@ -0,0 +1,51 @@ +--- +id: registry +title: 注册中心监控 +sidebar_label: 注册中心监控 +keywords: [开源监控工具, 开源 Java 监控工具, 注册中心监控指标] +--- + +> 采集并监控注册中心的通用性能指标。 + +**使用协议：registry** + +## 监控微服务步骤 + +1. 确保您的**注册中心**可用 + + > 当前支持 `Consul` 和 `Nacos`。 + +2. 在 HertzBeat 上新增 http_sd 监控，填写**注册中心**的必要信息，如主机、端口等。 +3. 点击**确定** + +## 配置参数 + +| 参数名称 | 参数帮助描述 | +|----------------|------------------------------------------------------------------------------| +| 主机 | 被监控的 IPV4、IPV6 或域名。注意⚠️不含协议头（如：https://、http://） | +| 任务名称 | 标识本次监控的名称，名称需唯一 | +| 端口 | 注册中心提供的端口 | +| 发现客户端类型 | 选择要监控的注册中心 | +| 采集间隔 | 监控周期性数据采集的时间间隔，单位：秒，最小可设置间隔为 30 秒 | +| 是否探测 | 新增监控前是否进行探测检查。探测成功后才继续新增和修改操作 | +| 描述备注 | 用于标识和描述此监控的更多信息，用户可在此备注信息 | + +## 采集指标 + +## 指标集合：server + +| 指标名称 | 指标单位 | 指标帮助描述 | +|------------|----------|--------------| +| 地址 | | | +| 端口 | | | +| 响应时间 | ms | | + +## 指标集合：service + +| 指标名称 | 指标单位 | 指标帮助描述 | +|------------|----------|------------------| +| 服务 ID | | | +| 服务名称 | | | +| 地址 | | | +| 端口 | | | +| 健康状态 | | 服务的当前健康状态 | diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/status.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/status.md index bbb55bd3c9f..931c669ecd7 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/status.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: 状态页面 -sidebar_label: 状态页面 +id: status +title: 状态页面 +sidebar_label: 状态页面 keywords: [开源监控系统, 开源网站监控, 状态页面] --- @@ -24,7 +24,7 @@ keywords: [开源监控系统, 开源网站监控, 状态页面] 填写完组织信息后，点击 `确定`。 -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. 新增组件 @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. 维护事件 @@ -59,7 +59,7 @@ status: 点击 `发布事件` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | 字段名称 | 字段说明 | 举例 | |------|---------------------------------------------|----------------------------------------------------------------------| @@ -70,4 +70,4 @@ status: > 提示：可以多次发布消息，及时向团队汇报当前状态。 -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/template_marketplace.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/template_marketplace.md new file mode 100644 index 00000000000..9f865c6448d --- /dev/null +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/template_marketplace.md @@ -0,0 +1,152 @@ +--- +id: template_marketplace +title: 模板市场 +sidebar_label: 模板市场 +--- + +> HertzBeat 官方模板市场：用户可自由上传、下载、查看、搜索和分享监控模板文件。 + +## 基础功能 + +### 搜索 + +💡 访客可用 + +> 展示模板名称、简介、收藏数、下载数、浏览数等信息 + +1. **无筛选：按上传顺序展示** + + ![search.png](/img/template-marketplace/search.png) + +2. **按类别筛选：当前分为六个类别** + + > **📋待办：** 开发标签功能，在类别内进一步细分，如数据库监控模板可分为 MySQL、Oracle 等。 + + ![search-category.png](/img/template-marketplace/search-category.png) + +3. **按标题模糊搜索** + + ![search-name.png](/img/template-marketplace/search-name.png) + +4. **悬浮窗功能：下载最新版本、查看详情、收藏/取消收藏** + + > 登录后显示用户是否已收藏 + + ![img.png](/img/template-marketplace/hover-window-guest.png)![img_1.png](/img/template-marketplace/hover-window-user.png) + +5. **排序：八种排序方式** + + > **📋待办：** 等待实际安装 + +### 模板详情 + +💡 访客可用 + + > 展示模板的基本信息，如名称、作者、更新时间、版本信息等。 + +1. **信息：概要信息、详细信息及其他信息** + + > **📋待办：** 升级为 Markdown 格式 + + ![img.png](/img/template-marketplace/detail-info.png) + +2. **版本：历史版本下载、分享及基本信息展示** + + > **📋待办：** 设置各历史版本的查看功能，展示版本描述等信息。 + + ![img.png](/img/template-marketplace/detail-version.png) + +3. **常见问题** + + > **📋待办：** 讨论或 issue 问答区 + + ![img.png](/img/template-marketplace/detail-faq.png) + +4. **下载** + + > 可直接从列表悬浮窗下载最新版本。 + > 也可直接从模板详情页下载最新版本。 + > 可从版本页下载历史版本。 + + ![img.png](/img/template-marketplace/download.png) + +5. **分享** + + > 模板详情页可分享最新版本。 + > 版本页可分享历史版本。 + > 分享会自动将分享 URL 复制到剪贴板，被分享者可通过该 URL 下载文件。 + > + > **📋待办：** 通过分享模板的 URL 访问共享模板详情页，被分享者可自由选择是否下载。 + + ![img.png](/img/template-marketplace/share.png) + +### 用户中心 + +💡 用户可用 + + > 提供资产管理、收藏管理和上传功能。 +> + > **📋待办：** 概览页、通知页、用户设置页 + +1. **资产：管理用户自己上传的所有模板** + + > 提供下载最新版本和查看详情的能力。 + > + > **📋待办：** 更新模板信息功能 + + ![img_1.png](/img/template-marketplace/user-center-asset.png) + + ![img.png](/img/template-marketplace/asset-detail.png) + +2. **版本升级** + + > 用户在该模板族下定义新版本号，更新版本信息，并上传最新版本的文件。 + + ![img.png](/img/template-marketplace/asset-upgrade.png) + +3. **收藏** + + ![img.png](/img/template-marketplace/user-center-star.png) + + ![img.png](/img/template-marketplace/user-center-star-detail.png) + +4. **上传** + + > 创建新的模板系列并上传第一个版本的文件。 + > + > 填写模板名称，选择模板类别，填写描述信息和版本信息，并上传文件。 + + ![img.png](/img/template-marketplace/user-center-upload.png) + +### 注册与登录 + +💡 访客可用 + +1. **注册** + + > 用户名可重复，但邮箱地址唯一。 + > + > **📋待办：** 验证码功能、邮箱验证功能 + + ![img.png](/img/template-marketplace/sign-up.png) + +2. **登录** + + > **📋待办：** 验证码功能和忘记密码功能 + + ![img.png](/img/template-marketplace/email-login.png) + +## 开发步骤 + + > 分别下载 `template-marketplace/hertzbeat-template-hub` 和 `template-marketplace/hertzbeat-template-hub-web-app` 项目 + + 前端项目按照 README.md 直接启动即可。 + + 后端项目步骤： + + 1. 在 `template-marketplace/hertzbeat-template-hub/sql` 中运行 `sql` 脚本创建数据库表 + 2. 安装 MinIO + 3. 在 `application.yml` 中配置 `MySQL` 和 `MinIO` + 4. 启动后端项目 + +其他问题可通过交流群或 ISSUE 反馈！ diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/introduce.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/introduce.md index 62dc34b7ff3..8ef4932fe2a 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/introduce.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/introduce.md @@ -66,11 +66,11 @@ HertzBeat 统一四个监控功能： HertzBeat 自身并没有去创造一种采集数据协议让监控对端来适配它。而是充分使用了现有的生态，`SNMP协议`采集网络交换机路由器信息，`JMX规范`采集JAVA应用信息，`JDBC规范`采集数据集信息，`SSH`直连执行脚本获取回显信息，`HTTP+(JsonPath | prometheus等)`解析API接口信息，`IPMI协议`采集服务器信息等等。 HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可配置化，最后使其都可以通过编写YML格式监控模板的形式，来制定模板使用这些协议来采集任何想要的指标数据。 -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) 你相信用户只需在UI页面编写一个监控模板，点击保存后，就能立刻适配一款`K8s`或`Docker`等新的监控类型吗？ -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 内置监控类型 @@ -121,7 +121,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 > 我们将每个监控类型都视为一个监控模板，不管是官方内置的还是后期用户自定义新增的。用户都可以方便的通过修改监控模板来新增修改删除监控指标。 > 模板里面包含各个协议的使用配置，环境变量，指标转换，指标计算，单位转换，指标采集等一系列功能，帮助用户能采集到自己想要的监控指标。 -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### 无需 Agent @@ -143,7 +143,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 - 监控任务在采集器集群中自调度，单采集器挂掉无感知故障迁移采集任务，新加入采集器节点自动调度分担采集压力。 - 单机模式与集群模式相互切换部署非常方便，无需额外组件部署。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 云边协同 @@ -154,7 +154,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 在多个网络不相通的隔离网络中，在以往方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 `HertzBeat` 提供的云边协同能力，可以在多个隔离网络部署边缘采集器，采集器在隔离网络内部进行监控任务采集，采集数据上报，由主服务统一调度管理展示。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 易用友好 @@ -189,7 +189,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - HertzBeat 的用户管理统一由配置文件 `sureness.yml` 维护，用户可以通过修改此文件来新增删除修改用户信息，用户角色权限等。默认账户密码 admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### 概览页面 @@ -197,7 +197,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 展示当前注册的采集器集群状态，包括采集器的上线状态，监控任务，启动时间，IP地址，名称等。 - 下发展示了最近告警信息列表，告警级别分布情况等。 -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### 监控中心 @@ -244,7 +244,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### 新增监控 @@ -252,7 +252,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 页面上配置的监控参数由对应监控类型的监控模板所定义，用户可以通过修改监控模板来修改页面配置参数。 - 支持关联标签，用标签来管理监控分组，告警匹配等。 -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### 监控详情 @@ -261,16 +261,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 监控历史数据报告，以趋势图表的形式展示了当前监控数值类型的指标的历史值，支持查询小时，天，月的历史数据，支持配置页面刷新时间。 - ⚠️注意监控历史图表需配置外置时序数据库才能获取完整功能。 -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### 告警中心 - 已触发告警消息的管理展示页面，使用户有直观的展示当前告警情况。 - 支持告警处理，告警标记未处理，告警删除清空等批量操作。 -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### 阈值规则 @@ -278,29 +278,29 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 阈值规则支持实时阈值和计划阈值，实时阈值可以在监控数据采集时直接触发告警，计划阈值支持 PromQL 等表达式在指定时间段内计算触发告警。 - 阈值规则支持可视化页面配置或更高灵活性的表达式规则配置，支持配置触发次数，告警级别，通知模板，关联指定监控等。 -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### 告警集成 - 统一管理不同第三方平台告警，集成接入第三方监控观测系统的告警消息，对其进行分组，收敛，抑制，静默，分发通知等。 -![HertzBeat](/img/home/11.png) +![HertzBeat](home/static/img/home/11.png) ### 告警分组 - 分组收敛支持对指定分组标签的告警进行分组合并，对时间段的相同重复告警去重收敛。 - 当阈值规则触发告警或外部告警上报后，会进入到分组收敛进行告警分组，告警去重，以避免大量告警消息导致告警风暴。 -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) ### 告警抑制 - 告警抑制用于配置告警之间的抑制关系，比如同一实例下高级别告警抑制低级别告警。 - 当某个告警发生时，可以抑制其他告警的产生。例如，当服务器宕机时，可以抑制该服务器上的所有告警。 -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### 告警静默 @@ -308,7 +308,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 此应用场景如用户在系统维护中，无需发已知告警。用户在工作日时间才会接收告警消息，用户在晚上需避免打扰等。 - 告警静默规则支持一次性时间段或周期性时间段，支持标签匹配和告警级别匹配。 -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### 消息通知 @@ -318,20 +318,20 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 通知策略支持标签匹配和告警级别匹配，方便的使不同标签的告警和告警级别分派给不同的接收处理人。 - 支持通知模板，用户可以自定义通过模板内容格式来满足自己的个性化通知展示需求。 -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) ### 监控模板 - HertzBeat 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需简单配置即可快速适配一款 `K8s` 或 `Docker` 等新的监控类型吗？ - 同理我们内置的所有监控类型(mysql,website,jvm,k8s)也一一映射为对应的监控模板，用户可以新增修改监控模板来自定义监控功能。 -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 采集集群 @@ -339,16 +339,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 采集器集群支持多节点部署，支持自动负载均衡，自动故障转移等。 - 支持多隔离网络的统一管理，云边协同。 -![HertzBeat](/img/home/18.png) +![HertzBeat](home/static/img/home/18.png) ### 状态页面 - 基于 HertzBeat 快速构建自己产品的对外状态页，轻松向用户传达您产品服务的实时状态。例如 Github 提供的服务状态页 [https://www.githubstatus.com](https://www.githubstatus.com)。 - 支持状态页组件状态和监控状态联动同步，故障事件维护管理机制等。提高您的透明度，专业度和用户信任，降低沟通成本。 -![HertzBeat](/img/home/19.png) +![HertzBeat](home/static/img/home/19.png) -![HertzBeat](/img/home/status.png) +![HertzBeat](home/static/img/home/status.png) --- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/baota-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/baota-deploy.md index 0bbfa27cf5e..f6acf556b77 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/baota-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: 使用 宝塔面板 部署 HertzBeat +id: baota-deploy +title: 使用 宝塔面板 部署 HertzBeat sidebar_label: 基于宝塔面板部署 --- @@ -16,15 +16,15 @@ Apache HertzBeat™ 支持在宝塔面板的 `Docker` 应用商店一键部署 > 在宝塔面板安装 Docker 服务，若已有则跳过。 - ![HertzBeat](/img/docs/start/install-to-baota-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-1.png) 2. 在`Docker-应用商店`中找到 `HertzBeat`，点击`安装` - ![HertzBeat](/img/docs/start/install-to-baota-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-2.png) 3. 设置域名等基本信息，点击`确定` - ![HertzBeat](/img/docs/start/install-to-baota-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-3.png) - 名称：应用名称，默认`HertzBeat-随机字符` - 版本选择：默认`latest` @@ -39,6 +39,6 @@ Apache HertzBeat™ 支持在宝塔面板的 `Docker` 应用商店一键部署 - 如您设置了域名，请直接在浏览器地址栏中输入域名访问，如`http://demo.hertzbeat.apache.org`，即可访问 `HertzBeat` 控制台。 - 如您选择了通过`IP+Port`访问，请在浏览器地址栏中输入域名访问 `http://<宝塔面板IP>:1157`，即可访问 `HertzBeat` 控制台。 -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > 默认用户名`admin`默认密码`hertzbeat` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/docker-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/docker-deploy.md index 658b8fb41ce..c97f93429c0 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/docker-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/docker-deploy.md @@ -1,11 +1,11 @@ --- -id: docker-deploy -title: 通过 Docker 方式安装 HertzBeat +id: docker-deploy +title: 通过 Docker 方式安装 HertzBeat sidebar_label: Docker方式安装 --- :::tip -使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 +使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 但不建议在生产环境中使用，生产环境建议使用 Docker Compose 方式部署, 安装包方式部署, Kubernetes 方式部署。 ::: @@ -51,17 +51,17 @@ sidebar_label: Docker方式安装 ::: -2. 开始探索 HertzBeat +2. 开始探索 HertzBeat 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用HertzBeat，默认账户密码 admin/hertzbeat。 ### 部署 HertzBeat Collector 集群(可选) :::note -HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 +HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 执行以下命令 @@ -96,7 +96,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 ::: -2. 开始探索 HertzBeat Collector +2. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -110,33 +110,33 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. MYSQL,TDENGINE或IotDB和HertzBeat都Docker部署在同一主机上，HertzBeat使用localhost或127.0.0.1连接数据库失败 此问题本质为Docker容器访问宿主机端口连接失败，由于docker默认网络模式为Bridge模式，其通过localhost访问不到宿主机。 - > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP + > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP > 解决办法二：使用Host网络模式启动Docker，即使Docker容器和宿主机共享网络 `docker run -d --network host .....` 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以 `docker logs hertzbeat` 查看容器日志是否有明显错误，提issue或交流群或社区反馈 3. 监控页面历史图表不显示，弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - + > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - > 安装初始化此时序数据库 4. 安装配置了时序数据库，但页面依旧显示弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 请检查配置的时许数据库参数是否正确 - > 时序数据库对应的 enable 是否设置为true - > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP + > 请检查配置的时许数据库参数是否正确 + > 时序数据库对应的 enable 是否设置为true + > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP > 可根据logs目录下启动日志排查 5. application.yml 是干什么用的 > 此文件是HertzBeat的配置文件，用于配置HertzBeat的各种参数，如数据库连接信息，时序数据库配置等。 - 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml + 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml 下载源 [github/script/application.yml](https://github.com/apache/hertzbeat/raw/master/script/application.yml) - 若需使用邮件发送告警，需替换 `application.yml` 里面的邮件服务器参数 @@ -147,8 +147,8 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 > 此文件是HertzBeat的用户配置文件，用于配置HertzBeat的用户信息，如账户密码等。 - HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat - 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 - 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml - 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 + 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml + 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) 具体修改步骤参考 [配置修改账户密码](account-modify) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/package-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/package-deploy.md index 1f576597a4d..22c401afc70 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/package-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/package-deploy.md @@ -69,7 +69,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 在选择前，建议先阅读 [Native 采集器指南](native-collector) 了解它的限制和取舍。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 下载安装包 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/rainbond-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/rainbond-deploy.md index 4ed3002af86..adbfcac881f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/rainbond-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: 使用 Rainbond 部署 HertzBeat +id: rainbond-deploy +title: 使用 Rainbond 部署 HertzBeat sidebar_label: 基于Rainbond部署 --- @@ -32,7 +32,7 @@ sidebar_label: 基于Rainbond部署 登录 Rainbond 后，点击左侧菜单中的 `应用市场`，切换到开源应用商店，在搜索框中搜索 `HertzBeat`，点击安装按钮。 -![HertzBeat](/img/docs/start/install-to-rainbond.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond.png) 填写以下信息，然后点击确认按钮进行安装。 @@ -43,7 +43,7 @@ sidebar_label: 基于Rainbond部署 等待安装完成，即可访问 HertzBeat 应用。 -![HertzBeat](/img/docs/start/hertzbeat-topology.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology.png) :::tip 通过 Rainbond 安装的 HertzBeat，默认使用了外部的 Mysql 数据库 和 Redis 以及 IoTDB。同时也挂载了 HertzBeat 的配置文件，可以在 `组件 -> 环境配置 -> 配置文件设置` 中修改配置文件。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/linux-os-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/linux-os-practice.md index 698a337ef52..18e907a3eb7 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/linux-os-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/linux-os-practice.md @@ -32,7 +32,7 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 操作系统监控 -> Linux 操作系统 -> 新增 Linux 操作系统监控 -![HertzBeat](/img/docs/start/linux-os-practice-1.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-1.png) ### 2. 配置参数 @@ -47,15 +47,15 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 可以使用标签分类来管理任务，如添加`OS=Linux`等相关标签。 -![HertzBeat](/img/docs/start/linux-os-practice-2.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-2.png) ### 3. 查看监控数据 在监控列表可以查看任务状态，点击这个监控详情可以查看指标数据图表等。 -![HertzBeat](/img/docs/start/linux-os-practice-3.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-3.png) -![HertzBeat](/img/docs/start/linux-os-practice-4.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-4.png) ### 4. 设置阈值规则 @@ -65,23 +65,23 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > > 配置阈值，配置告警表达式-当指标`文件系统使用率`大于等于 `50%` 触发，也支持设置告警级别和通知模板信息等。 -![HertzBeat](/img/docs/start/linux-os-practice-5.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 最终可以在告警中心看到已触发的告警。 -![HertzBeat](/img/docs/start/linux-os-practice-6.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-6.png) ### 5. 消息通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 -![HertzBeat](/img/docs/start/linux-os-practice-7.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-7.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 -![HertzBeat](/img/docs/start/linux-os-practice-8.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-8.png) 当阈值触发后就可以收到对应告警消息，如果没有配置消息通知，也可以在**告警中心**查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/springboot-auto-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/springboot-auto-practice.md index a3f8163eba0..36400130890 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/springboot-auto-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/springboot-auto-practice.md @@ -1,7 +1,7 @@ --- -id: springboot-auto-practice -title: SpringBoot Web应用监控案例 -sidebar_label: SpringBoot Web应用监控案例 +id: springboot-auto-practice +title: SpringBoot Web应用监控案例 +sidebar_label: SpringBoot Web应用监控案例 --- :::tip @@ -141,7 +141,7 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > 系统页面 -> 监控中心 -> 新增监控 -> AUTO -> Prometheus任务 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-1.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-1.png) 2. 填写关键参数 @@ -153,16 +153,16 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-2.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-2.png) 3. 查看检测指标数据 > 点击进入新建监控，可以查看指标数据详情及指标历史图表等。 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-3.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-3.png) - ![HertzBeat](/img/docs/start/springboot-auto-practice-4.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-4.png) ## Grafana可视化集成 (可选) @@ -181,13 +181,13 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 比如：Grafana 数据源选择`hertzbeat-victoria-metrics`，然后在仪表盘点击:「Share」→「Export」→「Save to file」下载模板并上传至 HertzBeat 监控中。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-5.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-5.png) 3. 查看 Grafana 图表 > 进入新增 AUTO 监控页面，点击 Grafana 图标按钮，即可查看 Grafana 图表。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-6.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-6.png) ## 告警与通知联动 @@ -196,7 +196,7 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > 系统页面 -> 告警 -> 阈值规则 -> 新增 -> 新增阈值 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-7.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-7.png) > HertzBeat 提供了 **实时计算** 和 **计划周期** 两种类型的阈值规则设置，这里我们以 **计划周期** 阈值规则为例。 > @@ -213,24 +213,24 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 可以设置的阈值规则组合有很多，用户可以根据自身需要设置更丰富的告警规则。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-8.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-8.png) > 最后可以在 告警中心 看到已触发的告警。 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-9.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-9.png) 3. 告警通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-10.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-10.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-11.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-11.png) 4. OK！当阈值规则触发后我们就可以收到对应告警消息啦，如果没有配置通知，也可以在告警中心查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/sslcert-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/sslcert-practice.md index c81d0b92402..91aaf8b6327 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/sslcert-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL 证书过期监控案例 +id: ssl-cert-practice +title: SSL 证书过期监控案例 sidebar_label: SSL 证书过期监控案例 --- @@ -34,28 +34,28 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 应用服务监控 -> SSL 证书 -> 新增 SSL 证书 - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. 配置监控网站 > 我们这里举例监控百度网站, 配置监控host域名，名称，采集间隔等。 - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. 设置阈值(证书过期时触发) - > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 + > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 > 配置阈值，选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 @@ -63,17 +63,17 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 同理如上，选择代码阈值规则，新增配置阈值，配置告警表达式-当指标有效期时间戳 `end_timestamp`，`now()`函数为当前时间戳，若配置提前一周触发告警即：`end_timestamp <= (now() + 604800000)` , 其中 `604800000` 为7天总时间差毫秒值。 - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > 最终可以在告警中心看到已触发的告警。 - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. 告警通知(通过钉钉微信飞书等及时通知) > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) 钉钉微信飞书等 token 配置可以参考帮助文档 @@ -81,11 +81,11 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 消息通知 -> 通知策略 -> 新增告警通知策略 -> 将刚才配置的接收人启用通知 - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK 当阈值触发后我们就可以收到对应告警消息啦，如果没有配通知，也可以在告警中心查看告警信息。 ----- +---- ## 结束搞定 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/tdengine-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/tdengine-practice.md index 6228026c503..2c83ad46560 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/tdengine-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/usecase/tdengine-practice.md @@ -1,6 +1,6 @@ --- -id: tdengine-practice -title: TDengine 监控案例 +id: tdengine-practice +title: TDengine 监控案例 sidebar_label: TDengine 监控案例 --- @@ -40,7 +40,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 监控中心 -> 新增监控 -> 自定义监控 -> TDengine-PromQL任务 - ![HertzBeat](/img/docs/start/tdengine_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1.png) 2. 填写关键参数 @@ -52,15 +52,15 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/tdengine_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/tdengine_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_3.png) - ![HertzBeat](/img/docs/start/tdengine_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_4.png) ## 监控 TDengine(Prometheus) @@ -68,7 +68,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 监控中心 -> 新增监控 -> AUTO -> Prometheus任务 - ![HertzBeat](/img/docs/start/tdengine_1_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_1.png) 2. 填写关键参数 @@ -80,15 +80,15 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/tdengine_1_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/tdengine_1_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_3.png) - ![HertzBeat](/img/docs/start/tdengine_1_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_4.png) ### Grafana可视化集成 (可选) @@ -107,13 +107,13 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 比如：Grafana 数据源选择`hertzbeat-victoria-metrics`，然后在仪表盘点击:「Share」→「Export」→「Save to file」下载模板并上传至 HertzBeat 监控中，可参考：[taoskeeper-prometheus-dashboard](https://grafana.com/grafana/dashboards/15164-taoskeeper-prometheus-dashboard/) - ![HertzBeat](/img/docs/start/tdengine_1_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_5.png) 3. 查看 Grafana 图表 > 进入新增 AUTO 监控页面，点击 Grafana 图标按钮，即可查看 Grafana 图表。 - ![HertzBeat](/img/docs/start/tdengine_1_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_6.png) ## 告警与通知联动 @@ -122,7 +122,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 告警 -> 阈值规则 -> 新增 -> 新增阈值 > - ![HertzBeat](/img/docs/start/tdengine_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_5.png) > HertzBeat 提供了 **实时计算** 和 **计划周期** 两种类型的阈值规则设置，这里我们以 **计划周期** 阈值规则为例。 > @@ -139,24 +139,24 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以设置的阈值规则组合有很多，用户可以根据自身需要设置更丰富的告警规则。 - ![HertzBeat](/img/docs/start/tdengine_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_6.png) > 最后可以在 告警中心 看到已触发的告警。 > - ![HertzBeat](/img/docs/start/tdengine_7.png) + ![HertzBeat](home/static/img/docs/start/tdengine_7.png) 3. 告警通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 > - ![HertzBeat](/img/docs/start/tdengine_8.png) + ![HertzBeat](home/static/img/docs/start/tdengine_8.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 > - ![HertzBeat](/img/docs/start/tdengine_9.png) + ![HertzBeat](home/static/img/docs/start/tdengine_9.png) 4. OK！当阈值规则触发后我们就可以收到对应告警消息啦，如果没有配置通知，也可以在告警中心查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/template.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/template.md index 5ee81d6b8bf..3951cbb4f2b 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/template.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/template.md @@ -1,6 +1,6 @@ --- -id: template -title: 监控模板中心 +id: template +title: 监控模板中心 sidebar_label: 监控模板 --- @@ -11,11 +11,11 @@ sidebar_label: 监控模板 这是它的架构原理: -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **我们将所有监控采集类型(mysql,website,jvm,k8s)都定义为yml模板，用户可以导入这些模板到hertzbeat系统中，使其支持对应类型的监控，非常方便！** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **欢迎大家一起贡献你使用过程中自定义的通用监控类型YML模板，可用的模板如下:** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md index 6393185640e..c7a7285a90f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md @@ -1,6 +1,6 @@ --- id: extend-http-example-hertzbeat -title: 教程一:适配一款基于HTTP协议的监控类型 +title: 教程一:适配一款基于HTTP协议的监控类型 sidebar_label: 教程一:适配一款HTTP协议监控 --- @@ -188,25 +188,25 @@ metrics: **新增完毕，现在我们重启hertzbeat系统。我们可以看到系统页面已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 系统页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常的设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-token.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-token.md index 674f2b56e02..e7b2bdd14f0 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-token.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http-example-token.md @@ -1,6 +1,6 @@ --- id: extend-http-example-token -title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 +title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 sidebar_label: 教程二:获取TOKEN后续认证使用 --- @@ -221,13 +221,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **新增成功后我们就可以在详情页面看到我们采集的 `token`, `refreshToken`指标数据。** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### 将`token`作为变量参数给后面的监控指标采集使用 @@ -381,15 +381,15 @@ metrics: **配置完成后，再次重启 `hertzbeat` 系统，查看监控详情页面** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http.md index 65a740c5a4c..e8aa27520be 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-http.md @@ -1,6 +1,6 @@ --- -id: extend-http -title: HTTP协议自定义监控 +id: extend-http +title: HTTP协议自定义监控 sidebar_label: HTTP协议自定义监控 --- @@ -20,7 +20,7 @@ HTTP协议支持我们自定义HTTP请求路径，请求header，请求参数， **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jdbc.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jdbc.md index c1e6545e4f4..50a56c366ca 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jdbc.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jdbc.md @@ -1,6 +1,6 @@ --- -id: extend-jdbc -title: JDBC协议自定义监控 +id: extend-jdbc +title: JDBC协议自定义监控 sidebar_label: JDBC协议自定义监控 --- @@ -57,7 +57,7 @@ SQL响应数据： **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jmx.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jmx.md index b4dadf8cfde..b906de82547 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jmx.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-jmx.md @@ -1,6 +1,6 @@ --- -id: extend-jmx -title: JMX协议自定义监控 +id: extend-jmx +title: JMX协议自定义监控 sidebar_label: JMX协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: JMX协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ngql.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ngql.md index 23b404986c5..93751b7a678 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ngql.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ngql.md @@ -13,18 +13,18 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 ### **filterCount** > -> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 -> commands字段语法格式: aliasField#NGQL#filterName#filterValue -> `aliasField`: 对应监控模板中的`aliasFields`中的值 -> `NGQL`: 查询语句 -> `filterName`: 过滤属性名称（可选） +> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 +> commands字段语法格式: aliasField#NGQL#filterName#filterValue +> `aliasField`: 对应监控模板中的`aliasFields`中的值 +> `NGQL`: 查询语句 +> `filterName`: 过滤属性名称（可选） > `filterValue`: 过滤属性值（可选） 例如： -- online_meta_count#SHOW HOSTS META#Status#ONLINE +- online_meta_count#SHOW HOSTS META#Status#ONLINE 对 `SHOW HOSTS META` 返回的结果中统计滤Status==ONLINE的数量 -- online_meta_count#SHOW HOSTS META## +- online_meta_count#SHOW HOSTS META## 统计 `SHOW HOSTS META` 返回的行数 #### **oneRow** @@ -50,7 +50,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 例如： -- 查询的指标字段为：a,b +- 查询的指标字段为：a,b - 查询NGQL：match (v:metrics) return v.metrics.a as a,v.metrics.b as b; 这里指标字段就能和响应数据一一映射为多行采集数据。 @@ -71,7 +71,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -168,7 +168,7 @@ metrics: parseType: columns # 定义采集数据使用的查询语句 commands: - - match (v:tag1) return "tag1" as name ,count(v) as cnt + - match (v:tag1) return "tag1" as name ,count(v) as cnt - match (v:tag2) return "tag2" as name ,count(v) as cnt timeout: ^_^timeout^_^ ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-point.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-point.md index 45e56692693..e4476822739 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-point.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-point.md @@ -1,17 +1,17 @@ --- -id: extend-point -title: 自定义监控 +id: extend-point +title: 自定义监控 sidebar_label: 自定义监控 --- -> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 +> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 > 目前自定义监控支持[HTTP协议](extend-http)，[JDBC协议](extend-jdbc)，[SSH协议](extend-ssh)，[JMX协议](extend-jmx)，[SNMP协议](extend-snmp)，后续会支持更多通用协议。 ## 自定义流程 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ### 自定义监控指标刷新时间 @@ -139,7 +139,7 @@ params: # hide param-true or false # 是否隐藏字段 true or false hide: true - + metrics: # metrics - summary, inner monitoring metrics (responseTime - response time, keyword - number of keywords) # 监控指标 - summary, 内置监控指标有 (responseTime - 响应时间, keyword - 关键字数量) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-push.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-push.md index d938b5cddfb..6b1d59b4112 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-push.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat页面 -> 应用服务监控 -> 推送方式监控 -> 新建推送方 ### 监控配置示例 -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-snmp.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-snmp.md index 018feed6f46..b24c30c5e9c 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-snmp.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-snmp.md @@ -1,6 +1,6 @@ --- -id: extend-snmp -title: SNMP协议自定义监控 +id: extend-snmp +title: SNMP协议自定义监控 sidebar_label: SNMP协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: SNMP协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ssh.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ssh.md index 9b19f2ae987..b1e2020c294 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ssh.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-ssh.md @@ -1,6 +1,6 @@ --- -id: extend-ssh -title: SSH协议自定义监控 +id: extend-ssh +title: SSH协议自定义监控 sidebar_label: SSH协议自定义监控 --- @@ -31,7 +31,7 @@ SHELL脚本查询回来的数据字段和我们需要的指标映射，就能获 ```shell tombook -14:00:15 up 72 days +14:00:15 up 72 days ``` 则最后采集到的指标数据一一映射为： @@ -54,7 +54,7 @@ Mem: 7962 4065 333 1 3562 3593 Swap: 8191 33 8158 ``` -在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： +在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： `free -m | grep Mem | awk 'BEGIN{print "total used free buff_cache available"} {print $2,$3,$4,$6,$7}'` 控制台响应为： @@ -69,7 +69,7 @@ total used free buff_cache available **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-telnet.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-telnet.md index dfaf2a5a714..34185e8e3c4 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-telnet.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-telnet.md @@ -1,6 +1,6 @@ --- -id: extend-telnet -title: Telnet协议自定义监控 +id: extend-telnet +title: Telnet协议自定义监控 sidebar_label: Telnet协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: Telnet协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-tutorial.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-tutorial.md index e8aa9d6119c..e3a89300808 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-tutorial.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/advanced/extend-tutorial.md @@ -1,6 +1,6 @@ --- id: extend-tutorial -title: 自定义适配一款基于HTTP协议的新监控类型 +title: 自定义适配一款基于HTTP协议的新监控类型 sidebar_label: 教程案例 --- @@ -227,25 +227,25 @@ metrics: **点击保存并应用。我们可以看到系统页面的自定义监控菜单已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/contribution.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/contribution.md index 73c6cb6f19d..cc742e99e8d 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/contribution.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/contribution.md @@ -1,5 +1,5 @@ --- -id: contribution +id: contribution title: 贡献指南 sidebar_position: 0 --- @@ -89,27 +89,27 @@ limitations under the License. 2. 然后 用 git 命令 将代码下载到本地: ```shell - git clone git@github.com:`YOUR_USERNAME`/hertzbeat.git #Recommended + git clone git@github.com:`YOUR_USERNAME`/hertzbeat.git #Recommended ``` 3. 下载完成后，请参考目标仓库的入门指南或者 README 文件对项目进行初始化。 4. 接着，您可以参考如下命令进行代码的提交, 切换新的分支, 进行开发: ```shell - git checkout -b a-feature-branch #Recommended + git checkout -b a-feature-branch #Recommended ``` 5. 提交 commit, commit 描述信息需要符合约定格式: [module name or type name]feature or bugfix or doc: custom message. ```shell - git add - git commit -m '[docs]feature: necessary instructions' #Recommended + git add + git commit -m '[docs]feature: necessary instructions' #Recommended ``` 6. 推送到远程仓库 ```shell - git push origin a-feature-branch + git push origin a-feature-branch ``` 7. 然后您就可以在 GitHub 上发起新的 PR (Pull Request)。 @@ -139,7 +139,7 @@ git push origin --delete a-dev-branch ```shell git remote add upstream https://github.com/apache/hertzbeat.git #Bind the remote warehouse, if it has been executed, it does not need to be executed again -git checkout master +git checkout master git pull upstream master ``` @@ -168,4 +168,4 @@ git pull upstream master > - **[web-app](https://github.com/apache/hertzbeat/tree/master/web-app)** 提供可视化控制台页面 > 监控告警系统可视化控制台前端 -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/new_committer_process.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/new_committer_process.md index fed1d3a9fb1..b9da04da3e9 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/new_committer_process.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/new_committer_process.md @@ -352,15 +352,15 @@ hi, i accept. Thanks for invitaion. 找到`CLAs`点击进入页面 - ![HertzBeat](/img/docs/community/clas-web.png) + ![HertzBeat](home/static/img/docs/community/clas-web.png) 找到`ICLA(个人贡献者许可协议)`，点击[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) - ![HertzBeat](/img/docs/community/icla-web.png) + ![HertzBeat](home/static/img/docs/community/icla-web.png) 跳转后，会显示需要签署的协议，这里可以在网页上直接填写，也可以下载后填写。 - ![HertzBeat](/img/docs/community/icla-pdf.png) + ![HertzBeat](home/static/img/docs/community/icla-pdf.png) 2. 填写iCLA @@ -368,8 +368,8 @@ hi, i accept. Thanks for invitaion. 需要填写的内容： - ![HertzBeat](/img/docs/community/icla-content-1.png) - ![HertzBeat](/img/docs/community/icla-content-2.png) + ![HertzBeat](home/static/img/docs/community/icla-content-1.png) + ![HertzBeat](home/static/img/docs/community/icla-content-2.png) 在PDF中需要填写的字段： @@ -383,12 +383,12 @@ hi, i accept. Thanks for invitaion. - `Date` > 填写样例 - > ![HertzBeat](/img/docs/community/icla-content-3.png) - > ![HertzBeat](/img/docs/community/icla-content-4.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-3.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-4.png) 3. 打印并签署 - ![HertzBeat](/img/docs/community/icla-content-5.png) + ![HertzBeat](home/static/img/docs/community/icla-content-5.png) `Please sign`字段需要将文件打印出来然后手写签名，内容为自己姓名的全拼。 @@ -420,7 +420,7 @@ hi, i accept. Thanks for invitaion. 在网站 [https://id.apache.org/reset/enter](https://id.apache.org/reset/enter) 输入您的Apache ID -![HertzBeat](/img/docs/community/account-1.png) +![HertzBeat](home/static/img/docs/community/account-1.png) 点击`Send Email`后会提示发送成功。 @@ -434,44 +434,44 @@ hi, i accept. Thanks for invitaion. 登录后可以看到这个内容`Link GitHub username to ASF id`，点击跳转 -![HertzBeat](/img/docs/community/account-2.png) +![HertzBeat](home/static/img/docs/community/account-2.png) 输入您的Apache的账号和密码并登录 -![HertzBeat](/img/docs/community/account-3.png) +![HertzBeat](home/static/img/docs/community/account-3.png) 点击 `Authenticate with GitHub` -![HertzBeat](/img/docs/community/account-4.png) +![HertzBeat](home/static/img/docs/community/account-4.png) 点击`Authorize apache`授权给Apache -![HertzBeat](/img/docs/community/account-5.png) +![HertzBeat](home/static/img/docs/community/account-5.png) 点击`Send GitHub Invitation!` 发送GitHub邀请邮件 -![HertzBeat](/img/docs/community/account-6.png) +![HertzBeat](home/static/img/docs/community/account-6.png) 邮箱中会收到一封邮件，点击`Join @apache` > 这里邮箱指的是您提供给PMC的那个邮箱地址 -![HertzBeat](/img/docs/community/account-7.png) +![HertzBeat](home/static/img/docs/community/account-7.png) 点击`Join The Apache Software Foundation`，加入GitHub加入Apache组织，会自动跳转到GitHub页面 -![HertzBeat](/img/docs/community/account-8.png) -![HertzBeat](/img/docs/community/account-9.png) +![HertzBeat](home/static/img/docs/community/account-8.png) +![HertzBeat](home/static/img/docs/community/account-9.png) 回到Apache页面，提示GitHub启用多重身份认证，在GitHub页面启用双重身份认证 > GitHub双重身份认证介绍，[点击跳转官方文档](https://docs.github.com/zh/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication) -![HertzBeat](/img/docs/community/account-10.png) +![HertzBeat](home/static/img/docs/community/account-10.png) 启动完成之后等几分钟，提示已经绑定完成 -![HertzBeat](/img/docs/community/account-11.png) +![HertzBeat](home/static/img/docs/community/account-11.png) 至此您的GitHub账号与Apache账号就绑定完成了。 @@ -485,17 +485,17 @@ hi, i accept. Thanks for invitaion. 进入设置页面，并点击`添加其他电子邮件地址`` -![HertzBeat](/img/docs/community/email-1.png) +![HertzBeat](home/static/img/docs/community/email-1.png) 填写您的apache邮箱，按照指引点击下一步 -![HertzBeat](/img/docs/community/email-2.png) -![HertzBeat](/img/docs/community/email-3.png) -![HertzBeat](/img/docs/community/email-4.png) +![HertzBeat](home/static/img/docs/community/email-2.png) +![HertzBeat](home/static/img/docs/community/email-3.png) +![HertzBeat](home/static/img/docs/community/email-4.png) 设置为默认发送邮箱(可选) -![HertzBeat](/img/docs/community/email-5.png) +![HertzBeat](home/static/img/docs/community/email-5.png) 配置完成。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/alert_threshold.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/alert_threshold.md index 26db47db07b..56f9a28f505 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/alert_threshold.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/alert_threshold.md @@ -22,7 +22,7 @@ sidebar_label: 阈值规则 配置阈值，例如: 选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) 配置项说明： diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/redis_cluster.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/redis_cluster.md index 7d20acff065..17e8ddd513f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/redis_cluster.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/redis_cluster.md @@ -1,7 +1,7 @@ --- -id: redis_cluster -title: 监控：Redis Cluster 数据库监控 -sidebar_label: Redis Cluster数据库 +id: redis_cluster +title: 监控：Redis Cluster 数据库监控 +sidebar_label: Redis Cluster数据库 keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监控] --- @@ -98,7 +98,7 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 添加监控节点时填入所需要的参数. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) 最终的效果. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/status.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/status.md index dc688d023b8..8fc76886a76 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/status.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: 状态页面 -sidebar_label: 状态页面 +id: status +title: 状态页面 +sidebar_label: 状态页面 keywords: [开源监控系统, 开源网站监控, 状态页面] --- @@ -24,7 +24,7 @@ keywords: [开源监控系统, 开源网站监控, 状态页面] 填写完组织信息后，点击 `确定`。 -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. 新增组件 @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. 维护事件 @@ -59,7 +59,7 @@ status: 点击 `发布事件` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | 字段名称 | 字段说明 | 举例 | |------|---------------------------------------------|----------------------------------------------------------------------| @@ -70,4 +70,4 @@ status: > 提示：可以多次发布消息，及时向团队汇报当前状态。 -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/introduce.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/introduce.md index a36aea6b10d..17922260c29 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/introduce.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/introduce.md @@ -39,11 +39,11 @@ slug: / HertzBeat 自身并没有去创造一种采集数据协议让监控对端来适配它。而是充分使用了现有的生态，`SNMP协议`采集网络交换机路由器信息，`JMX规范`采集JAVA应用信息，`JDBC规范`采集数据集信息，`SSH`直连执行脚本获取回显信息，`HTTP+(JsonPath | prometheus等)`解析API接口信息，`IPMI协议`采集服务器信息等等。 HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可配置化，最后使其都可以通过编写YML格式监控模板的形式，来制定模板使用这些协议来采集任何想要的指标数据。 -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) 你相信用户只需在UI页面编写一个监控模板，点击保存后，就能立刻适配一款`K8s`或`Docker`等新的监控类型吗？ -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 内置监控类型 @@ -94,7 +94,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 > 我们将每个监控类型都视为一个监控模板，不管是官方内置的还是后期用户自定义新增的。用户都可以方便的通过修改监控模板来新增修改删除监控指标。 > 模板里面包含各个协议的使用配置，环境变量，指标转换，指标计算，单位转换，指标采集等一系列功能，帮助用户能采集到自己想要的监控指标。 -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### 无需 Agent @@ -116,7 +116,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 - 监控任务在采集器集群中自调度，单采集器挂掉无感知故障迁移采集任务，新加入采集器节点自动调度分担采集压力。 - 单机模式与集群模式相互切换部署非常方便，无需额外组件部署。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 云边协同 @@ -127,7 +127,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 在多个网络不相通的隔离网络中，在以往方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 `HertzBeat` 提供的云边协同能力，可以在多个隔离网络部署边缘采集器，采集器在隔离网络内部进行监控任务采集，采集数据上报，由主服务统一调度管理展示。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 易用友好 @@ -162,7 +162,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - HertzBeat 的用户管理统一由配置文件 `sureness.yml` 维护，用户可以通过修改此文件来新增删除修改用户信息，用户角色权限等。默认账户密码 admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### 概览页面 @@ -170,7 +170,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 展示当前注册的采集器集群状态，包括采集器的上线状态，监控任务，启动时间，IP地址，名称等。 - 下发展示了最近告警信息列表，告警级别分布情况，告警处理率情况。 -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### 监控中心 @@ -217,7 +217,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### 新增修改监控 @@ -225,7 +225,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 页面上配置的监控参数由对应监控类型的监控模板所定义，用户可以通过修改监控模板来修改页面配置参数。 - 支持关联标签，用标签来管理监控分组，告警匹配等。 -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### 监控详情 @@ -234,16 +234,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 监控历史数据报告，以趋势图表的形式展示了当前监控数值类型的指标的历史值，支持查询小时，天，月的历史数据，支持配置页面刷新时间。 - ⚠️注意监控历史图表需配置外置时序数据库才能获取完整功能，时序数据库支持: IOTDB, TDengine, InfluxDB, GreptimeDB -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### 告警中心 - 已触发告警消息的管理展示页面，使用户有直观的展示当前告警情况。 - 支持告警处理，告警标记未处理，告警删除清空等批量操作。 -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### 阈值规则 @@ -252,18 +252,18 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 阈值规则支持可视化页面配置或表达式规则配置，灵活性更高。 - 支持配置触发次数，告警级别，通知模板，关联指定监控等。 -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### 告警收敛 - 当通过阈值规则判断触发告警后，会进入到告警收敛，告警收敛会根据规则对特定时间段的重复告警消息去重收敛，已避免大量重复性告警导致接收人告警麻木。 - 告警收敛规则支持重复告警生效时间段，标签匹配和告警级别匹配过滤。 -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### 告警静默 @@ -271,9 +271,9 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 此应用场景如用户在系统维护中，无需发已知告警。用户在工作日时间才会接收告警消息，用户在晚上需避免打扰等。 - 告警静默规则支持一次性时间段或周期性时间段，支持标签匹配和告警级别匹配。 -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### 消息通知 @@ -283,18 +283,18 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 通知策略支持标签匹配和告警级别匹配，方便的使不同标签的告警和告警级别分派给不同的接收处理人。 - 支持通知模板，用户可以自定义通过模板内容格式来满足自己的个性化通知展示需求。 -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) ### 监控模板 - HertzBeat 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需简单配置即可快速适配一款 `K8s` 或 `Docker` 等新的监控类型吗？ - 同理我们内置的所有监控类型(mysql,website,jvm,k8s)也一一映射为对应的监控模板，用户可以新增修改监控模板来自定义监控功能。 -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) --- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/baota-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/baota-deploy.md index 5f6c42fe43c..2135f84e91b 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/baota-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: 使用 宝塔面板 部署 HertzBeat +id: baota-deploy +title: 使用 宝塔面板 部署 HertzBeat sidebar_label: 基于宝塔面板部署 --- @@ -16,15 +16,15 @@ Apache HertzBeat 支持在宝塔面板的 `Docker` 应用商店一键部署。 > 在宝塔面板安装 Docker 服务，若已有则跳过。 - ![HertzBeat](/img/docs/start/install-to-baota-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-1.png) 2. 在`Docker-应用商店`中找到 `HertzBeat`，点击`安装` - ![HertzBeat](/img/docs/start/install-to-baota-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-2.png) 3. 设置域名等基本信息，点击`确定` - ![HertzBeat](/img/docs/start/install-to-baota-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-3.png) - 名称：应用名称，默认`HertzBeat-随机字符` - 版本选择：默认`latest` @@ -39,6 +39,6 @@ Apache HertzBeat 支持在宝塔面板的 `Docker` 应用商店一键部署。 - 如您设置了域名，请直接在浏览器地址栏中输入域名访问，如`http://demo.hertzbeat.apache.org`，即可访问 `HertzBeat` 控制台。 - 如您选择了通过`IP+Port`访问，请在浏览器地址栏中输入域名访问 `http://<宝塔面板IP>:1157`，即可访问 `HertzBeat` 控制台。 -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > 默认用户名`admin`默认密码`hertzbeat` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/docker-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/docker-deploy.md index c4cb4844c94..bc5e08e1541 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/docker-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/docker-deploy.md @@ -1,11 +1,11 @@ --- -id: docker-deploy -title: 通过 Docker 方式安装 HertzBeat +id: docker-deploy +title: 通过 Docker 方式安装 HertzBeat sidebar_label: Docker方式安装 --- :::tip -使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 +使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 但不建议在生产环境中使用，生产环境建议使用 Docker Compose 方式部署, 安装包方式部署, Kubernetes 方式部署。 ::: @@ -49,17 +49,17 @@ sidebar_label: Docker方式安装 ::: -2. 开始探索 HertzBeat +2. 开始探索 HertzBeat 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用HertzBeat，默认账户密码 admin/hertzbeat。 ### 部署 HertzBeat Collector 集群(可选) :::note -HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 +HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 执行以下命令 @@ -92,7 +92,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 ::: -2. 开始探索 HertzBeat Collector +2. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -106,33 +106,33 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. MYSQL,TDENGINE或IotDB和HertzBeat都Docker部署在同一主机上，HertzBeat使用localhost或127.0.0.1连接数据库失败 此问题本质为Docker容器访问宿主机端口连接失败，由于docker默认网络模式为Bridge模式，其通过localhost访问不到宿主机。 - > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP + > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP > 解决办法二：使用Host网络模式启动Docker，即使Docker容器和宿主机共享网络 `docker run -d --network host .....` 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以 `docker logs hertzbeat` 查看容器日志是否有明显错误，提issue或交流群或社区反馈 3. 监控页面历史图表不显示，弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - + > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - > 安装初始化此时序数据库 4. 安装配置了时序数据库，但页面依旧显示弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 请检查配置的时许数据库参数是否正确 - > 时序数据库对应的 enable 是否设置为true - > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP + > 请检查配置的时许数据库参数是否正确 + > 时序数据库对应的 enable 是否设置为true + > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP > 可根据logs目录下启动日志排查 5. application.yml 是干什么用的 > 此文件是HertzBeat的配置文件，用于配置HertzBeat的各种参数，如数据库连接信息，时序数据库配置等。 - 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml + 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml 下载源 [github/script/application.yml](https://github.com/apache/hertzbeat/raw/master/script/application.yml) - 若需使用邮件发送告警，需替换 `application.yml` 里面的邮件服务器参数 @@ -143,8 +143,8 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 > 此文件是HertzBeat的用户配置文件，用于配置HertzBeat的用户信息，如账户密码等。 - HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat - 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 - 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml - 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 + 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml + 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) 具体修改步骤参考 [配置修改账户密码](account-modify) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/package-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/package-deploy.md index b4f3d7e52da..af0972aedff 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/package-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/package-deploy.md @@ -1,6 +1,6 @@ --- -id: package-deploy -title: 通过安装包安装 HertzBeat +id: package-deploy +title: 通过安装包安装 HertzBeat sidebar_label: 安装包方式安装 --- @@ -40,7 +40,7 @@ Apache HertzBeat 支持在Linux Windows Mac系统安装运行，CPU支持X86/ARM 3. 配置账户文件(可选) - HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat 若需要新增删除修改账户或密码，可以通过修改位于 `config/sureness.yml` 的配置文件实现，具体参考 - [配置修改账户密码](account-modify) @@ -50,7 +50,7 @@ Apache HertzBeat 支持在Linux Windows Mac系统安装运行，CPU支持X86/ARM 执行位于安装目录 bin 下的启动脚本 startup.sh, windows 环境下为 startup.bat ```shell - ./startup.sh + ./startup.sh ``` 5. 开始探索HertzBeat @@ -63,7 +63,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 下载安装包 @@ -103,10 +103,10 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 执行位于安装目录 hertzbeat-collector/bin/ 下的启动脚本 startup.sh, windows 环境下为 startup.bat ```shell - ./startup.sh + ./startup.sh ``` -4. 开始探索 HertzBeat Collector +4. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -119,9 +119,9 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. 启动失败，需您提前准备JAVA运行环境 - 安装JAVA运行环境-可参考[官方网站](https://www.oracle.com/java/technologies/downloads/) + 安装JAVA运行环境-可参考[官方网站](https://www.oracle.com/java/technologies/downloads/) 要求：JAVA17环境 - 下载JAVA安装包: [镜像站](https://mirrors.huaweicloud.com/openjdk/) + 下载JAVA安装包: [镜像站](https://mirrors.huaweicloud.com/openjdk/) 安装后命令行检查是否成功安装 ```shell @@ -134,6 +134,6 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `hertzbeat/config/application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `hertzbeat/config/application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以查看 `hertzbeat/logs/` 目录下面的运行日志是否有明显错误，提issue或交流群或社区反馈 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/rainbond-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/rainbond-deploy.md index 4ed3002af86..adbfcac881f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/rainbond-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: 使用 Rainbond 部署 HertzBeat +id: rainbond-deploy +title: 使用 Rainbond 部署 HertzBeat sidebar_label: 基于Rainbond部署 --- @@ -32,7 +32,7 @@ sidebar_label: 基于Rainbond部署 登录 Rainbond 后，点击左侧菜单中的 `应用市场`，切换到开源应用商店，在搜索框中搜索 `HertzBeat`，点击安装按钮。 -![HertzBeat](/img/docs/start/install-to-rainbond.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond.png) 填写以下信息，然后点击确认按钮进行安装。 @@ -43,7 +43,7 @@ sidebar_label: 基于Rainbond部署 等待安装完成，即可访问 HertzBeat 应用。 -![HertzBeat](/img/docs/start/hertzbeat-topology.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology.png) :::tip 通过 Rainbond 安装的 HertzBeat，默认使用了外部的 Mysql 数据库 和 Redis 以及 IoTDB。同时也挂载了 HertzBeat 的配置文件，可以在 `组件 -> 环境配置 -> 配置文件设置` 中修改配置文件。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/sslcert-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/sslcert-practice.md index 7015867c0fe..29386d98aae 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/sslcert-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/start/sslcert-practice.md @@ -34,28 +34,28 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 应用服务监控 -> SSL 证书 -> 新增 SSL 证书 - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. 配置监控网站 > 我们这里举例监控百度网站, 配置监控host域名，名称，采集间隔等。 - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. 设置阈值(证书过期时触发) - > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 + > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 > 配置阈值，选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 @@ -63,17 +63,17 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 同理如上，选择代码阈值规则，新增配置阈值，配置告警表达式-当指标有效期时间戳 `end_timestamp`，`now()`函数为当前时间戳，若配置提前一周触发告警即：`end_timestamp <= (now() + 604800000)` , 其中 `604800000` 为7天总时间差毫秒值。 - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > 最终可以在告警中心看到已触发的告警。 - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. 告警通知(通过钉钉微信飞书等及时通知) > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) 钉钉微信飞书等 token 配置可以参考帮助文档 @@ -81,11 +81,11 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 消息通知 -> 通知策略 -> 新增告警通知策略 -> 将刚才配置的接收人启用通知 - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK 当阈值触发后我们就可以收到对应告警消息啦，如果没有配通知，也可以在告警中心查看告警信息。 ----- +---- ## 结束搞定 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/template.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/template.md index 5ee81d6b8bf..3951cbb4f2b 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/template.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/template.md @@ -1,6 +1,6 @@ --- -id: template -title: 监控模板中心 +id: template +title: 监控模板中心 sidebar_label: 监控模板 --- @@ -11,11 +11,11 @@ sidebar_label: 监控模板 这是它的架构原理: -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **我们将所有监控采集类型(mysql,website,jvm,k8s)都定义为yml模板，用户可以导入这些模板到hertzbeat系统中，使其支持对应类型的监控，非常方便！** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **欢迎大家一起贡献你使用过程中自定义的通用监控类型YML模板，可用的模板如下:** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md index f99807576ba..db74cfbd148 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md @@ -1,6 +1,6 @@ --- id: extend-http-example-hertzbeat -title: 教程一:适配一款基于HTTP协议的监控类型 +title: 教程一:适配一款基于HTTP协议的监控类型 sidebar_label: 教程一:适配一款HTTP协议监控 --- @@ -188,25 +188,25 @@ metrics: **新增完毕，现在我们重启hertzbeat系统。我们可以看到系统页面已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 系统页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常的设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-token.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-token.md index 674f2b56e02..e7b2bdd14f0 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-token.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http-example-token.md @@ -1,6 +1,6 @@ --- id: extend-http-example-token -title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 +title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 sidebar_label: 教程二:获取TOKEN后续认证使用 --- @@ -221,13 +221,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **新增成功后我们就可以在详情页面看到我们采集的 `token`, `refreshToken`指标数据。** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### 将`token`作为变量参数给后面的监控指标采集使用 @@ -381,15 +381,15 @@ metrics: **配置完成后，再次重启 `hertzbeat` 系统，查看监控详情页面** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http.md index 65a740c5a4c..e8aa27520be 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-http.md @@ -1,6 +1,6 @@ --- -id: extend-http -title: HTTP协议自定义监控 +id: extend-http +title: HTTP协议自定义监控 sidebar_label: HTTP协议自定义监控 --- @@ -20,7 +20,7 @@ HTTP协议支持我们自定义HTTP请求路径，请求header，请求参数， **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jdbc.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jdbc.md index c1e6545e4f4..50a56c366ca 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jdbc.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jdbc.md @@ -1,6 +1,6 @@ --- -id: extend-jdbc -title: JDBC协议自定义监控 +id: extend-jdbc +title: JDBC协议自定义监控 sidebar_label: JDBC协议自定义监控 --- @@ -57,7 +57,7 @@ SQL响应数据： **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jmx.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jmx.md index b4dadf8cfde..b906de82547 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jmx.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-jmx.md @@ -1,6 +1,6 @@ --- -id: extend-jmx -title: JMX协议自定义监控 +id: extend-jmx +title: JMX协议自定义监控 sidebar_label: JMX协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: JMX协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ngql.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ngql.md index 23b404986c5..93751b7a678 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ngql.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ngql.md @@ -13,18 +13,18 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 ### **filterCount** > -> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 -> commands字段语法格式: aliasField#NGQL#filterName#filterValue -> `aliasField`: 对应监控模板中的`aliasFields`中的值 -> `NGQL`: 查询语句 -> `filterName`: 过滤属性名称（可选） +> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 +> commands字段语法格式: aliasField#NGQL#filterName#filterValue +> `aliasField`: 对应监控模板中的`aliasFields`中的值 +> `NGQL`: 查询语句 +> `filterName`: 过滤属性名称（可选） > `filterValue`: 过滤属性值（可选） 例如： -- online_meta_count#SHOW HOSTS META#Status#ONLINE +- online_meta_count#SHOW HOSTS META#Status#ONLINE 对 `SHOW HOSTS META` 返回的结果中统计滤Status==ONLINE的数量 -- online_meta_count#SHOW HOSTS META## +- online_meta_count#SHOW HOSTS META## 统计 `SHOW HOSTS META` 返回的行数 #### **oneRow** @@ -50,7 +50,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 例如： -- 查询的指标字段为：a,b +- 查询的指标字段为：a,b - 查询NGQL：match (v:metrics) return v.metrics.a as a,v.metrics.b as b; 这里指标字段就能和响应数据一一映射为多行采集数据。 @@ -71,7 +71,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -168,7 +168,7 @@ metrics: parseType: columns # 定义采集数据使用的查询语句 commands: - - match (v:tag1) return "tag1" as name ,count(v) as cnt + - match (v:tag1) return "tag1" as name ,count(v) as cnt - match (v:tag2) return "tag2" as name ,count(v) as cnt timeout: ^_^timeout^_^ ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-point.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-point.md index 45e56692693..e4476822739 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-point.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-point.md @@ -1,17 +1,17 @@ --- -id: extend-point -title: 自定义监控 +id: extend-point +title: 自定义监控 sidebar_label: 自定义监控 --- -> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 +> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 > 目前自定义监控支持[HTTP协议](extend-http)，[JDBC协议](extend-jdbc)，[SSH协议](extend-ssh)，[JMX协议](extend-jmx)，[SNMP协议](extend-snmp)，后续会支持更多通用协议。 ## 自定义流程 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ### 自定义监控指标刷新时间 @@ -139,7 +139,7 @@ params: # hide param-true or false # 是否隐藏字段 true or false hide: true - + metrics: # metrics - summary, inner monitoring metrics (responseTime - response time, keyword - number of keywords) # 监控指标 - summary, 内置监控指标有 (responseTime - 响应时间, keyword - 关键字数量) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-push.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-push.md index d938b5cddfb..6b1d59b4112 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-push.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat页面 -> 应用服务监控 -> 推送方式监控 -> 新建推送方 ### 监控配置示例 -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-snmp.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-snmp.md index 018feed6f46..b24c30c5e9c 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-snmp.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-snmp.md @@ -1,6 +1,6 @@ --- -id: extend-snmp -title: SNMP协议自定义监控 +id: extend-snmp +title: SNMP协议自定义监控 sidebar_label: SNMP协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: SNMP协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ssh.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ssh.md index 9b19f2ae987..b1e2020c294 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ssh.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-ssh.md @@ -1,6 +1,6 @@ --- -id: extend-ssh -title: SSH协议自定义监控 +id: extend-ssh +title: SSH协议自定义监控 sidebar_label: SSH协议自定义监控 --- @@ -31,7 +31,7 @@ SHELL脚本查询回来的数据字段和我们需要的指标映射，就能获 ```shell tombook -14:00:15 up 72 days +14:00:15 up 72 days ``` 则最后采集到的指标数据一一映射为： @@ -54,7 +54,7 @@ Mem: 7962 4065 333 1 3562 3593 Swap: 8191 33 8158 ``` -在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： +在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： `free -m | grep Mem | awk 'BEGIN{print "total used free buff_cache available"} {print $2,$3,$4,$6,$7}'` 控制台响应为： @@ -69,7 +69,7 @@ total used free buff_cache available **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-telnet.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-telnet.md index dfaf2a5a714..34185e8e3c4 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-telnet.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-telnet.md @@ -1,6 +1,6 @@ --- -id: extend-telnet -title: Telnet协议自定义监控 +id: extend-telnet +title: Telnet协议自定义监控 sidebar_label: Telnet协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: Telnet协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-tutorial.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-tutorial.md index eecf853395c..2cd49874487 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-tutorial.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/advanced/extend-tutorial.md @@ -1,6 +1,6 @@ --- id: extend-tutorial -title: 自定义适配一款基于HTTP协议的新监控类型 +title: 自定义适配一款基于HTTP协议的新监控类型 sidebar_label: 教程案例 --- @@ -227,25 +227,25 @@ metrics: **点击保存并应用。我们可以看到系统页面的自定义监控菜单已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/new_committer_process.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/new_committer_process.md index aa4cb00058d..4180ddb8024 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/new_committer_process.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/new_committer_process.md @@ -355,15 +355,15 @@ hi, i accept. Thanks for invitaion. 找到`CLAs`点击进入页面 - ![HertzBeat](/img/docs/community/clas-web.png) + ![HertzBeat](home/static/img/docs/community/clas-web.png) 找到`ICLA(个人贡献者许可协议)`，点击[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) - ![HertzBeat](/img/docs/community/icla-web.png) + ![HertzBeat](home/static/img/docs/community/icla-web.png) 跳转后，会显示需要签署的协议，这里可以在网页上直接填写，也可以下载后填写。 - ![HertzBeat](/img/docs/community/icla-pdf.png) + ![HertzBeat](home/static/img/docs/community/icla-pdf.png) 2. 填写iCLA @@ -371,8 +371,8 @@ hi, i accept. Thanks for invitaion. 需要填写的内容： - ![HertzBeat](/img/docs/community/icla-content-1.png) - ![HertzBeat](/img/docs/community/icla-content-2.png) + ![HertzBeat](home/static/img/docs/community/icla-content-1.png) + ![HertzBeat](home/static/img/docs/community/icla-content-2.png) 在PDF中需要填写的字段： @@ -386,12 +386,12 @@ hi, i accept. Thanks for invitaion. - `Date` > 填写样例 - > ![HertzBeat](/img/docs/community/icla-content-3.png) - > ![HertzBeat](/img/docs/community/icla-content-4.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-3.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-4.png) 3. 打印并签署 - ![HertzBeat](/img/docs/community/icla-content-5.png) + ![HertzBeat](home/static/img/docs/community/icla-content-5.png) `Please sign`字段需要将文件打印出来然后手写签名，内容为自己姓名的全拼。 @@ -423,7 +423,7 @@ hi, i accept. Thanks for invitaion. 在网站 [https://id.apache.org/reset/enter](https://id.apache.org/reset/enter) 输入您的Apache ID -![HertzBeat](/img/docs/community/account-1.png) +![HertzBeat](home/static/img/docs/community/account-1.png) 点击`Send Email`后会提示发送成功。 @@ -437,44 +437,44 @@ hi, i accept. Thanks for invitaion. 登录后可以看到这个内容`Link GitHub username to ASF id`，点击跳转 -![HertzBeat](/img/docs/community/account-2.png) +![HertzBeat](home/static/img/docs/community/account-2.png) 输入您的Apache的账号和密码并登录 -![HertzBeat](/img/docs/community/account-3.png) +![HertzBeat](home/static/img/docs/community/account-3.png) 点击 `Authenticate with GitHub` -![HertzBeat](/img/docs/community/account-4.png) +![HertzBeat](home/static/img/docs/community/account-4.png) 点击`Authorize apache`授权给Apache -![HertzBeat](/img/docs/community/account-5.png) +![HertzBeat](home/static/img/docs/community/account-5.png) 点击`Send GitHub Invitation!` 发送GitHub邀请邮件 -![HertzBeat](/img/docs/community/account-6.png) +![HertzBeat](home/static/img/docs/community/account-6.png) 邮箱中会收到一封邮件，点击`Join @apache` > 这里邮箱指的是您提供给PMC的那个邮箱地址 -![HertzBeat](/img/docs/community/account-7.png) +![HertzBeat](home/static/img/docs/community/account-7.png) 点击`Join The Apache Software Foundation`，加入GitHub加入Apache组织，会自动跳转到GitHub页面 -![HertzBeat](/img/docs/community/account-8.png) -![HertzBeat](/img/docs/community/account-9.png) +![HertzBeat](home/static/img/docs/community/account-8.png) +![HertzBeat](home/static/img/docs/community/account-9.png) 回到Apache页面，提示GitHub启用多重身份认证，在GitHub页面启用双重身份认证 > GitHub双重身份认证介绍，[点击跳转官方文档](https://docs.github.com/zh/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication) -![HertzBeat](/img/docs/community/account-10.png) +![HertzBeat](home/static/img/docs/community/account-10.png) 启动完成之后等几分钟，提示已经绑定完成 -![HertzBeat](/img/docs/community/account-11.png) +![HertzBeat](home/static/img/docs/community/account-11.png) 至此您的GitHub账号与Apache账号就绑定完成了。 @@ -488,17 +488,17 @@ hi, i accept. Thanks for invitaion. 进入设置页面，并点击`添加其他电子邮件地址`` -![HertzBeat](/img/docs/community/email-1.png) +![HertzBeat](home/static/img/docs/community/email-1.png) 填写您的apache邮箱，按照指引点击下一步 -![HertzBeat](/img/docs/community/email-2.png) -![HertzBeat](/img/docs/community/email-3.png) -![HertzBeat](/img/docs/community/email-4.png) +![HertzBeat](home/static/img/docs/community/email-2.png) +![HertzBeat](home/static/img/docs/community/email-3.png) +![HertzBeat](home/static/img/docs/community/email-4.png) 设置为默认发送邮箱(可选) -![HertzBeat](/img/docs/community/email-5.png) +![HertzBeat](home/static/img/docs/community/email-5.png) 配置完成。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/alert_threshold.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/alert_threshold.md index 4e553600f66..f84ada65e92 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/alert_threshold.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/alert_threshold.md @@ -1,12 +1,12 @@ --- -id: alert_threshold -title: 告警阈值规则配置 +id: alert_threshold +title: 告警阈值规则配置 sidebar_label: 阈值规则 --- :::tip -告警阈值规则是 `HertzBeat` 的核心功能，用户可以通过阈值规则来配置告警的触发条件。 -阈值规则支持实时阈值和计划阈值，实时阈值可以在监控数据采集时直接触发告警，计划阈值支持 PromQL 等表达式在指定时间段内计算触发告警。 +告警阈值规则是 `HertzBeat` 的核心功能，用户可以通过阈值规则来配置告警的触发条件。 +阈值规则支持实时阈值和计划阈值，实时阈值可以在监控数据采集时直接触发告警，计划阈值支持 PromQL 等表达式在指定时间段内计算触发告警。 支持可视化页面配置或更高灵活性的表达式规则配置，支持配置触发次数，告警级别，通知模板，关联指定监控等。 ::: @@ -22,7 +22,7 @@ sidebar_label: 阈值规则 配置阈值，例如: 选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) 配置项说明： diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/redis_cluster.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/redis_cluster.md index 7d20acff065..17e8ddd513f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/redis_cluster.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/redis_cluster.md @@ -1,7 +1,7 @@ --- -id: redis_cluster -title: 监控：Redis Cluster 数据库监控 -sidebar_label: Redis Cluster数据库 +id: redis_cluster +title: 监控：Redis Cluster 数据库监控 +sidebar_label: Redis Cluster数据库 keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监控] --- @@ -98,7 +98,7 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 添加监控节点时填入所需要的参数. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) 最终的效果. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/status.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/status.md index dc688d023b8..8fc76886a76 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/status.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: 状态页面 -sidebar_label: 状态页面 +id: status +title: 状态页面 +sidebar_label: 状态页面 keywords: [开源监控系统, 开源网站监控, 状态页面] --- @@ -24,7 +24,7 @@ keywords: [开源监控系统, 开源网站监控, 状态页面] 填写完组织信息后，点击 `确定`。 -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. 新增组件 @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. 维护事件 @@ -59,7 +59,7 @@ status: 点击 `发布事件` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | 字段名称 | 字段说明 | 举例 | |------|---------------------------------------------|----------------------------------------------------------------------| @@ -70,4 +70,4 @@ status: > 提示：可以多次发布消息，及时向团队汇报当前状态。 -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/introduce.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/introduce.md index 6c13415f0f6..b2aa597ecec 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/introduce.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/introduce.md @@ -1,6 +1,6 @@ --- -id: introduce -title: Apache HertzBeat™ +id: introduce +title: Apache HertzBeat™ sidebar_label: 介绍 slug: / --- @@ -33,11 +33,11 @@ slug: / HertzBeat 自身并没有去创造一种采集数据协议让监控对端来适配它。而是充分使用了现有的生态，`SNMP协议`采集网络交换机路由器信息，`JMX规范`采集JAVA应用信息，`JDBC规范`采集数据集信息，`SSH`直连执行脚本获取回显信息，`HTTP+(JsonPath | prometheus等)`解析API接口信息，`IPMI协议`采集服务器信息等等。 HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可配置化，最后使其都可以通过编写YML格式监控模板的形式，来制定模板使用这些协议来采集任何想要的指标数据。 -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) 你相信用户只需在UI页面编写一个监控模板，点击保存后，就能立刻适配一款`K8s`或`Docker`等新的监控类型吗？ -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 内置监控类型 @@ -88,7 +88,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 > 我们将每个监控类型都视为一个监控模板，不管是官方内置的还是后期用户自定义新增的。用户都可以方便的通过修改监控模板来新增修改删除监控指标。 > 模板里面包含各个协议的使用配置，环境变量，指标转换，指标计算，单位转换，指标采集等一系列功能，帮助用户能采集到自己想要的监控指标。 -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### 无需 Agent @@ -110,7 +110,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 - 监控任务在采集器集群中自调度，单采集器挂掉无感知故障迁移采集任务，新加入采集器节点自动调度分担采集压力。 - 单机模式与集群模式相互切换部署非常方便，无需额外组件部署。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 云边协同 @@ -118,10 +118,10 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 - `HertzBeat` 支持部署边缘采集器集群，与主 `HertzBeat` 服务云边协同提升采集能力。 -在多个网络不相通的隔离网络中，在以往方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 +在多个网络不相通的隔离网络中，在以往方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 `HertzBeat` 提供的云边协同能力，可以在多个隔离网络部署边缘采集器，采集器在隔离网络内部进行监控任务采集，采集数据上报，由主服务统一调度管理展示。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 易用友好 @@ -156,7 +156,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - HertzBeat 的用户管理统一由配置文件 `sureness.yml` 维护，用户可以通过修改此文件来新增删除修改用户信息，用户角色权限等。默认账户密码 admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### 概览页面 @@ -164,7 +164,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 展示当前注册的采集器集群状态，包括采集器的上线状态，监控任务，启动时间，IP地址，名称等。 - 下发展示了最近告警信息列表，告警级别分布情况等。 -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### 监控中心 @@ -211,7 +211,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### 新增监控 @@ -219,7 +219,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 页面上配置的监控参数由对应监控类型的监控模板所定义，用户可以通过修改监控模板来修改页面配置参数。 - 支持关联标签，用标签来管理监控分组，告警匹配等。 -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### 监控详情 @@ -228,16 +228,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 监控历史数据报告，以趋势图表的形式展示了当前监控数值类型的指标的历史值，支持查询小时，天，月的历史数据，支持配置页面刷新时间。 - ⚠️注意监控历史图表需配置外置时序数据库才能获取完整功能。 -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### 告警中心 - 已触发告警消息的管理展示页面，使用户有直观的展示当前告警情况。 - 支持告警处理，告警标记未处理，告警删除清空等批量操作。 -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### 阈值规则 @@ -245,29 +245,29 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 阈值规则支持实时阈值和计划阈值，实时阈值可以在监控数据采集时直接触发告警，计划阈值支持 PromQL 等表达式在指定时间段内计算触发告警。 - 阈值规则支持可视化页面配置或更高灵活性的表达式规则配置，支持配置触发次数，告警级别，通知模板，关联指定监控等。 -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### 告警集成 - 统一管理不同第三方平台告警，集成接入第三方监控观测系统的告警消息，对其进行分组，收敛，抑制，静默，分发通知等。 -![HertzBeat](/img/home/11.png) +![HertzBeat](home/static/img/home/11.png) ### 告警分组 - 分组收敛支持对指定分组标签的告警进行分组合并，对时间段的相同重复告警去重收敛。 - 当阈值规则触发告警或外部告警上报后，会进入到分组收敛进行告警分组，告警去重，以避免大量告警消息导致告警风暴。 -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) ### 告警抑制 - 告警抑制用于配置告警之间的抑制关系，比如同一实例下高级别告警抑制低级别告警。 - 当某个告警发生时，可以抑制其他告警的产生。例如，当服务器宕机时，可以抑制该服务器上的所有告警。 -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### 告警静默 @@ -275,7 +275,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 此应用场景如用户在系统维护中，无需发已知告警。用户在工作日时间才会接收告警消息，用户在晚上需避免打扰等。 - 告警静默规则支持一次性时间段或周期性时间段，支持标签匹配和告警级别匹配。 -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### 消息通知 @@ -285,20 +285,20 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 通知策略支持标签匹配和告警级别匹配，方便的使不同标签的告警和告警级别分派给不同的接收处理人。 - 支持通知模板，用户可以自定义通过模板内容格式来满足自己的个性化通知展示需求。 -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) ### 监控模板 - HertzBeat 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需简单配置即可快速适配一款 `K8s` 或 `Docker` 等新的监控类型吗？ - 同理我们内置的所有监控类型(mysql,website,jvm,k8s)也一一映射为对应的监控模板，用户可以新增修改监控模板来自定义监控功能。 -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 采集集群 @@ -306,16 +306,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 采集器集群支持多节点部署，支持自动负载均衡，自动故障转移等。 - 支持多隔离网络的统一管理，云边协同。 -![HertzBeat](/img/home/18.png) +![HertzBeat](home/static/img/home/18.png) ### 状态页面 - 基于 HertzBeat 快速构建自己产品的对外状态页，轻松向用户传达您产品服务的实时状态。例如 Github 提供的服务状态页 [https://www.githubstatus.com](https://www.githubstatus.com)。 - 支持状态页组件状态和监控状态联动同步，故障事件维护管理机制等。提高您的透明度，专业度和用户信任，降低沟通成本。 -![HertzBeat](/img/home/19.png) +![HertzBeat](home/static/img/home/19.png) -![HertzBeat](/img/home/status.png) +![HertzBeat](home/static/img/home/status.png) --- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/baota-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/baota-deploy.md index 0bbfa27cf5e..f6acf556b77 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/baota-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: 使用 宝塔面板 部署 HertzBeat +id: baota-deploy +title: 使用 宝塔面板 部署 HertzBeat sidebar_label: 基于宝塔面板部署 --- @@ -16,15 +16,15 @@ Apache HertzBeat™ 支持在宝塔面板的 `Docker` 应用商店一键部署 > 在宝塔面板安装 Docker 服务，若已有则跳过。 - ![HertzBeat](/img/docs/start/install-to-baota-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-1.png) 2. 在`Docker-应用商店`中找到 `HertzBeat`，点击`安装` - ![HertzBeat](/img/docs/start/install-to-baota-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-2.png) 3. 设置域名等基本信息，点击`确定` - ![HertzBeat](/img/docs/start/install-to-baota-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-3.png) - 名称：应用名称，默认`HertzBeat-随机字符` - 版本选择：默认`latest` @@ -39,6 +39,6 @@ Apache HertzBeat™ 支持在宝塔面板的 `Docker` 应用商店一键部署 - 如您设置了域名，请直接在浏览器地址栏中输入域名访问，如`http://demo.hertzbeat.apache.org`，即可访问 `HertzBeat` 控制台。 - 如您选择了通过`IP+Port`访问，请在浏览器地址栏中输入域名访问 `http://<宝塔面板IP>:1157`，即可访问 `HertzBeat` 控制台。 -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > 默认用户名`admin`默认密码`hertzbeat` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/docker-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/docker-deploy.md index c4cb4844c94..bc5e08e1541 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/docker-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/docker-deploy.md @@ -1,11 +1,11 @@ --- -id: docker-deploy -title: 通过 Docker 方式安装 HertzBeat +id: docker-deploy +title: 通过 Docker 方式安装 HertzBeat sidebar_label: Docker方式安装 --- :::tip -使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 +使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 但不建议在生产环境中使用，生产环境建议使用 Docker Compose 方式部署, 安装包方式部署, Kubernetes 方式部署。 ::: @@ -49,17 +49,17 @@ sidebar_label: Docker方式安装 ::: -2. 开始探索 HertzBeat +2. 开始探索 HertzBeat 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用HertzBeat，默认账户密码 admin/hertzbeat。 ### 部署 HertzBeat Collector 集群(可选) :::note -HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 +HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 执行以下命令 @@ -92,7 +92,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 ::: -2. 开始探索 HertzBeat Collector +2. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -106,33 +106,33 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. MYSQL,TDENGINE或IotDB和HertzBeat都Docker部署在同一主机上，HertzBeat使用localhost或127.0.0.1连接数据库失败 此问题本质为Docker容器访问宿主机端口连接失败，由于docker默认网络模式为Bridge模式，其通过localhost访问不到宿主机。 - > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP + > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP > 解决办法二：使用Host网络模式启动Docker，即使Docker容器和宿主机共享网络 `docker run -d --network host .....` 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以 `docker logs hertzbeat` 查看容器日志是否有明显错误，提issue或交流群或社区反馈 3. 监控页面历史图表不显示，弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - + > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - > 安装初始化此时序数据库 4. 安装配置了时序数据库，但页面依旧显示弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 请检查配置的时许数据库参数是否正确 - > 时序数据库对应的 enable 是否设置为true - > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP + > 请检查配置的时许数据库参数是否正确 + > 时序数据库对应的 enable 是否设置为true + > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP > 可根据logs目录下启动日志排查 5. application.yml 是干什么用的 > 此文件是HertzBeat的配置文件，用于配置HertzBeat的各种参数，如数据库连接信息，时序数据库配置等。 - 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml + 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml 下载源 [github/script/application.yml](https://github.com/apache/hertzbeat/raw/master/script/application.yml) - 若需使用邮件发送告警，需替换 `application.yml` 里面的邮件服务器参数 @@ -143,8 +143,8 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 > 此文件是HertzBeat的用户配置文件，用于配置HertzBeat的用户信息，如账户密码等。 - HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat - 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 - 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml - 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 + 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml + 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) 具体修改步骤参考 [配置修改账户密码](account-modify) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/package-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/package-deploy.md index 8759ee12c6f..90cb3707a33 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/package-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/package-deploy.md @@ -1,6 +1,6 @@ --- -id: package-deploy -title: 通过安装包安装 HertzBeat +id: package-deploy +title: 通过安装包安装 HertzBeat sidebar_label: 安装包方式安装 --- @@ -40,7 +40,7 @@ Apache HertzBeat™ 支持在Linux Windows Mac系统安装运行，CPU支持X86/ 3. 配置账户文件(可选) - HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat 若需要新增删除修改账户或密码，可以通过修改位于 `config/sureness.yml` 的配置文件实现，具体参考 - [配置修改账户密码](account-modify) @@ -50,7 +50,7 @@ Apache HertzBeat™ 支持在Linux Windows Mac系统安装运行，CPU支持X86/ 执行位于安装目录 bin 下的启动脚本 startup.sh, windows 环境下为 startup.bat ```shell - ./startup.sh + ./startup.sh ``` 5. 开始探索HertzBeat @@ -63,7 +63,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 下载安装包 @@ -103,10 +103,10 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 执行位于安装目录 hertzbeat-collector/bin/ 下的启动脚本 startup.sh, windows 环境下为 startup.bat ```shell - ./startup.sh + ./startup.sh ``` -4. 开始探索 HertzBeat Collector +4. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -119,9 +119,9 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. 启动失败，需您提前准备JAVA运行环境 - 安装JAVA运行环境-可参考[官方网站](https://www.oracle.com/java/technologies/downloads/) + 安装JAVA运行环境-可参考[官方网站](https://www.oracle.com/java/technologies/downloads/) 要求：JAVA17环境 - 下载JAVA安装包: [镜像站](https://mirrors.huaweicloud.com/openjdk/) + 下载JAVA安装包: [镜像站](https://mirrors.huaweicloud.com/openjdk/) 安装后命令行检查是否成功安装 ```shell @@ -134,6 +134,6 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `hertzbeat/config/application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `hertzbeat/config/application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以查看 `hertzbeat/logs/` 目录下面的运行日志是否有明显错误，提issue或交流群或社区反馈 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/rainbond-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/rainbond-deploy.md index 4ed3002af86..adbfcac881f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/rainbond-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: 使用 Rainbond 部署 HertzBeat +id: rainbond-deploy +title: 使用 Rainbond 部署 HertzBeat sidebar_label: 基于Rainbond部署 --- @@ -32,7 +32,7 @@ sidebar_label: 基于Rainbond部署 登录 Rainbond 后，点击左侧菜单中的 `应用市场`，切换到开源应用商店，在搜索框中搜索 `HertzBeat`，点击安装按钮。 -![HertzBeat](/img/docs/start/install-to-rainbond.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond.png) 填写以下信息，然后点击确认按钮进行安装。 @@ -43,7 +43,7 @@ sidebar_label: 基于Rainbond部署 等待安装完成，即可访问 HertzBeat 应用。 -![HertzBeat](/img/docs/start/hertzbeat-topology.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology.png) :::tip 通过 Rainbond 安装的 HertzBeat，默认使用了外部的 Mysql 数据库 和 Redis 以及 IoTDB。同时也挂载了 HertzBeat 的配置文件，可以在 `组件 -> 环境配置 -> 配置文件设置` 中修改配置文件。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/linux-os-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/linux-os-practice.md index 48d51421dc5..508dfc58a1b 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/linux-os-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/linux-os-practice.md @@ -32,7 +32,7 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 操作系统监控 -> Linux 操作系统 -> 新增 Linux 操作系统监控 -![HertzBeat](/img/docs/start/linux-os-practice-1.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-1.png) ### 2. 配置参数 @@ -47,15 +47,15 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 可以使用标签分类来管理任务，如添加`OS=Linux`等相关标签。 -![HertzBeat](/img/docs/start/linux-os-practice-2.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-2.png) ### 3. 查看监控数据 在监控列表可以查看任务状态，点击这个监控详情可以查看指标数据图表等。 -![HertzBeat](/img/docs/start/linux-os-practice-3.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-3.png) -![HertzBeat](/img/docs/start/linux-os-practice-4.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-4.png) ### 4. 设置阈值规则 @@ -65,27 +65,27 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > > 配置阈值，配置告警表达式-当指标`文件系统使用率`大于等于 `50%` 触发，也支持设置告警级别和通知模板信息等。 -![HertzBeat](/img/docs/start/linux-os-practice-5.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 最终可以在告警中心看到已触发的告警。 -![HertzBeat](/img/docs/start/linux-os-practice-6.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-6.png) ### 5. 消息通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 -![HertzBeat](/img/docs/start/linux-os-practice-7.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-7.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 -![HertzBeat](/img/docs/start/linux-os-practice-8.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-8.png) 当阈值触发后就可以收到对应告警消息，如果没有配置消息通知，也可以在**告警中心**查看告警信息。 ----- +---- ## 总结 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/springboot-auto-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/springboot-auto-practice.md index 1564b1b6bb2..38f73e15a11 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/springboot-auto-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/springboot-auto-practice.md @@ -1,7 +1,7 @@ --- -id: springboot-auto-practice -title: SpringBoot Web应用监控案例 -sidebar_label: SpringBoot Web应用监控案例 +id: springboot-auto-practice +title: SpringBoot Web应用监控案例 +sidebar_label: SpringBoot Web应用监控案例 --- :::tip @@ -141,7 +141,7 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > 系统页面 -> 监控中心 -> 新增监控 -> AUTO -> Prometheus任务 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-1.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-1.png) 2. 填写关键参数 @@ -153,16 +153,16 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-2.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-2.png) 3. 查看检测指标数据 > 点击进入新建监控，可以查看指标数据详情及指标历史图表等。 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-3.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-3.png) - ![HertzBeat](/img/docs/start/springboot-auto-practice-4.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-4.png) ## Grafana可视化集成 (可选) @@ -181,13 +181,13 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 比如：Grafana 数据源选择`hertzbeat-victoria-metrics`，然后在仪表盘点击:「Share」→「Export」→「Save to file」下载模板并上传至 HertzBeat 监控中。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-5.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-5.png) 3. 查看 Grafana 图表 > 进入新增 AUTO 监控页面，点击 Grafana 图标按钮，即可查看 Grafana 图表。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-6.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-6.png) ## 告警与通知联动 @@ -196,7 +196,7 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > 系统页面 -> 告警 -> 阈值规则 -> 新增 -> 新增阈值 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-7.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-7.png) > HertzBeat 提供了 **实时计算** 和 **计划周期** 两种类型的阈值规则设置，这里我们以 **计划周期** 阈值规则为例。 > @@ -213,24 +213,24 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 可以设置的阈值规则组合有很多，用户可以根据自身需要设置更丰富的告警规则。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-8.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-8.png) > 最后可以在 告警中心 看到已触发的告警。 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-9.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-9.png) 3. 告警通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-10.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-10.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-11.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-11.png) 4. OK！当阈值规则触发后我们就可以收到对应告警消息啦，如果没有配置通知，也可以在告警中心查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/sslcert-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/sslcert-practice.md index 6e5dcc59a59..8c06c4863b8 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/sslcert-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL 证书过期监控案例 +id: ssl-cert-practice +title: SSL 证书过期监控案例 sidebar_label: SSL 证书过期监控案例 --- @@ -34,28 +34,28 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 应用服务监控 -> SSL 证书 -> 新增 SSL 证书 - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. 配置监控网站 > 我们这里举例监控百度网站, 配置监控host域名，名称，采集间隔等。 - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. 设置阈值(证书过期时触发) - > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 + > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 > 配置阈值，选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 @@ -63,17 +63,17 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 同理如上，选择代码阈值规则，新增配置阈值，配置告警表达式-当指标有效期时间戳 `end_timestamp`，`now()`函数为当前时间戳，若配置提前一周触发告警即：`end_timestamp <= (now() + 604800000)` , 其中 `604800000` 为7天总时间差毫秒值。 - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > 最终可以在告警中心看到已触发的告警。 - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. 告警通知(通过钉钉微信飞书等及时通知) > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) 钉钉微信飞书等 token 配置可以参考帮助文档 @@ -81,11 +81,11 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 消息通知 -> 通知策略 -> 新增告警通知策略 -> 将刚才配置的接收人启用通知 - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK 当阈值触发后我们就可以收到对应告警消息啦，如果没有配通知，也可以在告警中心查看告警信息。 ----- +---- ## 结束搞定 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/tdengine-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/tdengine-practice.md index 5fe1e5e49ac..452c432a803 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/tdengine-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/start/usecase/tdengine-practice.md @@ -1,6 +1,6 @@ --- -id: tdengine-practice -title: TDengine 监控案例 +id: tdengine-practice +title: TDengine 监控案例 sidebar_label: TDengine 监控案例 --- @@ -40,7 +40,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 监控中心 -> 新增监控 -> 自定义监控 -> TDengine-PromQL任务 - ![HertzBeat](/img/docs/start/tdengine_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1.png) 2. 填写关键参数 @@ -52,15 +52,15 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/tdengine_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/tdengine_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_3.png) - ![HertzBeat](/img/docs/start/tdengine_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_4.png) ## 监控 TDengine(Prometheus) @@ -68,7 +68,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 监控中心 -> 新增监控 -> AUTO -> Prometheus任务 - ![HertzBeat](/img/docs/start/tdengine_1_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_1.png) 2. 填写关键参数 @@ -80,15 +80,15 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/tdengine_1_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/tdengine_1_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_3.png) - ![HertzBeat](/img/docs/start/tdengine_1_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_4.png) ### Grafana可视化集成 (可选) @@ -107,13 +107,13 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 比如：Grafana 数据源选择`hertzbeat-victoria-metrics`，然后在仪表盘点击:「Share」→「Export」→「Save to file」下载模板并上传至 HertzBeat 监控中，可参考：[taoskeeper-prometheus-dashboard](https://grafana.com/grafana/dashboards/15164-taoskeeper-prometheus-dashboard/) - ![HertzBeat](/img/docs/start/tdengine_1_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_5.png) 3. 查看 Grafana 图表 > 进入新增 AUTO 监控页面，点击 Grafana 图标按钮，即可查看 Grafana 图表。 - ![HertzBeat](/img/docs/start/tdengine_1_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_6.png) ## 告警与通知联动 @@ -122,7 +122,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 告警 -> 阈值规则 -> 新增 -> 新增阈值 > - ![HertzBeat](/img/docs/start/tdengine_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_5.png) > HertzBeat 提供了 **实时计算** 和 **计划周期** 两种类型的阈值规则设置，这里我们以 **计划周期** 阈值规则为例。 > @@ -139,24 +139,24 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以设置的阈值规则组合有很多，用户可以根据自身需要设置更丰富的告警规则。 - ![HertzBeat](/img/docs/start/tdengine_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_6.png) > 最后可以在 告警中心 看到已触发的告警。 > - ![HertzBeat](/img/docs/start/tdengine_7.png) + ![HertzBeat](home/static/img/docs/start/tdengine_7.png) 3. 告警通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 > - ![HertzBeat](/img/docs/start/tdengine_8.png) + ![HertzBeat](home/static/img/docs/start/tdengine_8.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 > - ![HertzBeat](/img/docs/start/tdengine_9.png) + ![HertzBeat](home/static/img/docs/start/tdengine_9.png) 4. OK！当阈值规则触发后我们就可以收到对应告警消息啦，如果没有配置通知，也可以在告警中心查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/template.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/template.md index 5ee81d6b8bf..3951cbb4f2b 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/template.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/template.md @@ -1,6 +1,6 @@ --- -id: template -title: 监控模板中心 +id: template +title: 监控模板中心 sidebar_label: 监控模板 --- @@ -11,11 +11,11 @@ sidebar_label: 监控模板 这是它的架构原理: -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **我们将所有监控采集类型(mysql,website,jvm,k8s)都定义为yml模板，用户可以导入这些模板到hertzbeat系统中，使其支持对应类型的监控，非常方便！** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **欢迎大家一起贡献你使用过程中自定义的通用监控类型YML模板，可用的模板如下:** diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md index f99807576ba..db74cfbd148 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md @@ -1,6 +1,6 @@ --- id: extend-http-example-hertzbeat -title: 教程一:适配一款基于HTTP协议的监控类型 +title: 教程一:适配一款基于HTTP协议的监控类型 sidebar_label: 教程一:适配一款HTTP协议监控 --- @@ -188,25 +188,25 @@ metrics: **新增完毕，现在我们重启hertzbeat系统。我们可以看到系统页面已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 系统页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常的设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-token.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-token.md index 674f2b56e02..e7b2bdd14f0 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-token.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http-example-token.md @@ -1,6 +1,6 @@ --- id: extend-http-example-token -title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 +title: 教程二:基于HTTP协议获取TOKEN指标值，给后续采集认证使用 sidebar_label: 教程二:获取TOKEN后续认证使用 --- @@ -221,13 +221,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **新增成功后我们就可以在详情页面看到我们采集的 `token`, `refreshToken`指标数据。** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### 将`token`作为变量参数给后面的监控指标采集使用 @@ -381,15 +381,15 @@ metrics: **配置完成后，再次重启 `hertzbeat` 系统，查看监控详情页面** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http.md index 65a740c5a4c..e8aa27520be 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-http.md @@ -1,6 +1,6 @@ --- -id: extend-http -title: HTTP协议自定义监控 +id: extend-http +title: HTTP协议自定义监控 sidebar_label: HTTP协议自定义监控 --- @@ -20,7 +20,7 @@ HTTP协议支持我们自定义HTTP请求路径，请求header，请求参数， **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jdbc.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jdbc.md index c1e6545e4f4..50a56c366ca 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jdbc.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jdbc.md @@ -1,6 +1,6 @@ --- -id: extend-jdbc -title: JDBC协议自定义监控 +id: extend-jdbc +title: JDBC协议自定义监控 sidebar_label: JDBC协议自定义监控 --- @@ -57,7 +57,7 @@ SQL响应数据： **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jmx.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jmx.md index b4dadf8cfde..b906de82547 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jmx.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-jmx.md @@ -1,6 +1,6 @@ --- -id: extend-jmx -title: JMX协议自定义监控 +id: extend-jmx +title: JMX协议自定义监控 sidebar_label: JMX协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: JMX协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ngql.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ngql.md index 23b404986c5..93751b7a678 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ngql.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ngql.md @@ -13,18 +13,18 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 ### **filterCount** > -> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 -> commands字段语法格式: aliasField#NGQL#filterName#filterValue -> `aliasField`: 对应监控模板中的`aliasFields`中的值 -> `NGQL`: 查询语句 -> `filterName`: 过滤属性名称（可选） +> 对查询返回的结果按照指定字段进行过滤后，统计数量，通常用于 `SHOW ...` 语句中，如果可以使用NGQL语句直接返回数量的，建议使用NGQL语句统计数量。 +> commands字段语法格式: aliasField#NGQL#filterName#filterValue +> `aliasField`: 对应监控模板中的`aliasFields`中的值 +> `NGQL`: 查询语句 +> `filterName`: 过滤属性名称（可选） > `filterValue`: 过滤属性值（可选） 例如： -- online_meta_count#SHOW HOSTS META#Status#ONLINE +- online_meta_count#SHOW HOSTS META#Status#ONLINE 对 `SHOW HOSTS META` 返回的结果中统计滤Status==ONLINE的数量 -- online_meta_count#SHOW HOSTS META## +- online_meta_count#SHOW HOSTS META## 统计 `SHOW HOSTS META` 返回的行数 #### **oneRow** @@ -50,7 +50,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 例如： -- 查询的指标字段为：a,b +- 查询的指标字段为：a,b - 查询NGQL：match (v:metrics) return v.metrics.a as a,v.metrics.b as b; 这里指标字段就能和响应数据一一映射为多行采集数据。 @@ -71,7 +71,7 @@ NGQL查询回来的数据字段和我们需要的指标映射，就能获取对 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -168,7 +168,7 @@ metrics: parseType: columns # 定义采集数据使用的查询语句 commands: - - match (v:tag1) return "tag1" as name ,count(v) as cnt + - match (v:tag1) return "tag1" as name ,count(v) as cnt - match (v:tag2) return "tag2" as name ,count(v) as cnt timeout: ^_^timeout^_^ ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-point.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-point.md index 45e56692693..e4476822739 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-point.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-point.md @@ -1,17 +1,17 @@ --- -id: extend-point -title: 自定义监控 +id: extend-point +title: 自定义监控 sidebar_label: 自定义监控 --- -> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 +> HertzBeat拥有自定义监控能力，您只需配置监控模板YML就能适配一款自定义的监控类型。 > 目前自定义监控支持[HTTP协议](extend-http)，[JDBC协议](extend-jdbc)，[SSH协议](extend-ssh)，[JMX协议](extend-jmx)，[SNMP协议](extend-snmp)，后续会支持更多通用协议。 ## 自定义流程 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ### 自定义监控指标刷新时间 @@ -139,7 +139,7 @@ params: # hide param-true or false # 是否隐藏字段 true or false hide: true - + metrics: # metrics - summary, inner monitoring metrics (responseTime - response time, keyword - number of keywords) # 监控指标 - summary, 内置监控指标有 (responseTime - 响应时间, keyword - 关键字数量) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-push.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-push.md index d938b5cddfb..6b1d59b4112 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-push.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat页面 -> 应用服务监控 -> 推送方式监控 -> 新建推送方 ### 监控配置示例 -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-snmp.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-snmp.md index 018feed6f46..b24c30c5e9c 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-snmp.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-snmp.md @@ -1,6 +1,6 @@ --- -id: extend-snmp -title: SNMP协议自定义监控 +id: extend-snmp +title: SNMP协议自定义监控 sidebar_label: SNMP协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: SNMP协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ssh.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ssh.md index 9b19f2ae987..b1e2020c294 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ssh.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-ssh.md @@ -1,6 +1,6 @@ --- -id: extend-ssh -title: SSH协议自定义监控 +id: extend-ssh +title: SSH协议自定义监控 sidebar_label: SSH协议自定义监控 --- @@ -31,7 +31,7 @@ SHELL脚本查询回来的数据字段和我们需要的指标映射，就能获 ```shell tombook -14:00:15 up 72 days +14:00:15 up 72 days ``` 则最后采集到的指标数据一一映射为： @@ -54,7 +54,7 @@ Mem: 7962 4065 333 1 3562 3593 Swap: 8191 33 8158 ``` -在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： +在hertzbeat中multiRow格式解析需要响应数据列名称和指标值一一映射，则对应的查询SHELL脚本为： `free -m | grep Mem | awk 'BEGIN{print "total used free buff_cache available"} {print $2,$3,$4,$6,$7}'` 控制台响应为： @@ -69,7 +69,7 @@ total used free buff_cache available **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-telnet.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-telnet.md index dfaf2a5a714..34185e8e3c4 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-telnet.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-telnet.md @@ -1,6 +1,6 @@ --- -id: extend-telnet -title: Telnet协议自定义监控 +id: extend-telnet +title: Telnet协议自定义监控 sidebar_label: Telnet协议自定义监控 --- @@ -21,7 +21,7 @@ sidebar_label: Telnet协议自定义监控 **HertzBeat页面** -> **监控模板菜单** -> **新增监控类型** -> **配置自定义监控模板YML** -> **点击保存应用** -> **使用新监控类型添加监控** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-tutorial.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-tutorial.md index eecf853395c..2cd49874487 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-tutorial.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/advanced/extend-tutorial.md @@ -1,6 +1,6 @@ --- id: extend-tutorial -title: 自定义适配一款基于HTTP协议的新监控类型 +title: 自定义适配一款基于HTTP协议的新监控类型 sidebar_label: 教程案例 --- @@ -227,25 +227,25 @@ metrics: **点击保存并应用。我们可以看到系统页面的自定义监控菜单已经多了一个`hertzbeat`监控类型了。** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### 页面添加对`hertzbeat`监控类型的监控 > 我们点击新增 `HertzBeat监控系统`，配置监控IP，端口，采集周期，高级设置里的账户密码等, 点击确定添加监控。 -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > 过一定时间(取决于采集周期)我们就可以在监控详情看到具体的指标数据和历史图表啦！ -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### 设置阈值告警通知 > 接下来我们就可以正常设置阈值，告警触发后可以在告警中心查看，也可以新增接收人，设置告警通知等，Have Fun!!! ----- +---- #### 完 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/community/new_committer_process.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/community/new_committer_process.md index aa4cb00058d..4180ddb8024 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/community/new_committer_process.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/community/new_committer_process.md @@ -355,15 +355,15 @@ hi, i accept. Thanks for invitaion. 找到`CLAs`点击进入页面 - ![HertzBeat](/img/docs/community/clas-web.png) + ![HertzBeat](home/static/img/docs/community/clas-web.png) 找到`ICLA(个人贡献者许可协议)`，点击[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) - ![HertzBeat](/img/docs/community/icla-web.png) + ![HertzBeat](home/static/img/docs/community/icla-web.png) 跳转后，会显示需要签署的协议，这里可以在网页上直接填写，也可以下载后填写。 - ![HertzBeat](/img/docs/community/icla-pdf.png) + ![HertzBeat](home/static/img/docs/community/icla-pdf.png) 2. 填写iCLA @@ -371,8 +371,8 @@ hi, i accept. Thanks for invitaion. 需要填写的内容： - ![HertzBeat](/img/docs/community/icla-content-1.png) - ![HertzBeat](/img/docs/community/icla-content-2.png) + ![HertzBeat](home/static/img/docs/community/icla-content-1.png) + ![HertzBeat](home/static/img/docs/community/icla-content-2.png) 在PDF中需要填写的字段： @@ -386,12 +386,12 @@ hi, i accept. Thanks for invitaion. - `Date` > 填写样例 - > ![HertzBeat](/img/docs/community/icla-content-3.png) - > ![HertzBeat](/img/docs/community/icla-content-4.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-3.png) + > ![HertzBeat](home/static/img/docs/community/icla-content-4.png) 3. 打印并签署 - ![HertzBeat](/img/docs/community/icla-content-5.png) + ![HertzBeat](home/static/img/docs/community/icla-content-5.png) `Please sign`字段需要将文件打印出来然后手写签名，内容为自己姓名的全拼。 @@ -423,7 +423,7 @@ hi, i accept. Thanks for invitaion. 在网站 [https://id.apache.org/reset/enter](https://id.apache.org/reset/enter) 输入您的Apache ID -![HertzBeat](/img/docs/community/account-1.png) +![HertzBeat](home/static/img/docs/community/account-1.png) 点击`Send Email`后会提示发送成功。 @@ -437,44 +437,44 @@ hi, i accept. Thanks for invitaion. 登录后可以看到这个内容`Link GitHub username to ASF id`，点击跳转 -![HertzBeat](/img/docs/community/account-2.png) +![HertzBeat](home/static/img/docs/community/account-2.png) 输入您的Apache的账号和密码并登录 -![HertzBeat](/img/docs/community/account-3.png) +![HertzBeat](home/static/img/docs/community/account-3.png) 点击 `Authenticate with GitHub` -![HertzBeat](/img/docs/community/account-4.png) +![HertzBeat](home/static/img/docs/community/account-4.png) 点击`Authorize apache`授权给Apache -![HertzBeat](/img/docs/community/account-5.png) +![HertzBeat](home/static/img/docs/community/account-5.png) 点击`Send GitHub Invitation!` 发送GitHub邀请邮件 -![HertzBeat](/img/docs/community/account-6.png) +![HertzBeat](home/static/img/docs/community/account-6.png) 邮箱中会收到一封邮件，点击`Join @apache` > 这里邮箱指的是您提供给PMC的那个邮箱地址 -![HertzBeat](/img/docs/community/account-7.png) +![HertzBeat](home/static/img/docs/community/account-7.png) 点击`Join The Apache Software Foundation`，加入GitHub加入Apache组织，会自动跳转到GitHub页面 -![HertzBeat](/img/docs/community/account-8.png) -![HertzBeat](/img/docs/community/account-9.png) +![HertzBeat](home/static/img/docs/community/account-8.png) +![HertzBeat](home/static/img/docs/community/account-9.png) 回到Apache页面，提示GitHub启用多重身份认证，在GitHub页面启用双重身份认证 > GitHub双重身份认证介绍，[点击跳转官方文档](https://docs.github.com/zh/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication) -![HertzBeat](/img/docs/community/account-10.png) +![HertzBeat](home/static/img/docs/community/account-10.png) 启动完成之后等几分钟，提示已经绑定完成 -![HertzBeat](/img/docs/community/account-11.png) +![HertzBeat](home/static/img/docs/community/account-11.png) 至此您的GitHub账号与Apache账号就绑定完成了。 @@ -488,17 +488,17 @@ hi, i accept. Thanks for invitaion. 进入设置页面，并点击`添加其他电子邮件地址`` -![HertzBeat](/img/docs/community/email-1.png) +![HertzBeat](home/static/img/docs/community/email-1.png) 填写您的apache邮箱，按照指引点击下一步 -![HertzBeat](/img/docs/community/email-2.png) -![HertzBeat](/img/docs/community/email-3.png) -![HertzBeat](/img/docs/community/email-4.png) +![HertzBeat](home/static/img/docs/community/email-2.png) +![HertzBeat](home/static/img/docs/community/email-3.png) +![HertzBeat](home/static/img/docs/community/email-4.png) 设置为默认发送邮箱(可选) -![HertzBeat](/img/docs/community/email-5.png) +![HertzBeat](home/static/img/docs/community/email-5.png) 配置完成。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/alert_threshold.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/alert_threshold.md index 050ef5d7296..1caaa7eb96a 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/alert_threshold.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/alert_threshold.md @@ -24,7 +24,7 @@ sidebar_label: 阈值规则 配置阈值，例如: 选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) 配置项说明： diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/redis_cluster.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/redis_cluster.md index 7d20acff065..17e8ddd513f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/redis_cluster.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/redis_cluster.md @@ -1,7 +1,7 @@ --- -id: redis_cluster -title: 监控：Redis Cluster 数据库监控 -sidebar_label: Redis Cluster数据库 +id: redis_cluster +title: 监控：Redis Cluster 数据库监控 +sidebar_label: Redis Cluster数据库 keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监控] --- @@ -98,7 +98,7 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [开源监控系统, 开源数据库监控, RedisCluster数据库监 添加监控节点时填入所需要的参数. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) 最终的效果. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/status.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/status.md index ad2819fba23..4c2644b39a1 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/status.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: 状态页面 -sidebar_label: 状态页面 +id: status +title: 状态页面 +sidebar_label: 状态页面 keywords: [开源监控系统, 开源网站监控, 状态页面] --- @@ -24,7 +24,7 @@ keywords: [开源监控系统, 开源网站监控, 状态页面] 填写完组织信息后，点击 `确定`。 -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. 新增组件 @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. 维护事件 @@ -59,7 +59,7 @@ status: 点击 `发布事件` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | 字段名称 | 字段说明 | 举例 | |------|---------------------------------------------|----------------------------------------------------------------------| @@ -70,4 +70,4 @@ status: > 提示：可以多次发布消息，及时向团队汇报当前状态。 -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/introduce.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/introduce.md index 6c13415f0f6..b2aa597ecec 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/introduce.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/introduce.md @@ -1,6 +1,6 @@ --- -id: introduce -title: Apache HertzBeat™ +id: introduce +title: Apache HertzBeat™ sidebar_label: 介绍 slug: / --- @@ -33,11 +33,11 @@ slug: / HertzBeat 自身并没有去创造一种采集数据协议让监控对端来适配它。而是充分使用了现有的生态，`SNMP协议`采集网络交换机路由器信息，`JMX规范`采集JAVA应用信息，`JDBC规范`采集数据集信息，`SSH`直连执行脚本获取回显信息，`HTTP+(JsonPath | prometheus等)`解析API接口信息，`IPMI协议`采集服务器信息等等。 HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可配置化，最后使其都可以通过编写YML格式监控模板的形式，来制定模板使用这些协议来采集任何想要的指标数据。 -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) 你相信用户只需在UI页面编写一个监控模板，点击保存后，就能立刻适配一款`K8s`或`Docker`等新的监控类型吗？ -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 内置监控类型 @@ -88,7 +88,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 > 我们将每个监控类型都视为一个监控模板，不管是官方内置的还是后期用户自定义新增的。用户都可以方便的通过修改监控模板来新增修改删除监控指标。 > 模板里面包含各个协议的使用配置，环境变量，指标转换，指标计算，单位转换，指标采集等一系列功能，帮助用户能采集到自己想要的监控指标。 -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### 无需 Agent @@ -110,7 +110,7 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 - 监控任务在采集器集群中自调度，单采集器挂掉无感知故障迁移采集任务，新加入采集器节点自动调度分担采集压力。 - 单机模式与集群模式相互切换部署非常方便，无需额外组件部署。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 云边协同 @@ -118,10 +118,10 @@ HertzBeat 使用这些已有的标准协议或规范，将他们抽象规范可 - `HertzBeat` 支持部署边缘采集器集群，与主 `HertzBeat` 服务云边协同提升采集能力。 -在多个网络不相通的隔离网络中，在以往方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 +在多个网络不相通的隔离网络中，在以往方案中我们需要在每个网络都部署一套监控系统，这导致数据不互通，管理部署维护都不方便。 `HertzBeat` 提供的云边协同能力，可以在多个隔离网络部署边缘采集器，采集器在隔离网络内部进行监控任务采集，采集数据上报，由主服务统一调度管理展示。 -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### 易用友好 @@ -156,7 +156,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - HertzBeat 的用户管理统一由配置文件 `sureness.yml` 维护，用户可以通过修改此文件来新增删除修改用户信息，用户角色权限等。默认账户密码 admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### 概览页面 @@ -164,7 +164,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 展示当前注册的采集器集群状态，包括采集器的上线状态，监控任务，启动时间，IP地址，名称等。 - 下发展示了最近告警信息列表，告警级别分布情况等。 -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### 监控中心 @@ -211,7 +211,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### 新增监控 @@ -219,7 +219,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 页面上配置的监控参数由对应监控类型的监控模板所定义，用户可以通过修改监控模板来修改页面配置参数。 - 支持关联标签，用标签来管理监控分组，告警匹配等。 -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### 监控详情 @@ -228,16 +228,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 监控历史数据报告，以趋势图表的形式展示了当前监控数值类型的指标的历史值，支持查询小时，天，月的历史数据，支持配置页面刷新时间。 - ⚠️注意监控历史图表需配置外置时序数据库才能获取完整功能。 -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### 告警中心 - 已触发告警消息的管理展示页面，使用户有直观的展示当前告警情况。 - 支持告警处理，告警标记未处理，告警删除清空等批量操作。 -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### 阈值规则 @@ -245,29 +245,29 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 阈值规则支持实时阈值和计划阈值，实时阈值可以在监控数据采集时直接触发告警，计划阈值支持 PromQL 等表达式在指定时间段内计算触发告警。 - 阈值规则支持可视化页面配置或更高灵活性的表达式规则配置，支持配置触发次数，告警级别，通知模板，关联指定监控等。 -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### 告警集成 - 统一管理不同第三方平台告警，集成接入第三方监控观测系统的告警消息，对其进行分组，收敛，抑制，静默，分发通知等。 -![HertzBeat](/img/home/11.png) +![HertzBeat](home/static/img/home/11.png) ### 告警分组 - 分组收敛支持对指定分组标签的告警进行分组合并，对时间段的相同重复告警去重收敛。 - 当阈值规则触发告警或外部告警上报后，会进入到分组收敛进行告警分组，告警去重，以避免大量告警消息导致告警风暴。 -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) ### 告警抑制 - 告警抑制用于配置告警之间的抑制关系，比如同一实例下高级别告警抑制低级别告警。 - 当某个告警发生时，可以抑制其他告警的产生。例如，当服务器宕机时，可以抑制该服务器上的所有告警。 -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### 告警静默 @@ -275,7 +275,7 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 此应用场景如用户在系统维护中，无需发已知告警。用户在工作日时间才会接收告警消息，用户在晚上需避免打扰等。 - 告警静默规则支持一次性时间段或周期性时间段，支持标签匹配和告警级别匹配。 -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### 消息通知 @@ -285,20 +285,20 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 通知策略支持标签匹配和告警级别匹配，方便的使不同标签的告警和告警级别分派给不同的接收处理人。 - 支持通知模板，用户可以自定义通过模板内容格式来满足自己的个性化通知展示需求。 -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) ### 监控模板 - HertzBeat 将 `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` 等协议规范可配置化，只需在浏览器配置监控模板 `YML` 就能使用这些协议去自定义采集想要的指标。您相信只需简单配置即可快速适配一款 `K8s` 或 `Docker` 等新的监控类型吗？ - 同理我们内置的所有监控类型(mysql,website,jvm,k8s)也一一映射为对应的监控模板，用户可以新增修改监控模板来自定义监控功能。 -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### 采集集群 @@ -306,16 +306,16 @@ Docker 环境下运行一条命令即可：`docker run -d -p 1157:1157 -p 1158:1 - 采集器集群支持多节点部署，支持自动负载均衡，自动故障转移等。 - 支持多隔离网络的统一管理，云边协同。 -![HertzBeat](/img/home/18.png) +![HertzBeat](home/static/img/home/18.png) ### 状态页面 - 基于 HertzBeat 快速构建自己产品的对外状态页，轻松向用户传达您产品服务的实时状态。例如 Github 提供的服务状态页 [https://www.githubstatus.com](https://www.githubstatus.com)。 - 支持状态页组件状态和监控状态联动同步，故障事件维护管理机制等。提高您的透明度，专业度和用户信任，降低沟通成本。 -![HertzBeat](/img/home/19.png) +![HertzBeat](home/static/img/home/19.png) -![HertzBeat](/img/home/status.png) +![HertzBeat](home/static/img/home/status.png) --- diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/baota-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/baota-deploy.md index 0bbfa27cf5e..f6acf556b77 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/baota-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: 使用 宝塔面板 部署 HertzBeat +id: baota-deploy +title: 使用 宝塔面板 部署 HertzBeat sidebar_label: 基于宝塔面板部署 --- @@ -16,15 +16,15 @@ Apache HertzBeat™ 支持在宝塔面板的 `Docker` 应用商店一键部署 > 在宝塔面板安装 Docker 服务，若已有则跳过。 - ![HertzBeat](/img/docs/start/install-to-baota-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-1.png) 2. 在`Docker-应用商店`中找到 `HertzBeat`，点击`安装` - ![HertzBeat](/img/docs/start/install-to-baota-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-2.png) 3. 设置域名等基本信息，点击`确定` - ![HertzBeat](/img/docs/start/install-to-baota-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-baota-3.png) - 名称：应用名称，默认`HertzBeat-随机字符` - 版本选择：默认`latest` @@ -39,6 +39,6 @@ Apache HertzBeat™ 支持在宝塔面板的 `Docker` 应用商店一键部署 - 如您设置了域名，请直接在浏览器地址栏中输入域名访问，如`http://demo.hertzbeat.apache.org`，即可访问 `HertzBeat` 控制台。 - 如您选择了通过`IP+Port`访问，请在浏览器地址栏中输入域名访问 `http://<宝塔面板IP>:1157`，即可访问 `HertzBeat` 控制台。 -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > 默认用户名`admin`默认密码`hertzbeat` diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/docker-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/docker-deploy.md index c4cb4844c94..bc5e08e1541 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/docker-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/docker-deploy.md @@ -1,11 +1,11 @@ --- -id: docker-deploy -title: 通过 Docker 方式安装 HertzBeat +id: docker-deploy +title: 通过 Docker 方式安装 HertzBeat sidebar_label: Docker方式安装 --- :::tip -使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 +使用 Docker 方式一键启动 HertzBeat 最小可用环境，无外部服务依赖，方便快速体验。 但不建议在生产环境中使用，生产环境建议使用 Docker Compose 方式部署, 安装包方式部署, Kubernetes 方式部署。 ::: @@ -49,17 +49,17 @@ sidebar_label: Docker方式安装 ::: -2. 开始探索 HertzBeat +2. 开始探索 HertzBeat 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用HertzBeat，默认账户密码 admin/hertzbeat。 ### 部署 HertzBeat Collector 集群(可选) :::note -HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 +HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数据发送到 HertzBeat Server。 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 执行以下命令 @@ -92,7 +92,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 ::: -2. 开始探索 HertzBeat Collector +2. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -106,33 +106,33 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. MYSQL,TDENGINE或IotDB和HertzBeat都Docker部署在同一主机上，HertzBeat使用localhost或127.0.0.1连接数据库失败 此问题本质为Docker容器访问宿主机端口连接失败，由于docker默认网络模式为Bridge模式，其通过localhost访问不到宿主机。 - > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP + > 解决办法一：配置application.yml将数据库的连接地址由localhost修改为宿主机的对外IP > 解决办法二：使用Host网络模式启动Docker，即使Docker容器和宿主机共享网络 `docker run -d --network host .....` 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以 `docker logs hertzbeat` 查看容器日志是否有明显错误，提issue或交流群或社区反馈 3. 监控页面历史图表不显示，弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - + > 如弹窗所示，历史图表展示的前提是需要安装配置hertzbeat的依赖服务 - > 安装初始化此时序数据库 4. 安装配置了时序数据库，但页面依旧显示弹出 [无法提供历史图表数据，请配置依赖时序数据库] - > 请检查配置的时许数据库参数是否正确 - > 时序数据库对应的 enable 是否设置为true - > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP + > 请检查配置的时许数据库参数是否正确 + > 时序数据库对应的 enable 是否设置为true + > 注意⚠️若hertzbeat和外置数据库都为docker容器在同一主机下启动，容器之间默认不能用127.0.0.1通讯，改为主机IP > 可根据logs目录下启动日志排查 5. application.yml 是干什么用的 > 此文件是HertzBeat的配置文件，用于配置HertzBeat的各种参数，如数据库连接信息，时序数据库配置等。 - 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml + 下载 `application.yml` 文件到主机目录下，例如: $(pwd)/application.yml 下载源 [github/script/application.yml](https://github.com/apache/hertzbeat/raw/master/script/application.yml) - 若需使用邮件发送告警，需替换 `application.yml` 里面的邮件服务器参数 @@ -143,8 +143,8 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 > 此文件是HertzBeat的用户配置文件，用于配置HertzBeat的用户信息，如账户密码等。 - HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat - 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 - 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml - 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + HertzBeat默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + 若需要新增删除修改账户或密码，可以通过配置 `sureness.yml` 实现，若无此需求可忽略此步骤 + 下载 `sureness.yml` 文件到主机目录下，例如: $(pwd)/sureness.yml + 下载源 [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) 具体修改步骤参考 [配置修改账户密码](account-modify) diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/package-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/package-deploy.md index 8759ee12c6f..90cb3707a33 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/package-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/package-deploy.md @@ -1,6 +1,6 @@ --- -id: package-deploy -title: 通过安装包安装 HertzBeat +id: package-deploy +title: 通过安装包安装 HertzBeat sidebar_label: 安装包方式安装 --- @@ -40,7 +40,7 @@ Apache HertzBeat™ 支持在Linux Windows Mac系统安装运行，CPU支持X86/ 3. 配置账户文件(可选) - HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat + HertzBeat 默认内置三个用户账户,分别为 admin/hertzbeat tom/hertzbeat guest/hertzbeat 若需要新增删除修改账户或密码，可以通过修改位于 `config/sureness.yml` 的配置文件实现，具体参考 - [配置修改账户密码](account-modify) @@ -50,7 +50,7 @@ Apache HertzBeat™ 支持在Linux Windows Mac系统安装运行，CPU支持X86/ 执行位于安装目录 bin 下的启动脚本 startup.sh, windows 环境下为 startup.bat ```shell - ./startup.sh + ./startup.sh ``` 5. 开始探索HertzBeat @@ -63,7 +63,7 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 通过部署多个 HertzBeat Collector 可以实现数据的高可用，负载均衡和云边协同。 ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. 下载安装包 @@ -103,10 +103,10 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 执行位于安装目录 hertzbeat-collector/bin/ 下的启动脚本 startup.sh, windows 环境下为 startup.bat ```shell - ./startup.sh + ./startup.sh ``` -4. 开始探索 HertzBeat Collector +4. 开始探索 HertzBeat Collector 浏览器访问 [http://ip:1157/](http://ip:1157/) 即可开始探索使用，默认账户密码 admin/hertzbeat。 **HAVE FUN** @@ -119,9 +119,9 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 1. 启动失败，需您提前准备JAVA运行环境 - 安装JAVA运行环境-可参考[官方网站](https://www.oracle.com/java/technologies/downloads/) + 安装JAVA运行环境-可参考[官方网站](https://www.oracle.com/java/technologies/downloads/) 要求：JAVA17环境 - 下载JAVA安装包: [镜像站](https://mirrors.huaweicloud.com/openjdk/) + 下载JAVA安装包: [镜像站](https://mirrors.huaweicloud.com/openjdk/) 安装后命令行检查是否成功安装 ```shell @@ -134,6 +134,6 @@ HertzBeat Collector 是一个轻量级的数据采集器，用于采集并将数 2. 按照流程部署，访问 [http://ip:1157/](http://ip:1157/) 无界面 请参考下面几点排查问题： - > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 - > 二：HertzBeat的配置文件 `hertzbeat/config/application.yml` 里面的依赖服务IP账户密码等配置是否正确 + > 一：若切换了依赖服务MYSQL数据库，排查数据库是否成功创建，是否启动成功 + > 二：HertzBeat的配置文件 `hertzbeat/config/application.yml` 里面的依赖服务IP账户密码等配置是否正确 > 三：若都无问题可以查看 `hertzbeat/logs/` 目录下面的运行日志是否有明显错误，提issue或交流群或社区反馈 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/rainbond-deploy.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/rainbond-deploy.md index 4ed3002af86..adbfcac881f 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/rainbond-deploy.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: 使用 Rainbond 部署 HertzBeat +id: rainbond-deploy +title: 使用 Rainbond 部署 HertzBeat sidebar_label: 基于Rainbond部署 --- @@ -32,7 +32,7 @@ sidebar_label: 基于Rainbond部署 登录 Rainbond 后，点击左侧菜单中的 `应用市场`，切换到开源应用商店，在搜索框中搜索 `HertzBeat`，点击安装按钮。 -![HertzBeat](/img/docs/start/install-to-rainbond.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond.png) 填写以下信息，然后点击确认按钮进行安装。 @@ -43,7 +43,7 @@ sidebar_label: 基于Rainbond部署 等待安装完成，即可访问 HertzBeat 应用。 -![HertzBeat](/img/docs/start/hertzbeat-topology.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology.png) :::tip 通过 Rainbond 安装的 HertzBeat，默认使用了外部的 Mysql 数据库 和 Redis 以及 IoTDB。同时也挂载了 HertzBeat 的配置文件，可以在 `组件 -> 环境配置 -> 配置文件设置` 中修改配置文件。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/linux-os-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/linux-os-practice.md index 698a337ef52..18e907a3eb7 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/linux-os-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/linux-os-practice.md @@ -32,7 +32,7 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 操作系统监控 -> Linux 操作系统 -> 新增 Linux 操作系统监控 -![HertzBeat](/img/docs/start/linux-os-practice-1.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-1.png) ### 2. 配置参数 @@ -47,15 +47,15 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea 可以使用标签分类来管理任务，如添加`OS=Linux`等相关标签。 -![HertzBeat](/img/docs/start/linux-os-practice-2.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-2.png) ### 3. 查看监控数据 在监控列表可以查看任务状态，点击这个监控详情可以查看指标数据图表等。 -![HertzBeat](/img/docs/start/linux-os-practice-3.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-3.png) -![HertzBeat](/img/docs/start/linux-os-practice-4.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-4.png) ### 4. 设置阈值规则 @@ -65,23 +65,23 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > > 配置阈值，配置告警表达式-当指标`文件系统使用率`大于等于 `50%` 触发，也支持设置告警级别和通知模板信息等。 -![HertzBeat](/img/docs/start/linux-os-practice-5.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 最终可以在告警中心看到已触发的告警。 -![HertzBeat](/img/docs/start/linux-os-practice-6.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-6.png) ### 5. 消息通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 -![HertzBeat](/img/docs/start/linux-os-practice-7.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-7.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 -![HertzBeat](/img/docs/start/linux-os-practice-8.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-8.png) 当阈值触发后就可以收到对应告警消息，如果没有配置消息通知，也可以在**告警中心**查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/springboot-auto-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/springboot-auto-practice.md index a3f8163eba0..36400130890 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/springboot-auto-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/springboot-auto-practice.md @@ -1,7 +1,7 @@ --- -id: springboot-auto-practice -title: SpringBoot Web应用监控案例 -sidebar_label: SpringBoot Web应用监控案例 +id: springboot-auto-practice +title: SpringBoot Web应用监控案例 +sidebar_label: SpringBoot Web应用监控案例 --- :::tip @@ -141,7 +141,7 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > 系统页面 -> 监控中心 -> 新增监控 -> AUTO -> Prometheus任务 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-1.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-1.png) 2. 填写关键参数 @@ -153,16 +153,16 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-2.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-2.png) 3. 查看检测指标数据 > 点击进入新建监控，可以查看指标数据详情及指标历史图表等。 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-3.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-3.png) - ![HertzBeat](/img/docs/start/springboot-auto-practice-4.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-4.png) ## Grafana可视化集成 (可选) @@ -181,13 +181,13 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 比如：Grafana 数据源选择`hertzbeat-victoria-metrics`，然后在仪表盘点击:「Share」→「Export」→「Save to file」下载模板并上传至 HertzBeat 监控中。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-5.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-5.png) 3. 查看 Grafana 图表 > 进入新增 AUTO 监控页面，点击 Grafana 图标按钮，即可查看 Grafana 图表。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-6.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-6.png) ## 告警与通知联动 @@ -196,7 +196,7 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > 系统页面 -> 告警 -> 阈值规则 -> 新增 -> 新增阈值 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-7.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-7.png) > HertzBeat 提供了 **实时计算** 和 **计划周期** 两种类型的阈值规则设置，这里我们以 **计划周期** 阈值规则为例。 > @@ -213,24 +213,24 @@ Apache HertzBeat 一个拥有强大自定义监控能力，无需Agent的实时 > > 可以设置的阈值规则组合有很多，用户可以根据自身需要设置更丰富的告警规则。 - ![HertzBeat](/img/docs/start/springboot-auto-practice-8.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-8.png) > 最后可以在 告警中心 看到已触发的告警。 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-9.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-9.png) 3. 告警通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-10.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-10.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 > - ![HertzBeat](/img/docs/start/springboot-auto-practice-11.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-11.png) 4. OK！当阈值规则触发后我们就可以收到对应告警消息啦，如果没有配置通知，也可以在告警中心查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/sslcert-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/sslcert-practice.md index c81d0b92402..91aaf8b6327 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/sslcert-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL 证书过期监控案例 +id: ssl-cert-practice +title: SSL 证书过期监控案例 sidebar_label: SSL 证书过期监控案例 --- @@ -34,28 +34,28 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 系统页面 -> 监控中心 -> 新增监控 -> 应用服务监控 -> SSL 证书 -> 新增 SSL 证书 - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. 配置监控网站 > 我们这里举例监控百度网站, 配置监控host域名，名称，采集间隔等。 - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. 设置阈值(证书过期时触发) - > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 + > 系统页面 -> 告警 -> 告警阈值 -> 新增阈值 -> 新增实时阈值规则 > 配置阈值，选择SSL证书指标对象，配置告警表达式-当指标`expired`为`true`触发，即`equals(expired,"true")` , 设置告警级别通知模板信息等。 - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > 阈值规则还有其它功能可以配置, 比如阈值关联指定监控, 触发次数, 关联标签等等。 @@ -63,17 +63,17 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 同理如上，选择代码阈值规则，新增配置阈值，配置告警表达式-当指标有效期时间戳 `end_timestamp`，`now()`函数为当前时间戳，若配置提前一周触发告警即：`end_timestamp <= (now() + 604800000)` , 其中 `604800000` 为7天总时间差毫秒值。 - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > 最终可以在告警中心看到已触发的告警。 - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. 告警通知(通过钉钉微信飞书等及时通知) > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) 钉钉微信飞书等 token 配置可以参考帮助文档 @@ -81,11 +81,11 @@ github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbea > 消息通知 -> 通知策略 -> 新增告警通知策略 -> 将刚才配置的接收人启用通知 - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK 当阈值触发后我们就可以收到对应告警消息啦，如果没有配通知，也可以在告警中心查看告警信息。 ----- +---- ## 结束搞定 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/tdengine-practice.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/tdengine-practice.md index 6228026c503..2c83ad46560 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/tdengine-practice.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/start/usecase/tdengine-practice.md @@ -1,6 +1,6 @@ --- -id: tdengine-practice -title: TDengine 监控案例 +id: tdengine-practice +title: TDengine 监控案例 sidebar_label: TDengine 监控案例 --- @@ -40,7 +40,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 监控中心 -> 新增监控 -> 自定义监控 -> TDengine-PromQL任务 - ![HertzBeat](/img/docs/start/tdengine_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1.png) 2. 填写关键参数 @@ -52,15 +52,15 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/tdengine_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/tdengine_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_3.png) - ![HertzBeat](/img/docs/start/tdengine_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_4.png) ## 监控 TDengine(Prometheus) @@ -68,7 +68,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 监控中心 -> 新增监控 -> AUTO -> Prometheus任务 - ![HertzBeat](/img/docs/start/tdengine_1_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_1.png) 2. 填写关键参数 @@ -80,15 +80,15 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以使用标签分类来管理任务，如添加`env=test`等业务相关标签。 - ![HertzBeat](/img/docs/start/tdengine_1_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_2.png) 3. 查看检测指标数据 > 在监控列表可以查看任务状态，进监控详情可以查看指标数据图表等。 - ![HertzBeat](/img/docs/start/tdengine_1_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_3.png) - ![HertzBeat](/img/docs/start/tdengine_1_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_4.png) ### Grafana可视化集成 (可选) @@ -107,13 +107,13 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 比如：Grafana 数据源选择`hertzbeat-victoria-metrics`，然后在仪表盘点击:「Share」→「Export」→「Save to file」下载模板并上传至 HertzBeat 监控中，可参考：[taoskeeper-prometheus-dashboard](https://grafana.com/grafana/dashboards/15164-taoskeeper-prometheus-dashboard/) - ![HertzBeat](/img/docs/start/tdengine_1_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_5.png) 3. 查看 Grafana 图表 > 进入新增 AUTO 监控页面，点击 Grafana 图标按钮，即可查看 Grafana 图表。 - ![HertzBeat](/img/docs/start/tdengine_1_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_6.png) ## 告警与通知联动 @@ -122,7 +122,7 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > 系统页面 -> 告警 -> 阈值规则 -> 新增 -> 新增阈值 > - ![HertzBeat](/img/docs/start/tdengine_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_5.png) > HertzBeat 提供了 **实时计算** 和 **计划周期** 两种类型的阈值规则设置，这里我们以 **计划周期** 阈值规则为例。 > @@ -139,24 +139,24 @@ TDengine TSDB 集成了多种监控指标收集机制，并通过 taosKeeper 进 > > 可以设置的阈值规则组合有很多，用户可以根据自身需要设置更丰富的告警规则。 - ![HertzBeat](/img/docs/start/tdengine_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_6.png) > 最后可以在 告警中心 看到已触发的告警。 > - ![HertzBeat](/img/docs/start/tdengine_7.png) + ![HertzBeat](home/static/img/docs/start/tdengine_7.png) 3. 告警通知 > 系统页面 -> 消息通知 -> 通知媒介 -> 新增接收对象 > - ![HertzBeat](/img/docs/start/tdengine_8.png) + ![HertzBeat](home/static/img/docs/start/tdengine_8.png) > 系统页面 -> 消息通知 -> 通知策略 -> 新增通知策略 -> 选择接收对象并启用通知 > - ![HertzBeat](/img/docs/start/tdengine_9.png) + ![HertzBeat](home/static/img/docs/start/tdengine_9.png) 4. OK！当阈值规则触发后我们就可以收到对应告警消息啦，如果没有配置通知，也可以在告警中心查看告警信息。 diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/template.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/template.md index 5ee81d6b8bf..3951cbb4f2b 100644 --- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/template.md +++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.8.0/template.md @@ -1,6 +1,6 @@ --- -id: template -title: 监控模板中心 +id: template +title: 监控模板中心 sidebar_label: 监控模板 --- @@ -11,11 +11,11 @@ sidebar_label: 监控模板 这是它的架构原理: -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **我们将所有监控采集类型(mysql,website,jvm,k8s)都定义为yml模板，用户可以导入这些模板到hertzbeat系统中，使其支持对应类型的监控，非常方便！** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **欢迎大家一起贡献你使用过程中自定义的通用监控类型YML模板，可用的模板如下:** diff --git a/home/sidebars.json b/home/sidebars.json index fd24405bbeb..8cf502b1f29 100755 --- a/home/sidebars.json +++ b/home/sidebars.json @@ -178,6 +178,7 @@ "label": "database", "items": [ "help/mysql", + "help/mysql_account_expiry", "help/mariadb", "help/postgresql", "help/greenplum", @@ -320,6 +321,8 @@ "help/time_expression", "help/grafana_dashboard", "help/collector", + "help/registry", + "help/template_marketplace", "help/risc-v", "help/issue" ] diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md b/home/versioned_docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md index 482712129b2..205f6c36eb8 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-http-example-hertzbeat.md @@ -191,19 +191,19 @@ metrics: **The addition is complete, now we save and apply. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-http-example-token.md b/home/versioned_docs/version-1.6.x/advanced/extend-http-example-token.md index 35a0c8cef65..c08ef5c8aa7 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-http-example-token.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-http-example-token.md @@ -229,13 +229,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **After the addition is successful, we can see the `token`, `refreshToken` metric data we collected on the details page.** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### Use `token` as a variable parameter to collect and use the following metricss @@ -389,9 +389,9 @@ metrics: **After the configuration is complete, save and apply, and check the monitoring details page** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-jmx.md b/home/versioned_docs/version-1.6.x/advanced/extend-jmx.md index 29f1bc3ff44..eaf1a16d151 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-jmx.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-jmx.md @@ -21,7 +21,7 @@ By configuring the monitoring template YML metrics `field`, `aliasFields`, `obje **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-push.md b/home/versioned_docs/version-1.6.x/advanced/extend-push.md index 1762fc7b751..e950a964608 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-push.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat DashBoard -> Service Monitor -> Push Style Monitor -> New Push Style M ### Monitor Configuration Example -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-snmp.md b/home/versioned_docs/version-1.6.x/advanced/extend-snmp.md index ce39f61ec80..345d46b97c3 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-snmp.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-snmp.md @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields`, and `oids` under the `snmp` p **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-telnet.md b/home/versioned_docs/version-1.6.x/advanced/extend-telnet.md index c4a65f885db..c3710905b58 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-telnet.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-telnet.md @@ -1,5 +1,5 @@ --- -id: extend-telnet +id: extend-telnet title: Telnet Protocol Custom Monitoring sidebar_label: Telnet Protocol Custom Monitoring --- @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields` the `Telnet` protocol of the m **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/versioned_docs/version-1.6.x/advanced/extend-tutorial.md b/home/versioned_docs/version-1.6.x/advanced/extend-tutorial.md index 6c774d84216..a254793ae3b 100644 --- a/home/versioned_docs/version-1.6.x/advanced/extend-tutorial.md +++ b/home/versioned_docs/version-1.6.x/advanced/extend-tutorial.md @@ -203,19 +203,19 @@ metrics: **The addition is complete, now we restart the hertzbeat system. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.6.x/community/contribution.md b/home/versioned_docs/version-1.6.x/community/contribution.md index a189c4192d7..7c3b364fb59 100644 --- a/home/versioned_docs/version-1.6.x/community/contribution.md +++ b/home/versioned_docs/version-1.6.x/community/contribution.md @@ -85,27 +85,27 @@ Of course, if you have a good idea, you can also propose it directly on GitHub D 2. Then download the code locally with git command: ```shell - git clone git@github.com:`YOUR_USERNAME`/hertzbeat.git #Recommended + git clone git@github.com:`YOUR_USERNAME`/hertzbeat.git #Recommended ``` 3. After the download is complete, please refer to the getting started guide or README file of the target repository to initialize the project. 4. Then, you can refer to the following command to submit the code: ```shell - git checkout -b a-feature-branch #Recommended + git checkout -b a-feature-branch #Recommended ``` 5. Submit the coed as a commit, the commit message format specification required: [module name or type name]feature or bugfix or doc: custom message. ```shell - git add - git commit -m '[docs]feature: necessary instructions' #Recommended + git add + git commit -m '[docs]feature: necessary instructions' #Recommended ``` 6. Push to the remote repository ```shell - git push origin a-feature-branch + git push origin a-feature-branch ``` 7. Then you can initiate a new PR (Pull Request) on GitHub. @@ -135,7 +135,7 @@ On the master/main branch, you can do the following to sync the upstream reposit ```shell git remote add upstream https://github.com/apache/hertzbeat.git #Bind the remote warehouse, if it has been executed, it does not need to be executed again -git checkout master +git checkout master git pull upstream master ``` @@ -168,4 +168,4 @@ Add WeChat account `ahertzbeat` to pull you into the WeChat group. > - **[web-app](https://github.com/apache/hertzbeat/tree/master/web-app)** Provide web ui. > Angular Web UI. -![hertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) diff --git a/home/versioned_docs/version-1.6.x/help/alert_threshold.md b/home/versioned_docs/version-1.6.x/help/alert_threshold.md index 0491f66ccb9..b7670e85a12 100644 --- a/home/versioned_docs/version-1.6.x/help/alert_threshold.md +++ b/home/versioned_docs/version-1.6.x/help/alert_threshold.md @@ -5,8 +5,8 @@ sidebar_label: Alarm Threshold --- :::tip -Alarm Threshold are the core function of `HertzBeat`, users can configure the trigger conditions of the alarm through the threshold rules. -Support real-time threshold and scheduled threshold, real-time threshold can directly trigger the alarm when monitoring data is collected, scheduled threshold supports PromQL and other expressions to calculate the trigger alarm within a specified time period. +Alarm Threshold are the core function of `HertzBeat`, users can configure the trigger conditions of the alarm through the threshold rules. +Support real-time threshold and scheduled threshold, real-time threshold can directly trigger the alarm when monitoring data is collected, scheduled threshold supports PromQL and other expressions to calculate the trigger alarm within a specified time period. Support visual page configuration or more flexible expression rule configuration, support configuring trigger times, alarm levels, notification templates, associated specified monitoring and so on. ::: @@ -22,7 +22,7 @@ Support visual page configuration or more flexible expression rule configuration Configure the threshold, for example: Select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) Configuration item details: diff --git a/home/versioned_docs/version-1.6.x/help/redis_cluster.md b/home/versioned_docs/version-1.6.x/help/redis_cluster.md index e548d0eb91d..d030162e9da 100644 --- a/home/versioned_docs/version-1.6.x/help/redis_cluster.md +++ b/home/versioned_docs/version-1.6.x/help/redis_cluster.md @@ -98,7 +98,7 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to Add a redis monitor center, fill require parameters. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) final effect. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/versioned_docs/version-1.6.x/help/status.md b/home/versioned_docs/version-1.6.x/help/status.md index 934ad0c7b78..fe30c7badaf 100644 --- a/home/versioned_docs/version-1.6.x/help/status.md +++ b/home/versioned_docs/version-1.6.x/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: Status Page -sidebar_label: Status Page +id: status +title: Status Page +sidebar_label: Status Page keywords: [Open Source Monitoring System, Open Source Website Monitoring, Status Page] --- @@ -24,7 +24,7 @@ The fields that need to be filled in are as follows: After filling in the organization information, click `Confirm`. -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. Add Component @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. Maintain Events @@ -59,7 +59,7 @@ When an event occurs, you can publish a notification on the status page. Click `Publish Event` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | Field Name | Field Description | Example | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -70,4 +70,4 @@ Click `Publish Event` > Note: You can publish messages multiple times to keep the team updated on the current status. -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/versioned_docs/version-1.6.x/introduce.md b/home/versioned_docs/version-1.6.x/introduce.md index c8ebe7a21c3..aaf789f61ff 100644 --- a/home/versioned_docs/version-1.6.x/introduce.md +++ b/home/versioned_docs/version-1.6.x/introduce.md @@ -40,11 +40,11 @@ slug: / HertzBeat itself did not create a data collection protocol for the monitoring client to adapt to. Instead, HertzBeat makes full use of the existing ecosystem, `SNMP protocol` to collect information from network switches and routers, `JMX specification` to collect information from Java applications, `JDBC specification` to collect information from datasets, `SSH` to directly connect to scripts to get the display information, `HTTP+ (JsonPath | prometheus, etc.)` to parse the information from API interfaces, `IPMI protocol` to collect server information, and so on. HertzBeat uses these existing standard protocols or specifications, makes them abstractly configurable, and finally makes them all available in the form of YML format monitoring templates that can be written to create templates that use these protocols to collect any desired metrics data. -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) Do you believe that users can just write a monitoring template on the UI page, click save and immediately adapt a new monitoring type like `K8s` or `Docker`? -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Built-in Monitoring Types @@ -95,7 +95,7 @@ Do you believe that users can just write a monitoring template on the UI page, c > Each monitor type is considered as a monitor template, no matter it is built-in or user-defined. You can easily add, modify and delete indicators by modifying the monitoring template. > The templates contain a series of functions such as protocol configuration, environment variables, metrics conversion, metrics calculation, units conversion, metrics collection, etc., which help users to collect the metrics they want. -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### No Agent Required @@ -118,7 +118,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t * Monitoring tasks are self-scheduled in the collector cluster, single collector hangs without sensing the failure to migrate the collection tasks, and the newly added collector nodes are automatically scheduled to share the collection pressure. * It is very easy to switch between stand-alone mode and cluster mode without additional component deployment. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Cloud Edge Collaboration @@ -127,7 +127,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t In an isolated network where multiple networks are not connected, we need to deploy a monitoring system in each network in the previous solution, which leads to data non-interoperability and inconvenient management, deployment and maintenance. `HertzBeat` provides the ability of cloud edge collaboration, can be deployed in multiple isolated networks edge collector, collector in the isolated network within the monitoring task collection, collection of data reported by the main service unified scheduling management display. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Easy to Use @@ -163,7 +163,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat * HertzBeat's user management is unified by the configuration file `sureness.yml`, which allows users to add, delete, and modify user information, user role permissions, and so on. Default password admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### Overview Page @@ -171,7 +171,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat * Show the status of currently registered collector clusters, including collector on-line status, monitoring tasks, startup time, IP address, name and so on. * Show the list of recent alarm messages, alarm level distribution and alarm processing rate. -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### Monitoring Center @@ -218,7 +218,7 @@ Built-in support for monitoring types include: [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### Add and Modify Surveillance @@ -226,7 +226,7 @@ Built-in support for monitoring types include: * The monitoring parameters configured on the page are defined by the monitoring template of the corresponding monitoring type, and users can modify the configuration parameters on the page by modifying the monitoring template. * Support associated tags to manage monitoring grouping, alarm matching, and so on. -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### Monitor Details @@ -235,16 +235,16 @@ Built-in support for monitoring types include: * Monitor Historical Data Report displays the historical values of the currently monitored metrics in the form of trend charts, supports querying hourly, daily and monthly historical data, and supports configuring the page refresh time. * ⚠️ Note that the monitoring history charts need to be configured with an external timing database in order to get the full functionality, timing database support: IOTDB, TDengine, InfluxDB, GreptimeDB -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### Alarm Center * The management display page of triggered alarm messages enables users to visualize the current alarm situation. * Support alarm processing, alarm marking unprocessed, alarm deletion, clearing and other batch operations. -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### Threshold Rules @@ -253,18 +253,18 @@ Built-in support for monitoring types include: * Threshold rules support visual page configuration or expression rule configuration for more flexibility. * It supports configuring the number of triggers, alarm levels, notification templates, associated with a specific monitor and so on. -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### Alarm Convergence * When the alarm is triggered by the threshold rule, it will enter into the alarm convergence, the alarm convergence will be based on the rules of the specific time period of the duplicate alarm message de-emphasis convergence, to avoid a large number of repetitive alarms lead to the receiver alarm numbness. * Alarm convergence rules support duplicate alarm effective time period, label matching and alarm level matching filter. -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### Alarm Silence @@ -272,9 +272,9 @@ Built-in support for monitoring types include: * This application scenario, such as users in the system maintenance, do not need to send known alarms. Users will only receive alarm messages on weekdays, and users need to avoid disturbances at night. * Alarm silence rules support one-time time period or periodic time period, support label matching and alarm level matching. -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### Message Notification @@ -284,18 +284,18 @@ Built-in support for monitoring types include: * The notification policy supports tag matching and alert level matching, which makes it convenient to assign alerts with different tags and alert levels to different receivers and handlers. * Support notification templates, users can customize the content format of the templates to meet their own personalized notification display needs. -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) ### Monitoring Templates * HertzBeat makes `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` and other protocols configurable so that you can customize the metrics you want to collect using these protocols by simply configuring the monitoring template `YML` in your browser. Would you believe that you can instantly adapt a new monitoring type such as `K8s` or `Docker` just by configuring it? * All our built-in monitoring types (mysql, website, jvm, k8s) are also mapped to corresponding monitoring templates, so you can add and modify monitoring templates to customize your monitoring functions. -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) --- diff --git a/home/versioned_docs/version-1.6.x/start/baota-deploy.md b/home/versioned_docs/version-1.6.x/start/baota-deploy.md index 46ff957e801..66023a1affc 100644 --- a/home/versioned_docs/version-1.6.x/start/baota-deploy.md +++ b/home/versioned_docs/version-1.6.x/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: Use aaPanel Deploy HertzBeat +id: baota-deploy +title: Use aaPanel Deploy HertzBeat sidebar_label: Install via aaPanel --- @@ -12,19 +12,19 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i ## Install -1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. +1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. - > Install the Docker service, skip if it already exists. + > Install the Docker service, skip if it already exists. - ![HertzBeat](/img/docs/start/install-to-aapanel-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-1.png) 2. Find `HertzBeat` in `One-Click Install` and click `Install` - ![HertzBeat](/img/docs/start/install-to-aapanel-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-2.png) 3. Config the domain, name and others, click `OK` - ![HertzBeat](/img/docs/start/install-to-aapanel-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-3.png) - Name: App name, default the `HertzBeat-random` - Version：Default `latest` - Domain：Config if you need domain access, please configure the domain name here and resolve the domain name to the server @@ -38,6 +38,6 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i - If you have set a domain name, please enter the domain name directly in the browser address bar to access, such as `http://demo.hertzbeat.apache.org`, you can access the `HertzBeat` console. - If you choose to access via `IP+Port`, please enter the domain name in the browser address bar to access `http://`\`:1157`, you can access the `HertzBeat` console. -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > Default account username: `admin` password: `hertzbeat` diff --git a/home/versioned_docs/version-1.6.x/start/docker-deploy.md b/home/versioned_docs/version-1.6.x/start/docker-deploy.md index 75638876732..570efdb9e9b 100644 --- a/home/versioned_docs/version-1.6.x/start/docker-deploy.md +++ b/home/versioned_docs/version-1.6.x/start/docker-deploy.md @@ -1,6 +1,6 @@ --- -id: docker-deploy -title: Install HertzBeat via Docker +id: docker-deploy +title: Install HertzBeat via Docker sidebar_label: Install via Docker --- @@ -51,7 +51,7 @@ It is necessary to have Docker environment in your environment. If not installed ::: -2. Start to explore HertzBeat +2. Start to explore HertzBeat Access [http://ip:1157/](http://ip:1157/) using browser. You can explore HertzBeat with default account `admin/hertzbeat` now! ### Deploy HertzBeat Collector Cluster(Optional) @@ -61,7 +61,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat By deploying multiple HertzBeat Collectors, high availability, load balancing, and cloud-edge collaboration of data can be achieved. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Execute the following command @@ -109,31 +109,31 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 1. MYSQL, TDENGINE, IoTDB and HertzBeat are deployed on the same host by Docker,HertzBeat use localhost or 127.0.0.1 connect to the database but fail The problems lies in Docker container failed to visit and connect localhost port. Because the docker default network mode is Bridge mode which can't access local machine through localhost. - > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. + > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. > Solution B：Use the Host network mode to start Docker, namely making Docker container and hosting share network. `docker run -d --network host .....` 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues： - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. - > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. + > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. 3. Historical monitoring charts have been missing data for a long time - > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. + > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. > 2: Check whether IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. 4. If the history chart on the monitoring page is not displayed，popup [please configure time series database] - > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. + > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. > Installation and initialization this database, please refer to [Using victoria-metrics to store metrics data](victoria-metrics-init) 5. The time series database is installed and configured, but the page still displays a pop-up [Unable to provide historical chart data, please configure dependent time series database] - > Please check if the configuration parameters are correct - > Is time-series database enable set to true - > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed + > Please check if the configuration parameters are correct + > Is time-series database enable set to true + > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed > You can check the startup logs according to the logs directory 6. What is the purpose of application.yml @@ -149,9 +149,9 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 7. What is the purpose of sureness.yml - > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. - > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` - > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. - > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` - > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. + > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` + > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. + > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` + > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) > For detail steps, please refer to [Configure Account Password](account-modify) diff --git a/home/versioned_docs/version-1.6.x/start/package-deploy.md b/home/versioned_docs/version-1.6.x/start/package-deploy.md index 9f74edffc25..d39106d099d 100644 --- a/home/versioned_docs/version-1.6.x/start/package-deploy.md +++ b/home/versioned_docs/version-1.6.x/start/package-deploy.md @@ -1,6 +1,6 @@ --- -id: package-deploy -title: Install HertzBeat via Package +id: package-deploy +title: Install HertzBeat via Package sidebar_label: Install via Package --- @@ -50,7 +50,7 @@ Since version 1.6.0 uses `Java 17` and the installation package no longer provid Execute the startup script in the installation directory `bin/`, or `startup.bat` in windows. ```shell - ./startup.sh + ./startup.sh ``` 5. Begin to explore HertzBeat @@ -64,7 +64,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat Deploying multiple HertzBeat Collectors can achieve high availability, load balancing, and cloud-edge collaboration of data. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Download installation package @@ -132,6 +132,6 @@ Deploying multiple HertzBeat Collectors can achieve high availability, load bala 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues: - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `hertzbeat/config/application.yml`. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `hertzbeat/config/application.yml`. > 3：Check whether the running log has errors in `hertzbeat/logs/` directory. If you haven't solved the issue, report it to the communication group or community. diff --git a/home/versioned_docs/version-1.6.x/start/rainbond-deploy.md b/home/versioned_docs/version-1.6.x/start/rainbond-deploy.md index 2a1cf1de3d8..273502bce5b 100644 --- a/home/versioned_docs/version-1.6.x/start/rainbond-deploy.md +++ b/home/versioned_docs/version-1.6.x/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: Use Rainbond Deploy HertzBeat +id: rainbond-deploy +title: Use Rainbond Deploy HertzBeat sidebar_label: Install via Rainbond --- @@ -32,7 +32,7 @@ To install Rainbond, please refer to [Rainbond Quick Install](https://www.rainbo After logging in Rainbond, click Market in the left menu, switch to open source app store, and search HertzBeat in the search box, and click the Install button. -![HertzBeat](/img/docs/start/install-to-rainbond-en.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond-en.png) Fill in the following information, and click Confirm button to install. @@ -43,7 +43,7 @@ Fill in the following information, and click Confirm button to install. After installation, HertzBeat can be accessed via the Access button. -![HertzBeat](/img/docs/start/hertzbeat-topology-en.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology-en.png) :::tip HertzBeat installed via Rainbond, External Mysql database and Redis and IoTDB are used by default, The HertzBeat configuration file is also mounted, which can be modified in `Components -> Environment Configuration -> Configuration File Settings`. diff --git a/home/versioned_docs/version-1.6.x/start/sslcert-practice.md b/home/versioned_docs/version-1.6.x/start/sslcert-practice.md index 7edeb2b7bbb..fffd116fcd5 100644 --- a/home/versioned_docs/version-1.6.x/start/sslcert-practice.md +++ b/home/versioned_docs/version-1.6.x/start/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL Certificate Monitoring Practice +id: ssl-cert-practice +title: SSL Certificate Monitoring Practice sidebar_label: SSL Certificate Monitoring Practice --- @@ -32,29 +32,29 @@ The production environment recommends a complete deployment method, refer [https > HertzBeat Page -> Monitors -> New Monitor -> Service Monitor -> Add SSL Certificate - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. Configure the monitoring website > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. > Click OK Note - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. View the detection index data > In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. Set the threshold (triggered when the certificate expires) - > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule + > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule > Configure the threshold, select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > Threshold rule has others function you can try eg: associating thresholds with monitoring, trigger times so on. @@ -62,17 +62,17 @@ The production environment recommends a complete deployment method, refer [https > In the same way, switch coding threshold, add a new configuration threshold and configure an alarm expression - when the metric expires timestamp `end_timestamp`, the `now()` function is the current timestamp, if the configuration triggers an alarm one week in advance: `end_timestamp <= (now() + 604800000)` , where `604800000` is the 7-day total time difference in milliseconds. - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. Alarm notification (in time notification via Dingding WeChat Feishu, etc.) > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Config the Feishu Receiver - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) For token configuration such as Feishu, please refer to the help document @@ -80,7 +80,7 @@ The production environment recommends a complete deployment method, refer [https > Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. diff --git a/home/versioned_docs/version-1.6.x/template.md b/home/versioned_docs/version-1.6.x/template.md index b88ebcd9325..80ea874935a 100644 --- a/home/versioned_docs/version-1.6.x/template.md +++ b/home/versioned_docs/version-1.6.x/template.md @@ -1,6 +1,6 @@ --- -id: template -title: Monitoring Template Here +id: template +title: Monitoring Template Here sidebar_label: Monitoring Template --- @@ -11,11 +11,11 @@ sidebar_label: Monitoring Template Here is the architecture. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **We define all monitoring collection types (mysql, website, jvm, k8s) as yml templates, and users can import these templates into the hertzbeat system to support corresponding types of monitoring, which is very convenient!** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **Welcome everyone to contribute your customized general monitoring type YML template during use. The available templates are as follows:** diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md b/home/versioned_docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md index 482712129b2..205f6c36eb8 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-http-example-hertzbeat.md @@ -191,19 +191,19 @@ metrics: **The addition is complete, now we save and apply. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-http-example-token.md b/home/versioned_docs/version-1.7.x/advanced/extend-http-example-token.md index 35a0c8cef65..c08ef5c8aa7 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-http-example-token.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-http-example-token.md @@ -229,13 +229,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **After the addition is successful, we can see the `token`, `refreshToken` metric data we collected on the details page.** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### Use `token` as a variable parameter to collect and use the following metricss @@ -389,9 +389,9 @@ metrics: **After the configuration is complete, save and apply, and check the monitoring details page** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-jmx.md b/home/versioned_docs/version-1.7.x/advanced/extend-jmx.md index 29f1bc3ff44..eaf1a16d151 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-jmx.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-jmx.md @@ -21,7 +21,7 @@ By configuring the monitoring template YML metrics `field`, `aliasFields`, `obje **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-push.md b/home/versioned_docs/version-1.7.x/advanced/extend-push.md index 1762fc7b751..e950a964608 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-push.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat DashBoard -> Service Monitor -> Push Style Monitor -> New Push Style M ### Monitor Configuration Example -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-snmp.md b/home/versioned_docs/version-1.7.x/advanced/extend-snmp.md index ce39f61ec80..345d46b97c3 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-snmp.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-snmp.md @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields`, and `oids` under the `snmp` p **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-telnet.md b/home/versioned_docs/version-1.7.x/advanced/extend-telnet.md index c4a65f885db..c3710905b58 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-telnet.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-telnet.md @@ -1,5 +1,5 @@ --- -id: extend-telnet +id: extend-telnet title: Telnet Protocol Custom Monitoring sidebar_label: Telnet Protocol Custom Monitoring --- @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields` the `Telnet` protocol of the m **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/versioned_docs/version-1.7.x/advanced/extend-tutorial.md b/home/versioned_docs/version-1.7.x/advanced/extend-tutorial.md index 6c774d84216..a254793ae3b 100644 --- a/home/versioned_docs/version-1.7.x/advanced/extend-tutorial.md +++ b/home/versioned_docs/version-1.7.x/advanced/extend-tutorial.md @@ -203,19 +203,19 @@ metrics: **The addition is complete, now we restart the hertzbeat system. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.7.x/help/alert_threshold.md b/home/versioned_docs/version-1.7.x/help/alert_threshold.md index be8e90bc5f7..1d569645873 100644 --- a/home/versioned_docs/version-1.7.x/help/alert_threshold.md +++ b/home/versioned_docs/version-1.7.x/help/alert_threshold.md @@ -26,7 +26,7 @@ Support visual page configuration or more flexible expression rule configuration Configure the threshold, for example: Select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) Configuration item details: diff --git a/home/versioned_docs/version-1.7.x/help/redis_cluster.md b/home/versioned_docs/version-1.7.x/help/redis_cluster.md index e548d0eb91d..d030162e9da 100644 --- a/home/versioned_docs/version-1.7.x/help/redis_cluster.md +++ b/home/versioned_docs/version-1.7.x/help/redis_cluster.md @@ -98,7 +98,7 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to Add a redis monitor center, fill require parameters. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) final effect. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/versioned_docs/version-1.7.x/help/status.md b/home/versioned_docs/version-1.7.x/help/status.md index daf362a0f5c..fc8c7b91fc2 100644 --- a/home/versioned_docs/version-1.7.x/help/status.md +++ b/home/versioned_docs/version-1.7.x/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: Status Page -sidebar_label: Status Page +id: status +title: Status Page +sidebar_label: Status Page keywords: [Open Source Monitoring System, Open Source Website Monitoring, Status Page] --- @@ -24,7 +24,7 @@ The fields that need to be filled in are as follows: After filling in the organization information, click `Confirm`. -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. Add Component @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. Maintain Events @@ -59,7 +59,7 @@ When an event occurs, you can publish a notification on the status page. Click `Publish Event` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | Field Name | Field Description | Example | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -70,4 +70,4 @@ Click `Publish Event` > Note: You can publish messages multiple times to keep the team updated on the current status. -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/versioned_docs/version-1.7.x/introduce.md b/home/versioned_docs/version-1.7.x/introduce.md index fdba2db0c45..8067b2796fe 100644 --- a/home/versioned_docs/version-1.7.x/introduce.md +++ b/home/versioned_docs/version-1.7.x/introduce.md @@ -32,11 +32,11 @@ slug: / HertzBeat itself did not create a data collection protocol for the monitoring client to adapt to. Instead, HertzBeat makes full use of the existing ecosystem, `SNMP protocol` to collect information from network switches and routers, `JMX specification` to collect information from Java applications, `JDBC specification` to collect information from datasets, `SSH` to directly connect to scripts to get the display information, `HTTP+ (JsonPath | prometheus, etc.)` to parse the information from API interfaces, `IPMI protocol` to collect server information, and so on. HertzBeat uses these existing standard protocols or specifications, makes them abstractly configurable, and finally makes them all available in the form of YML format monitoring templates that can be written to create templates that use these protocols to collect any desired metrics data. -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) Do you believe that users can just write a monitoring template on the UI page, click save and immediately adapt a new monitoring type like `K8s` or `Docker`? -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Built-in Monitoring Types @@ -87,7 +87,7 @@ Do you believe that users can just write a monitoring template on the UI page, c > Each monitor type is considered as a monitor template, no matter it is built-in or user-defined. You can easily add, modify and delete indicators by modifying the monitoring template. > The templates contain a series of functions such as protocol configuration, environment variables, metrics conversion, metrics calculation, units conversion, metrics collection, etc., which help users to collect the metrics they want. -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### No Agent Required @@ -110,7 +110,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t - Monitoring tasks are self-scheduled in the collector cluster, single collector hangs without sensing the failure to migrate the collection tasks, and the newly added collector nodes are automatically scheduled to share the collection pressure. - It is very easy to switch between stand-alone mode and cluster mode without additional component deployment. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Cloud Edge Collaboration @@ -119,7 +119,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t In an isolated network where multiple networks are not connected, we need to deploy a monitoring system in each network in the previous solution, which leads to data non-interoperability and inconvenient management, deployment and maintenance. `HertzBeat` provides the ability of cloud edge collaboration, can be deployed in multiple isolated networks edge collector, collector in the isolated network within the monitoring task collection, collection of data reported by the main service unified scheduling management display. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Easy to Use @@ -155,7 +155,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat - HertzBeat's user management is unified by the configuration file `sureness.yml`, which allows users to add, delete, and modify user information, user role permissions, and so on. Default password admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### Overview Page @@ -163,7 +163,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat - Show the status of currently registered collector clusters, including collector on-line status, monitoring tasks, startup time, IP address, name and so on. - Show the list of recent alarm messages, alarm level distribution etc. -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### Monitoring Center @@ -210,7 +210,7 @@ Built-in support for monitoring types include: [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### New Monitor @@ -218,7 +218,7 @@ Built-in support for monitoring types include: - The monitoring parameters configured on the page are defined by the monitoring template of the corresponding monitoring type, and users can modify the configuration parameters on the page by modifying the monitoring template. - Support associated tags to manage monitoring grouping, alarm matching, and so on. -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### Monitor Details @@ -227,16 +227,16 @@ Built-in support for monitoring types include: - Monitor Historical Data Report displays the historical values of the currently monitored metrics in the form of trend charts, supports querying hourly, daily and monthly historical data, and supports configuring the page refresh time. - ⚠️ Note that the monitoring history charts need to be configured with an external timing database in order to get the full functionality. -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### Alarm Center - The management display page of triggered alarm messages enables users to visualize the current alarm situation. - Support alarm processing, alarm marking unprocessed, alarm deletion, clearing and other batch operations. -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### Alarm Threshold @@ -244,29 +244,29 @@ Built-in support for monitoring types include: - Support real-time threshold and scheduled threshold, real-time threshold can directly trigger the alarm when monitoring data is collected, scheduled threshold supports PromQL and other expressions to calculate the trigger alarm within a specified time period. - Support visual page configuration or more flexible expression rule configuration, support configuring trigger times, alarm levels, notification templates, associated specified monitoring and so on. -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### Alarm Integration - Integration with third-party monitoring systems such as `Prometheus`, `WebHook`, `Skywalking`, `AlertManager`, etc. to receive alarm messages from these systems and perform alarm processing. -![HertzBeat](/img/home/11.png) +![HertzBeat](home/static/img/home/11.png) ### Alarm Grouping - Group convergence supports merging alarms for specified group labels by grouping. It deduplicates and converges the same repeated alarms in a time period. - When the threshold rule triggers an alarm or an external alarm is reported, it will enter the grouping convergence for alarm grouping and alarm deduplication to avoid alarm storms caused by a large number of alarm messages. -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) ### Alarm Inhibition - Alarm suppression is used to configure the suppression relationship between alarms. For example, high-level alarms suppress low-level alarms under the same instance. - When an alarm occurs, it can suppress the occurrence of other alarms. For example, when a server crashes, it can suppress all alarms on that server. -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### Alarm Silence @@ -274,7 +274,7 @@ Built-in support for monitoring types include: - This application scenario, such as users in the system maintenance, do not need to send known alarms. Users will only receive alarm messages on weekdays, and users need to avoid disturbances at night. - Alarm silence rules support one-time time period or periodic time period, support label matching and alarm level matching. -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### Message Notification @@ -284,20 +284,20 @@ Built-in support for monitoring types include: - The notification policy supports tag matching and alert level matching, which makes it convenient to assign alerts with different tags and alert levels to different receivers and handlers. - Support notification templates, users can customize the content format of the templates to meet their own personalized notification display needs. -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) ### Monitoring Template - HertzBeat makes `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` and other protocols configurable so that you can customize the metrics you want to collect using these protocols by simply configuring the monitoring template `YML` in your browser. Would you believe that you can instantly adapt a new monitoring type such as `K8s` or `Docker` just by configuring it? - All our built-in monitoring types (mysql, website, jvm, k8s) are also mapped to corresponding monitoring templates, so you can add and modify monitoring templates to customize your monitoring functions. -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Collector Cluster @@ -305,16 +305,16 @@ Built-in support for monitoring types include: - The collector cluster supports multi-node deployment, automatic load balancing, automatic failover, etc. - Supports unified management of multiple isolated networks, cloud-edge collaboration. -![HertzBeat](/img/home/18.png) +![HertzBeat](home/static/img/home/18.png) ### Status Page - Based on HertzBeat, quickly build an external status page for your own product and easily convey the real-time status of your product service to users. For example, the service status page provided by Github [https://www.githubstatus.com](https://www.githubstatus.com). - Support synchronization between the status of the status page component and the monitoring status, as well as the fault event maintenance management mechanism, etc. Improve your transparency, professionalism, and user trust, and reduce communication costs. -![HertzBeat](/img/home/19.png) +![HertzBeat](home/static/img/home/19.png) -![HertzBeat](/img/home/status.png) +![HertzBeat](home/static/img/home/status.png) --- diff --git a/home/versioned_docs/version-1.7.x/start/baota-deploy.md b/home/versioned_docs/version-1.7.x/start/baota-deploy.md index 9d7257d80f2..3673d63088e 100644 --- a/home/versioned_docs/version-1.7.x/start/baota-deploy.md +++ b/home/versioned_docs/version-1.7.x/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: Use aaPanel Deploy HertzBeat +id: baota-deploy +title: Use aaPanel Deploy HertzBeat sidebar_label: Install via aaPanel --- @@ -12,19 +12,19 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i ## Install -1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. +1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. - > Install the Docker service, skip if it already exists. + > Install the Docker service, skip if it already exists. - ![HertzBeat](/img/docs/start/install-to-aapanel-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-1.png) 2. Find `HertzBeat` in `One-Click Install` and click `Install` - ![HertzBeat](/img/docs/start/install-to-aapanel-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-2.png) 3. Config the domain, name and others, click `OK` - ![HertzBeat](/img/docs/start/install-to-aapanel-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-3.png) - Name: App name, default the `HertzBeat-random` - Version：Default `latest` - Domain：Config if you need domain access, please configure the domain name here and resolve the domain name to the server @@ -38,6 +38,6 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i - If you have set a domain name, please enter the domain name directly in the browser address bar to access, such as `http://demo.hertzbeat.apache.org`, you can access the `HertzBeat` console. - If you choose to access via `IP+Port`, please enter the domain name in the browser address bar to access `http://\:1157`, you can access the `HertzBeat` console. -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > Default account username: `admin` password: `hertzbeat` diff --git a/home/versioned_docs/version-1.7.x/start/docker-deploy.md b/home/versioned_docs/version-1.7.x/start/docker-deploy.md index 75638876732..570efdb9e9b 100644 --- a/home/versioned_docs/version-1.7.x/start/docker-deploy.md +++ b/home/versioned_docs/version-1.7.x/start/docker-deploy.md @@ -1,6 +1,6 @@ --- -id: docker-deploy -title: Install HertzBeat via Docker +id: docker-deploy +title: Install HertzBeat via Docker sidebar_label: Install via Docker --- @@ -51,7 +51,7 @@ It is necessary to have Docker environment in your environment. If not installed ::: -2. Start to explore HertzBeat +2. Start to explore HertzBeat Access [http://ip:1157/](http://ip:1157/) using browser. You can explore HertzBeat with default account `admin/hertzbeat` now! ### Deploy HertzBeat Collector Cluster(Optional) @@ -61,7 +61,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat By deploying multiple HertzBeat Collectors, high availability, load balancing, and cloud-edge collaboration of data can be achieved. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Execute the following command @@ -109,31 +109,31 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 1. MYSQL, TDENGINE, IoTDB and HertzBeat are deployed on the same host by Docker,HertzBeat use localhost or 127.0.0.1 connect to the database but fail The problems lies in Docker container failed to visit and connect localhost port. Because the docker default network mode is Bridge mode which can't access local machine through localhost. - > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. + > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. > Solution B：Use the Host network mode to start Docker, namely making Docker container and hosting share network. `docker run -d --network host .....` 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues： - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. - > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. + > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. 3. Historical monitoring charts have been missing data for a long time - > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. + > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. > 2: Check whether IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. 4. If the history chart on the monitoring page is not displayed，popup [please configure time series database] - > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. + > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. > Installation and initialization this database, please refer to [Using victoria-metrics to store metrics data](victoria-metrics-init) 5. The time series database is installed and configured, but the page still displays a pop-up [Unable to provide historical chart data, please configure dependent time series database] - > Please check if the configuration parameters are correct - > Is time-series database enable set to true - > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed + > Please check if the configuration parameters are correct + > Is time-series database enable set to true + > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed > You can check the startup logs according to the logs directory 6. What is the purpose of application.yml @@ -149,9 +149,9 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 7. What is the purpose of sureness.yml - > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. - > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` - > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. - > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` - > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. + > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` + > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. + > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` + > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) > For detail steps, please refer to [Configure Account Password](account-modify) diff --git a/home/versioned_docs/version-1.7.x/start/package-deploy.md b/home/versioned_docs/version-1.7.x/start/package-deploy.md index 4ce2a57e7de..ed2db29296f 100644 --- a/home/versioned_docs/version-1.7.x/start/package-deploy.md +++ b/home/versioned_docs/version-1.7.x/start/package-deploy.md @@ -1,6 +1,6 @@ --- -id: package-deploy -title: Install HertzBeat via Package +id: package-deploy +title: Install HertzBeat via Package sidebar_label: Install via Package --- @@ -50,7 +50,7 @@ Since version 1.6.0 uses `Java 17` and the installation package no longer provid Execute the startup script in the installation directory `bin/`, or `startup.bat` in windows. ```shell - ./startup.sh + ./startup.sh ``` 5. Begin to explore HertzBeat @@ -64,7 +64,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat Deploying multiple HertzBeat Collectors can achieve high availability, load balancing, and cloud-edge collaboration of data. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Download installation package @@ -132,6 +132,6 @@ Deploying multiple HertzBeat Collectors can achieve high availability, load bala 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues: - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `hertzbeat/config/application.yml`. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `hertzbeat/config/application.yml`. > 3：Check whether the running log has errors in `hertzbeat/logs/` directory. If you haven't solved the issue, report it to the communication group or community. diff --git a/home/versioned_docs/version-1.7.x/start/rainbond-deploy.md b/home/versioned_docs/version-1.7.x/start/rainbond-deploy.md index 2183dd6b78f..91bf6fd36b8 100644 --- a/home/versioned_docs/version-1.7.x/start/rainbond-deploy.md +++ b/home/versioned_docs/version-1.7.x/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: Use Rainbond Deploy HertzBeat +id: rainbond-deploy +title: Use Rainbond Deploy HertzBeat sidebar_label: Install via Rainbond --- @@ -32,7 +32,7 @@ To install Rainbond, please refer to [Rainbond Quick Install](https://www.rainbo After logging in Rainbond, click Market in the left menu, switch to open source app store, and search HertzBeat in the search box, and click the Install button. -![HertzBeat](/img/docs/start/install-to-rainbond-en.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond-en.png) Fill in the following information, and click Confirm button to install. @@ -43,7 +43,7 @@ Fill in the following information, and click Confirm button to install. After installation, HertzBeat can be accessed via the Access button. -![HertzBeat](/img/docs/start/hertzbeat-topology-en.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology-en.png) :::tip HertzBeat installed via Rainbond, External Mysql database and Redis and IoTDB are used by default, The HertzBeat configuration file is also mounted, which can be modified in `Components -> Environment Configuration -> Configuration File Settings`. diff --git a/home/versioned_docs/version-1.7.x/start/usecase/linux-os-practice.md b/home/versioned_docs/version-1.7.x/start/usecase/linux-os-practice.md index f015609b0dd..b6f2c333664 100644 --- a/home/versioned_docs/version-1.7.x/start/usecase/linux-os-practice.md +++ b/home/versioned_docs/version-1.7.x/start/usecase/linux-os-practice.md @@ -32,7 +32,7 @@ The production environment recommends a complete deployment method, refer [Insta > HertzBeat Page -> Monitors -> New Monitor -> OS Monitor -> Add OS Linux -![HertzBeat](/img/docs/start/linux-os-practice-1.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-1.png) ### 2. Configure the monitoring parameters @@ -47,15 +47,15 @@ The production environment recommends a complete deployment method, refer [Insta Tasks can be managed using label classification, such as adding bind labels like `OS=Linux`. -![HertzBeat](/img/docs/start/linux-os-practice-2.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-2.png) ### 3. View the detection index data In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. -![HertzBeat](/img/docs/start/linux-os-practice-3.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-3.png) -![HertzBeat](/img/docs/start/linux-os-practice-4.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-4.png) ### 4. Set the threshold @@ -65,27 +65,27 @@ Here, we set a threshold rule to trigger an alert when **the usage rate of a cer > > Configure the threshold, configure the alarm expression-triggered when the metric`Disk Usage` greater than or equal to `50%`，set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/linux-os-practice-5.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-5.png) > Threshold rule has others function you can try e.g., associating thresholds with monitoring, trigger times so on. Finally, you can see the triggered alarm in the alarm center. -![HertzBeat](/img/docs/start/linux-os-practice-6.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-6.png) ### 5. Alarm notification > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Configure the Email Receiver -![HertzBeat](/img/docs/start/linux-os-practice-7.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-7.png) > HertzBeat Page -> Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured -![HertzBeat](/img/docs/start/linux-os-practice-8.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-8.png) When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. ----- +---- ## Summary diff --git a/home/versioned_docs/version-1.7.x/start/usecase/springboot-auto-practice.md b/home/versioned_docs/version-1.7.x/start/usecase/springboot-auto-practice.md index a91bb21abf7..1a26c5dc3a6 100644 --- a/home/versioned_docs/version-1.7.x/start/usecase/springboot-auto-practice.md +++ b/home/versioned_docs/version-1.7.x/start/usecase/springboot-auto-practice.md @@ -1,7 +1,7 @@ --- -id: springboot-auto-practice -title: SpringBoot Web Application Monitoring Practice -sidebar_label: SpringBoot Web Application Monitoring Practice +id: springboot-auto-practice +title: SpringBoot Web Application Monitoring Practice +sidebar_label: SpringBoot Web Application Monitoring Practice --- :::tip @@ -136,7 +136,7 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > HertzBeat Page -> Monitors -> New Monitor -> AUTO -> Prometheus Task - ![HertzBeat](/img/docs/start/springboot-auto-practice-1.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-1.png) 2. Fill in Key Parameters @@ -148,15 +148,15 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > > Tasks can be managed using label classification, such as adding Bind Labels like `env=test`. - ![HertzBeat](/img/docs/start/springboot-auto-practice-2.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-2.png) 3. View Detected Metric Data > Click on the newly created monitor to view detailed metric data, historical charts, etc. - ![HertzBeat](/img/docs/start/springboot-auto-practice-3.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-3.png) - ![HertzBeat](/img/docs/start/springboot-auto-practice-4.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-4.png) ## Grafana Visualization Integration (Optional) @@ -174,13 +174,13 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > > For example: In Grafana, select `hertzbeat-victoria-metrics` as the data source. Then click on the dashboard:「Share」→「Export」→「Save to file」to download the template and upload this file to the HertzBeat monitor. - ![HertzBeat](/img/docs/start/springboot-auto-practice-5.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-5.png) 3. View Grafana Dashboard > Go to the AUTO monitor page, click the Grafana icon button, and view the integrated Grafana dashboard. - ![HertzBeat](/img/docs/start/springboot-auto-practice-6.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-6.png) ## Alarm and Notification Interlinkage @@ -188,7 +188,7 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > HertzBeat Page -> Alerting -> Threshold -> New -> New Threshold Rule - ![HertzBeat](/img/docs/start/springboot-auto-practice-7.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-7.png) > HertzBeat provides two types of threshold rule settings: **RealTime Calculation** and **Periodically execute**. Here, we use the **Periodically execute** threshold rule as an example. > @@ -205,21 +205,21 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > >You can create many combinations of threshold rules. Users can set up richer alarm rules based on their specific needs. - ![HertzBeat](/img/docs/start/springboot-auto-practice-8.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-8.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/springboot-auto-practice-9.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-9.png) 3. Alarm Notification > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver - ![HertzBeat](/img/docs/start/springboot-auto-practice-10.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-10.png) > HertzBeat Page -> Notification -> Notice Policy -> New Notice Policy -> Select Recipient(s) and Enable Notification - ![HertzBeat](/img/docs/start/springboot-auto-practice-11.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-11.png) 4. OK! When the threshold is triggered, we will receive the corresponding alarm message. If no notification is configured, you can also view the alarm information in the alarm center. diff --git a/home/versioned_docs/version-1.7.x/start/usecase/sslcert-practice.md b/home/versioned_docs/version-1.7.x/start/usecase/sslcert-practice.md index 8d912fce4b2..c8a48964bda 100644 --- a/home/versioned_docs/version-1.7.x/start/usecase/sslcert-practice.md +++ b/home/versioned_docs/version-1.7.x/start/usecase/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL Certificate Monitoring Practice +id: ssl-cert-practice +title: SSL Certificate Monitoring Practice sidebar_label: SSL Certificate Monitoring Practice --- @@ -34,29 +34,29 @@ The production environment recommends a complete deployment method, refer [https > HertzBeat Page -> Monitors -> New Monitor -> Service Monitor -> Add SSL Certificate - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. Configure the monitoring website - > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. + > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. > Click OK Note - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. View the detection index data > In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. Set the threshold (triggered when the certificate expires) - > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule + > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule > Configure the threshold, select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > Threshold rule has others function you can try eg: associating thresholds with monitoring, trigger times so on. @@ -64,17 +64,17 @@ The production environment recommends a complete deployment method, refer [https > In the same way, switch coding threshold, add a new configuration threshold and configure an alarm expression - when the metric expires timestamp `end_timestamp`, the `now()` function is the current timestamp, if the configuration triggers an alarm one week in advance: `end_timestamp <= (now() + 604800000)` , where `604800000` is the 7-day total time difference in milliseconds. - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. Alarm notification (in time notification via Dingding WeChat Feishu, etc.) > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Config the Feishu Receiver - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) For token configuration such as Feishu, please refer to the help document @@ -82,7 +82,7 @@ The production environment recommends a complete deployment method, refer [https > Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. diff --git a/home/versioned_docs/version-1.7.x/start/usecase/tdengine-practice.md b/home/versioned_docs/version-1.7.x/start/usecase/tdengine-practice.md index fae07ada5ca..96368e8dab4 100644 --- a/home/versioned_docs/version-1.7.x/start/usecase/tdengine-practice.md +++ b/home/versioned_docs/version-1.7.x/start/usecase/tdengine-practice.md @@ -1,6 +1,6 @@ --- -id: tdengine-practice -title: TDengine Monitoring Practice +id: tdengine-practice +title: TDengine Monitoring Practice sidebar_label: TDengine Monitoring Practice --- @@ -40,7 +40,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Monitoring Center -> Add Monitoring -> Custom Monitoring -> TDengine-PromQL Task - ![HertzBeat](/img/docs/start/tdengine_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1.png) 2. Fill in key parameters @@ -52,15 +52,15 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > You can use tags to categorize tasks, such as adding business-related tags like `env=test`. - ![HertzBeat](/img/docs/start/tdengine_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_2.png) 3. View inspection indicator data > You can view task statuses in the monitoring list and view metric data charts and other information in the monitoring details. - ![HertzBeat](/img/docs/start/tdengine_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_3.png) - ![HertzBeat](/img/docs/start/tdengine_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_4.png) ## Monitor TDengine(Prometheus) @@ -68,7 +68,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Monitoring Center -> Add Monitoring -> AUTO -> Prometheus Task - ![HertzBeat](/img/docs/start/tdengine_1_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_1.png) 2. Fill in key parameters @@ -80,15 +80,15 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > You can use tags to categorize tasks, such as adding business-related tags like `env=test`. - ![HertzBeat](/img/docs/start/tdengine_1_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_2.png) 3. View inspection indicator data > You can view task statuses in the monitoring list and view metric data charts and other information in the monitoring details. - ![HertzBeat](/img/docs/start/tdengine_1_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_3.png) - ![HertzBeat](/img/docs/start/tdengine_1_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_4.png) ### Grafana visualization integration (optional) @@ -106,13 +106,13 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > For example: Select the Grafana data source `hertzbeat-victoria-metrics`, then click "Share" → "Export" → "Save to file" on the dashboard to download the template and upload it to HertzBeat monitoring. For reference, see: [taoskeeper-prometheus-dashboard](https://grafana.com/grafana/dashboards/15164-taoskeeper-prometheus-dashboard/) - ![HertzBeat](/img/docs/start/tdengine_1_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_5.png) 3. View Grafana charts > Go to the new AUTO monitoring page, click the Grafana icon button to view the Grafana chart. - ![HertzBeat](/img/docs/start/tdengine_1_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_6.png) ## Alarm and notification linkage @@ -120,7 +120,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Alerts -> Threshold Rules -> Add -> Add Threshold - ![HertzBeat](/img/docs/start/tdengine_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_5.png) > HertzBeat provides two types of threshold rule settings: **real-time calculation** and **scheduled cycle**. Here, we will use the **scheduled cycle** threshold rule as an example. > @@ -137,21 +137,21 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > There are many combinations of threshold rules that can be set, and users can set more detailed alert rules according to their needs. - ![HertzBeat](/img/docs/start/tdengine_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_6.png) > Finally, you can see the triggered alerts in the Alert Center. - ![HertzBeat](/img/docs/start/tdengine_7.png) + ![HertzBeat](home/static/img/docs/start/tdengine_7.png) 3. Alert notification > System Page -> Message Notifications -> Notification Media -> Add New Recipient - ![HertzBeat](/img/docs/start/tdengine_8.png) + ![HertzBeat](home/static/img/docs/start/tdengine_8.png) > System Page -> Message Notifications -> Notification Policies -> Add Notification Policy -> Select recipients and enable notifications - ![HertzBeat](/img/docs/start/tdengine_9.png) + ![HertzBeat](home/static/img/docs/start/tdengine_9.png) 4. OK! When the threshold rule is triggered, we will receive the corresponding alert message. If no notification is configured, you can also view the alert information in the alert center. diff --git a/home/versioned_docs/version-1.7.x/template.md b/home/versioned_docs/version-1.7.x/template.md index b88ebcd9325..80ea874935a 100644 --- a/home/versioned_docs/version-1.7.x/template.md +++ b/home/versioned_docs/version-1.7.x/template.md @@ -1,6 +1,6 @@ --- -id: template -title: Monitoring Template Here +id: template +title: Monitoring Template Here sidebar_label: Monitoring Template --- @@ -11,11 +11,11 @@ sidebar_label: Monitoring Template Here is the architecture. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **We define all monitoring collection types (mysql, website, jvm, k8s) as yml templates, and users can import these templates into the hertzbeat system to support corresponding types of monitoring, which is very convenient!** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **Welcome everyone to contribute your customized general monitoring type YML template during use. The available templates are as follows:** diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md b/home/versioned_docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md index 482712129b2..205f6c36eb8 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-http-example-hertzbeat.md @@ -191,19 +191,19 @@ metrics: **The addition is complete, now we save and apply. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-http-example-token.md b/home/versioned_docs/version-1.8.0/advanced/extend-http-example-token.md index 35a0c8cef65..c08ef5c8aa7 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-http-example-token.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-http-example-token.md @@ -229,13 +229,13 @@ metrics: } ``` -![HertzBeat](/img/docs/advanced/extend-http-example-5.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-5.png) **After the addition is successful, we can see the `token`, `refreshToken` metric data we collected on the details page.** -![HertzBeat](/img/docs/advanced/extend-http-example-6.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-6.png) -![HertzBeat](/img/docs/advanced/extend-http-example-7.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-7.png) ### Use `token` as a variable parameter to collect and use the following metricss @@ -389,9 +389,9 @@ metrics: **After the configuration is complete, save and apply, and check the monitoring details page** -![HertzBeat](/img/docs/advanced/extend-http-example-8.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-8.png) -![HertzBeat](/img/docs/advanced/extend-http-example-9.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-9.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-jmx.md b/home/versioned_docs/version-1.8.0/advanced/extend-jmx.md index 29f1bc3ff44..eaf1a16d151 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-jmx.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-jmx.md @@ -21,7 +21,7 @@ By configuring the monitoring template YML metrics `field`, `aliasFields`, `obje **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-push.md b/home/versioned_docs/version-1.8.0/advanced/extend-push.md index 1762fc7b751..e950a964608 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-push.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-push.md @@ -1,6 +1,6 @@ --- -id: extend-push -title: Push Style Custom Monitoring +id: extend-push +title: Push Style Custom Monitoring sidebar_label: Push Style Custom Monitoring --- @@ -23,4 +23,4 @@ HertzBeat DashBoard -> Service Monitor -> Push Style Monitor -> New Push Style M ### Monitor Configuration Example -![HertzBeat](/img/docs/advanced/extend-push-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-push-example-1.png) diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-snmp.md b/home/versioned_docs/version-1.8.0/advanced/extend-snmp.md index ce39f61ec80..345d46b97c3 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-snmp.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-snmp.md @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields`, and `oids` under the `snmp` p **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-telnet.md b/home/versioned_docs/version-1.8.0/advanced/extend-telnet.md index c4a65f885db..c3710905b58 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-telnet.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-telnet.md @@ -1,5 +1,5 @@ --- -id: extend-telnet +id: extend-telnet title: Telnet Protocol Custom Monitoring sidebar_label: Telnet Protocol Custom Monitoring --- @@ -21,7 +21,7 @@ By configuring the metrics `field`, `aliasFields` the `Telnet` protocol of the m **HertzBeat Dashboard** -> **Monitoring Templates** -> **New Template** -> **Config Monitoring Template Yml** -> **Save and Apply** -> **Add A Monitoring with The New Monitoring Type** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) ------- @@ -295,5 +295,5 @@ metrics: timeout: ^_^timeout^_^ cmd: mntr - + ``` diff --git a/home/versioned_docs/version-1.8.0/advanced/extend-tutorial.md b/home/versioned_docs/version-1.8.0/advanced/extend-tutorial.md index 6c774d84216..a254793ae3b 100644 --- a/home/versioned_docs/version-1.8.0/advanced/extend-tutorial.md +++ b/home/versioned_docs/version-1.8.0/advanced/extend-tutorial.md @@ -203,19 +203,19 @@ metrics: **The addition is complete, now we restart the hertzbeat system. We can see that the system page has added a `hertzbeat` monitoring type.** -![HertzBeat](/img/docs/advanced/extend-http-example-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-1.png) ### The system page adds the monitoring of `hertzbeat` monitoring type > We click Add `HertzBeat Monitoring Tool`, configure monitoring IP, port, collection cycle, account password in advanced settings, etc., click OK to add monitoring. -![HertzBeat](/img/docs/advanced/extend-http-example-2.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-2.png) -![HertzBeat](/img/docs/advanced/extend-http-example-3.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-3.png) > After a certain period of time (depending on the collection cycle), we can see the specific metric data and historical charts in the monitoring details! -![HertzBeat](/img/docs/advanced/extend-http-example-4.png) +![HertzBeat](home/static/img/docs/advanced/extend-http-example-4.png) ### Set threshold alarm notification diff --git a/home/versioned_docs/version-1.8.0/help/alert_threshold.md b/home/versioned_docs/version-1.8.0/help/alert_threshold.md index be8e90bc5f7..1d569645873 100644 --- a/home/versioned_docs/version-1.8.0/help/alert_threshold.md +++ b/home/versioned_docs/version-1.8.0/help/alert_threshold.md @@ -26,7 +26,7 @@ Support visual page configuration or more flexible expression rule configuration Configure the threshold, for example: Select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) Configuration item details: diff --git a/home/versioned_docs/version-1.8.0/help/redis_cluster.md b/home/versioned_docs/version-1.8.0/help/redis_cluster.md index e548d0eb91d..d030162e9da 100644 --- a/home/versioned_docs/version-1.8.0/help/redis_cluster.md +++ b/home/versioned_docs/version-1.8.0/help/redis_cluster.md @@ -98,7 +98,7 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to "187b879f73c473b3cbb82ff95f668e65af46115ddaa27f3ff1a712332b981531": { ... "Name": "redis-slave-2", - "IPv4Address": "192.168.117.6/24", + "IPv4Address": "192.168.117.6/24", ... }, "45e22b64c82e51857fc104436cdd6cc0c5776ad10a2e4b9d8e52e36cfb87217e": { @@ -155,11 +155,11 @@ keywords: [ open source monitoring tool, open source Redis Cluster monitoring to Add a redis monitor center, fill require parameters. - ![HertzBeat](/img/docs/help/redis-cluster-add.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-add.png) final effect. - ![HertzBeat](/img/docs/help/redis-cluster-view.png) + ![HertzBeat](home/static/img/docs/help/redis-cluster-view.png) ### Configuration Parameters diff --git a/home/versioned_docs/version-1.8.0/help/status.md b/home/versioned_docs/version-1.8.0/help/status.md index daf362a0f5c..fc8c7b91fc2 100644 --- a/home/versioned_docs/version-1.8.0/help/status.md +++ b/home/versioned_docs/version-1.8.0/help/status.md @@ -1,7 +1,7 @@ --- -id: status -title: Status Page -sidebar_label: Status Page +id: status +title: Status Page +sidebar_label: Status Page keywords: [Open Source Monitoring System, Open Source Website Monitoring, Status Page] --- @@ -24,7 +24,7 @@ The fields that need to be filled in are as follows: After filling in the organization information, click `Confirm`. -![HertzBeat](/img/docs/help/status-3.png) +![HertzBeat](home/static/img/docs/help/status-3.png) ## 2. Add Component @@ -51,7 +51,7 @@ status: interval: 60 ``` -![HertzBeat](/img/docs/help/status-4.png) +![HertzBeat](home/static/img/docs/help/status-4.png) ## 3. Maintain Events @@ -59,7 +59,7 @@ When an event occurs, you can publish a notification on the status page. Click `Publish Event` -![HertzBeat](/img/docs/help/status-1.png) +![HertzBeat](home/static/img/docs/help/status-1.png) | Field Name | Field Description | Example | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -70,4 +70,4 @@ Click `Publish Event` > Note: You can publish messages multiple times to keep the team updated on the current status. -![HertzBeat](/img/docs/help/status-2.png) +![HertzBeat](home/static/img/docs/help/status-2.png) diff --git a/home/versioned_docs/version-1.8.0/introduce.md b/home/versioned_docs/version-1.8.0/introduce.md index a4a9c4eb91c..c883347a3ed 100644 --- a/home/versioned_docs/version-1.8.0/introduce.md +++ b/home/versioned_docs/version-1.8.0/introduce.md @@ -32,11 +32,11 @@ slug: / HertzBeat itself did not create a data collection protocol for the monitoring client to adapt to. Instead, HertzBeat makes full use of the existing ecosystem, `SNMP protocol` to collect information from network switches and routers, `JMX specification` to collect information from Java applications, `JDBC specification` to collect information from datasets, `SSH` to directly connect to scripts to get the display information, `HTTP+ (JsonPath | prometheus, etc.)` to parse the information from API interfaces, `IPMI protocol` to collect server information, and so on. HertzBeat uses these existing standard protocols or specifications, makes them abstractly configurable, and finally makes them all available in the form of YML format monitoring templates that can be written to create templates that use these protocols to collect any desired metrics data. -![HertzBeat](/img/blog/multi-protocol.png) +![HertzBeat](home/static/img/blog/multi-protocol.png) Do you believe that users can just write a monitoring template on the UI page, click save and immediately adapt a new monitoring type like `K8s` or `Docker`? -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Built-in Monitoring Types @@ -87,7 +87,7 @@ Do you believe that users can just write a monitoring template on the UI page, c > Each monitor type is considered as a monitor template, no matter it is built-in or user-defined. You can easily add, modify and delete indicators by modifying the monitoring template. > The templates contain a series of functions such as protocol configuration, environment variables, metrics conversion, metrics calculation, units conversion, metrics collection, etc., which help users to collect the metrics they want. -![HertzBeat](/img/docs/custom-arch.png) +![HertzBeat](home/static/img/docs/custom-arch.png) ### No Agent Required @@ -110,7 +110,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t - Monitoring tasks are self-scheduled in the collector cluster, single collector hangs without sensing the failure to migrate the collection tasks, and the newly added collector nodes are automatically scheduled to share the collection pressure. - It is very easy to switch between stand-alone mode and cluster mode without additional component deployment. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Cloud Edge Collaboration @@ -119,7 +119,7 @@ The principle of `HertzBeat` is to use different protocols to connect directly t In an isolated network where multiple networks are not connected, we need to deploy a monitoring system in each network in the previous solution, which leads to data non-interoperability and inconvenient management, deployment and maintenance. `HertzBeat` provides the ability of cloud edge collaboration, can be deployed in multiple isolated networks edge collector, collector in the isolated network within the monitoring task collection, collection of data reported by the main service unified scheduling management display. -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) ### Easy to Use @@ -155,7 +155,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat - HertzBeat's user management is unified by the configuration file `sureness.yml`, which allows users to add, delete, and modify user information, user role permissions, and so on. Default password admin/hertzbeat -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) ### Overview Page @@ -163,7 +163,7 @@ Browser access `http://localhost:1157` default account password `admin/hertzbeat - Show the status of currently registered collector clusters, including collector on-line status, monitoring tasks, startup time, IP address, name and so on. - Show the list of recent alarm messages, alarm level distribution etc. -![HertzBeat](/img/home/1.png) +![HertzBeat](home/static/img/home/1.png) ### Monitoring Center @@ -210,7 +210,7 @@ Built-in support for monitoring types include: [HuaweiSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-huawei_switch.yml), [TpLinkSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-tplink_switch.yml), [H3cSwitch](https://raw.githubusercontent.com/apache/hertzbeat/master/hertzbeat-manager/src/main/resources/define/app-h3c_switch.yml) -![HertzBeat](/img/home/2.png) +![HertzBeat](home/static/img/home/2.png) ### New Monitor @@ -218,7 +218,7 @@ Built-in support for monitoring types include: - The monitoring parameters configured on the page are defined by the monitoring template of the corresponding monitoring type, and users can modify the configuration parameters on the page by modifying the monitoring template. - Support associated tags to manage monitoring grouping, alarm matching, and so on. -![HertzBeat](/img/home/10.png) +![HertzBeat](home/static/img/home/10.png) ### Monitor Details @@ -227,16 +227,16 @@ Built-in support for monitoring types include: - Monitor Historical Data Report displays the historical values of the currently monitored metrics in the form of trend charts, supports querying hourly, daily and monthly historical data, and supports configuring the page refresh time. - ⚠️ Note that the monitoring history charts need to be configured with an external timing database in order to get the full functionality. -![HertzBeat](/img/home/3.png) +![HertzBeat](home/static/img/home/3.png) -![HertzBeat](/img/home/4.png) +![HertzBeat](home/static/img/home/4.png) ### Alarm Center - The management display page of triggered alarm messages enables users to visualize the current alarm situation. - Support alarm processing, alarm marking unprocessed, alarm deletion, clearing and other batch operations. -![HertzBeat](/img/home/7.png) +![HertzBeat](home/static/img/home/7.png) ### Alarm Threshold @@ -244,29 +244,29 @@ Built-in support for monitoring types include: - Support real-time threshold and scheduled threshold, real-time threshold can directly trigger the alarm when monitoring data is collected, scheduled threshold supports PromQL and other expressions to calculate the trigger alarm within a specified time period. - Support visual page configuration or more flexible expression rule configuration, support configuring trigger times, alarm levels, notification templates, associated specified monitoring and so on. -![HertzBeat](/img/home/6.png) +![HertzBeat](home/static/img/home/6.png) -![HertzBeat](/img/docs/start/ssl_5.png) +![HertzBeat](home/static/img/docs/start/ssl_5.png) ### Alarm Integration - Integration with third-party monitoring systems such as `Prometheus`, `WebHook`, `Skywalking`, `AlertManager`, etc. to receive alarm messages from these systems and perform alarm processing. -![HertzBeat](/img/home/11.png) +![HertzBeat](home/static/img/home/11.png) ### Alarm Grouping - Group convergence supports merging alarms for specified group labels by grouping. It deduplicates and converges the same repeated alarms in a time period. - When the threshold rule triggers an alarm or an external alarm is reported, it will enter the grouping convergence for alarm grouping and alarm deduplication to avoid alarm storms caused by a large number of alarm messages. -![HertzBeat](/img/home/12.png) +![HertzBeat](home/static/img/home/12.png) ### Alarm Inhibition - Alarm suppression is used to configure the suppression relationship between alarms. For example, high-level alarms suppress low-level alarms under the same instance. - When an alarm occurs, it can suppress the occurrence of other alarms. For example, when a server crashes, it can suppress all alarms on that server. -![HertzBeat](/img/home/13.png) +![HertzBeat](home/static/img/home/13.png) ### Alarm Silence @@ -274,7 +274,7 @@ Built-in support for monitoring types include: - This application scenario, such as users in the system maintenance, do not need to send known alarms. Users will only receive alarm messages on weekdays, and users need to avoid disturbances at night. - Alarm silence rules support one-time time period or periodic time period, support label matching and alarm level matching. -![HertzBeat](/img/home/15.png) +![HertzBeat](home/static/img/home/15.png) ### Message Notification @@ -284,20 +284,20 @@ Built-in support for monitoring types include: - The notification policy supports tag matching and alert level matching, which makes it convenient to assign alerts with different tags and alert levels to different receivers and handlers. - Support notification templates, users can customize the content format of the templates to meet their own personalized notification display needs. -![HertzBeat](/img/home/16.png) +![HertzBeat](home/static/img/home/16.png) -![HertzBeat](/img/home/17.png) +![HertzBeat](home/static/img/home/17.png) -![HertzBeat](/img/home/8.png) +![HertzBeat](home/static/img/home/8.png) -![HertzBeat](/img/home/14.png) +![HertzBeat](home/static/img/home/14.png) ### Monitoring Template - HertzBeat makes `Http, Jmx, Ssh, Snmp, Jdbc, Prometheus` and other protocols configurable so that you can customize the metrics you want to collect using these protocols by simply configuring the monitoring template `YML` in your browser. Would you believe that you can instantly adapt a new monitoring type such as `K8s` or `Docker` just by configuring it? - All our built-in monitoring types (mysql, website, jvm, k8s) are also mapped to corresponding monitoring templates, so you can add and modify monitoring templates to customize your monitoring functions. -![HertzBeat](/img/home/9.png) +![HertzBeat](home/static/img/home/9.png) ### Collector Cluster @@ -305,16 +305,16 @@ Built-in support for monitoring types include: - The collector cluster supports multi-node deployment, automatic load balancing, automatic failover, etc. - Supports unified management of multiple isolated networks, cloud-edge collaboration. -![HertzBeat](/img/home/18.png) +![HertzBeat](home/static/img/home/18.png) ### Status Page - Based on HertzBeat, quickly build an external status page for your own product and easily convey the real-time status of your product service to users. For example, the service status page provided by Github [https://www.githubstatus.com](https://www.githubstatus.com). - Support synchronization between the status of the status page component and the monitoring status, as well as the fault event maintenance management mechanism, etc. Improve your transparency, professionalism, and user trust, and reduce communication costs. -![HertzBeat](/img/home/19.png) +![HertzBeat](home/static/img/home/19.png) -![HertzBeat](/img/home/status.png) +![HertzBeat](home/static/img/home/status.png) --- diff --git a/home/versioned_docs/version-1.8.0/start/baota-deploy.md b/home/versioned_docs/version-1.8.0/start/baota-deploy.md index 9d7257d80f2..3673d63088e 100644 --- a/home/versioned_docs/version-1.8.0/start/baota-deploy.md +++ b/home/versioned_docs/version-1.8.0/start/baota-deploy.md @@ -1,6 +1,6 @@ --- -id: baota-deploy -title: Use aaPanel Deploy HertzBeat +id: baota-deploy +title: Use aaPanel Deploy HertzBeat sidebar_label: Install via aaPanel --- @@ -12,19 +12,19 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i ## Install -1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. +1. Log in, click `Docker` menu and install the `Docker` `Docker Compose` according the prompts. - > Install the Docker service, skip if it already exists. + > Install the Docker service, skip if it already exists. - ![HertzBeat](/img/docs/start/install-to-aapanel-1.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-1.png) 2. Find `HertzBeat` in `One-Click Install` and click `Install` - ![HertzBeat](/img/docs/start/install-to-aapanel-2.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-2.png) 3. Config the domain, name and others, click `OK` - ![HertzBeat](/img/docs/start/install-to-aapanel-3.png) + ![HertzBeat](home/static/img/docs/start/install-to-aapanel-3.png) - Name: App name, default the `HertzBeat-random` - Version：Default `latest` - Domain：Config if you need domain access, please configure the domain name here and resolve the domain name to the server @@ -38,6 +38,6 @@ Install aaPanel, go to the [aaPanel](https://www.aapanel.com/new/download.html#i - If you have set a domain name, please enter the domain name directly in the browser address bar to access, such as `http://demo.hertzbeat.apache.org`, you can access the `HertzBeat` console. - If you choose to access via `IP+Port`, please enter the domain name in the browser address bar to access `http://\:1157`, you can access the `HertzBeat` console. -![HertzBeat](/img/home/0.png) +![HertzBeat](home/static/img/home/0.png) > Default account username: `admin` password: `hertzbeat` diff --git a/home/versioned_docs/version-1.8.0/start/docker-deploy.md b/home/versioned_docs/version-1.8.0/start/docker-deploy.md index 75638876732..570efdb9e9b 100644 --- a/home/versioned_docs/version-1.8.0/start/docker-deploy.md +++ b/home/versioned_docs/version-1.8.0/start/docker-deploy.md @@ -1,6 +1,6 @@ --- -id: docker-deploy -title: Install HertzBeat via Docker +id: docker-deploy +title: Install HertzBeat via Docker sidebar_label: Install via Docker --- @@ -51,7 +51,7 @@ It is necessary to have Docker environment in your environment. If not installed ::: -2. Start to explore HertzBeat +2. Start to explore HertzBeat Access [http://ip:1157/](http://ip:1157/) using browser. You can explore HertzBeat with default account `admin/hertzbeat` now! ### Deploy HertzBeat Collector Cluster(Optional) @@ -61,7 +61,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat By deploying multiple HertzBeat Collectors, high availability, load balancing, and cloud-edge collaboration of data can be achieved. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Execute the following command @@ -109,31 +109,31 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 1. MYSQL, TDENGINE, IoTDB and HertzBeat are deployed on the same host by Docker,HertzBeat use localhost or 127.0.0.1 connect to the database but fail The problems lies in Docker container failed to visit and connect localhost port. Because the docker default network mode is Bridge mode which can't access local machine through localhost. - > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. + > Solution A：Configure application.yml. Change database connection address from localhost to external IP of the host machine. > Solution B：Use the Host network mode to start Docker, namely making Docker container and hosting share network. `docker run -d --network host .....` 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues： - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. - > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. + > 3：`docker logs hertzbeat` Check whether the container log has errors. If you haven't solved the issue, report it to the communication group or community. 3. Historical monitoring charts have been missing data for a long time - > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. + > 1：Check whether you configure victoria-metrics or Tdengine or IoTDB. No configuration means no historical chart data. > 2: Check whether IP account and password configuration is correct in HertzBeat's configuration file `application.yml`. 4. If the history chart on the monitoring page is not displayed，popup [please configure time series database] - > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. + > As shown in the popup window，the premise of history chart display is that you need install and configure hertzbeat's dependency service database. > Installation and initialization this database, please refer to [Using victoria-metrics to store metrics data](victoria-metrics-init) 5. The time series database is installed and configured, but the page still displays a pop-up [Unable to provide historical chart data, please configure dependent time series database] - > Please check if the configuration parameters are correct - > Is time-series database enable set to true - > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed + > Please check if the configuration parameters are correct + > Is time-series database enable set to true + > Note⚠️If both hertzbeat and time-series database are started under the same host for docker containers, 127.0.0.1 cannot be used for communication between containers by default, and the host IP is changed > You can check the startup logs according to the logs directory 6. What is the purpose of application.yml @@ -149,9 +149,9 @@ By deploying multiple HertzBeat Collectors, high availability, load balancing, a 7. What is the purpose of sureness.yml - > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. - > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` - > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. - > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` - > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) + > This file is the user configuration file of HertzBeat, used to configure user information of HertzBeat, such as account password, etc. + > HertzBeat default built-in three user accounts, respectively `admin/hertzbeat tom/hertzbeat guest/hertzbeat` + > If you need update account or password, configure `sureness.yml`. Ignore this step without this demand. + > Download and config `sureness.yml` in the host directory，eg:`$(pwd)/sureness.yml` + > Download from [github/script/sureness.yml](https://github.com/apache/hertzbeat/raw/master/script/sureness.yml) > For detail steps, please refer to [Configure Account Password](account-modify) diff --git a/home/versioned_docs/version-1.8.0/start/package-deploy.md b/home/versioned_docs/version-1.8.0/start/package-deploy.md index 4ce2a57e7de..ed2db29296f 100644 --- a/home/versioned_docs/version-1.8.0/start/package-deploy.md +++ b/home/versioned_docs/version-1.8.0/start/package-deploy.md @@ -1,6 +1,6 @@ --- -id: package-deploy -title: Install HertzBeat via Package +id: package-deploy +title: Install HertzBeat via Package sidebar_label: Install via Package --- @@ -50,7 +50,7 @@ Since version 1.6.0 uses `Java 17` and the installation package no longer provid Execute the startup script in the installation directory `bin/`, or `startup.bat` in windows. ```shell - ./startup.sh + ./startup.sh ``` 5. Begin to explore HertzBeat @@ -64,7 +64,7 @@ HertzBeat Collector is a lightweight data collector used to collect and send dat Deploying multiple HertzBeat Collectors can achieve high availability, load balancing, and cloud-edge collaboration of data. ::: -![HertzBeat](/img/docs/cluster-arch.png) +![HertzBeat](home/static/img/docs/cluster-arch.png) 1. Download installation package @@ -132,6 +132,6 @@ Deploying multiple HertzBeat Collectors can achieve high availability, load bala 2. According to the process deploy，visit [http://ip:1157/](http://ip:1157/) no interface Please refer to the following points to troubleshoot issues: - > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. - > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `hertzbeat/config/application.yml`. + > 1：If you switch to dependency service MYSQL database，check whether the database is created and started successfully. + > 2：Check whether dependent services, IP account and password configuration is correct in HertzBeat's configuration file `hertzbeat/config/application.yml`. > 3：Check whether the running log has errors in `hertzbeat/logs/` directory. If you haven't solved the issue, report it to the communication group or community. diff --git a/home/versioned_docs/version-1.8.0/start/rainbond-deploy.md b/home/versioned_docs/version-1.8.0/start/rainbond-deploy.md index 2183dd6b78f..91bf6fd36b8 100644 --- a/home/versioned_docs/version-1.8.0/start/rainbond-deploy.md +++ b/home/versioned_docs/version-1.8.0/start/rainbond-deploy.md @@ -1,6 +1,6 @@ --- -id: rainbond-deploy -title: Use Rainbond Deploy HertzBeat +id: rainbond-deploy +title: Use Rainbond Deploy HertzBeat sidebar_label: Install via Rainbond --- @@ -32,7 +32,7 @@ To install Rainbond, please refer to [Rainbond Quick Install](https://www.rainbo After logging in Rainbond, click Market in the left menu, switch to open source app store, and search HertzBeat in the search box, and click the Install button. -![HertzBeat](/img/docs/start/install-to-rainbond-en.png) +![HertzBeat](home/static/img/docs/start/install-to-rainbond-en.png) Fill in the following information, and click Confirm button to install. @@ -43,7 +43,7 @@ Fill in the following information, and click Confirm button to install. After installation, HertzBeat can be accessed via the Access button. -![HertzBeat](/img/docs/start/hertzbeat-topology-en.png) +![HertzBeat](home/static/img/docs/start/hertzbeat-topology-en.png) :::tip HertzBeat installed via Rainbond, External Mysql database and Redis and IoTDB are used by default, The HertzBeat configuration file is also mounted, which can be modified in `Components -> Environment Configuration -> Configuration File Settings`. diff --git a/home/versioned_docs/version-1.8.0/start/usecase/linux-os-practice.md b/home/versioned_docs/version-1.8.0/start/usecase/linux-os-practice.md index 27f06ba6f51..d8e164845bd 100644 --- a/home/versioned_docs/version-1.8.0/start/usecase/linux-os-practice.md +++ b/home/versioned_docs/version-1.8.0/start/usecase/linux-os-practice.md @@ -32,7 +32,7 @@ The production environment recommends a complete deployment method, refer [Insta > HertzBeat Page -> Monitors -> New Monitor -> OS Monitor -> Add OS Linux -![HertzBeat](/img/docs/start/linux-os-practice-1.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-1.png) ### 2. Configure the monitoring parameters @@ -47,15 +47,15 @@ The production environment recommends a complete deployment method, refer [Insta Tasks can be managed using label classification, such as adding bind labels like `OS=Linux`. -![HertzBeat](/img/docs/start/linux-os-practice-2.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-2.png) ### 3. View the detection index data In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. -![HertzBeat](/img/docs/start/linux-os-practice-3.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-3.png) -![HertzBeat](/img/docs/start/linux-os-practice-4.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-4.png) ### 4. Set the threshold @@ -65,23 +65,23 @@ Here, we set a threshold rule to trigger an alert when **the usage rate of a cer > > Configure the threshold, configure the alarm expression-triggered when the metric`Disk Usage` greater than or equal to `50%`，set the alarm level notification template information, etc. -![HertzBeat](/img/docs/start/linux-os-practice-5.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-5.png) > Threshold rule has others function you can try e.g., associating thresholds with monitoring, trigger times so on. Finally, you can see the triggered alarm in the alarm center. -![HertzBeat](/img/docs/start/linux-os-practice-6.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-6.png) ### 5. Alarm notification > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Configure the Email Receiver -![HertzBeat](/img/docs/start/linux-os-practice-7.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-7.png) > HertzBeat Page -> Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured -![HertzBeat](/img/docs/start/linux-os-practice-8.png) +![HertzBeat](home/static/img/docs/start/linux-os-practice-8.png) When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. diff --git a/home/versioned_docs/version-1.8.0/start/usecase/springboot-auto-practice.md b/home/versioned_docs/version-1.8.0/start/usecase/springboot-auto-practice.md index 636aa6d95b1..0eb11b071ac 100644 --- a/home/versioned_docs/version-1.8.0/start/usecase/springboot-auto-practice.md +++ b/home/versioned_docs/version-1.8.0/start/usecase/springboot-auto-practice.md @@ -1,7 +1,7 @@ --- -id: springboot-auto-practice -title: SpringBoot Web Application Monitoring Practice -sidebar_label: SpringBoot Web Application Monitoring Practice +id: springboot-auto-practice +title: SpringBoot Web Application Monitoring Practice +sidebar_label: SpringBoot Web Application Monitoring Practice --- :::tip @@ -136,7 +136,7 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > HertzBeat Page -> Monitors -> New Monitor -> AUTO -> Prometheus Task - ![HertzBeat](/img/docs/start/springboot-auto-practice-1.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-1.png) 2. Fill in Key Parameters @@ -148,15 +148,15 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > > Tasks can be managed using label classification, such as adding Bind Labels like `env=test`. - ![HertzBeat](/img/docs/start/springboot-auto-practice-2.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-2.png) 3. View Detected Metric Data > Click on the newly created monitor to view detailed metric data, historical charts, etc. - ![HertzBeat](/img/docs/start/springboot-auto-practice-3.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-3.png) - ![HertzBeat](/img/docs/start/springboot-auto-practice-4.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-4.png) ## Grafana Visualization Integration (Optional) @@ -174,13 +174,13 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > > For example: In Grafana, select `hertzbeat-victoria-metrics` as the data source. Then click on the dashboard:「Share」→「Export」→「Save to file」to download the template and upload this file to the HertzBeat monitor. - ![HertzBeat](/img/docs/start/springboot-auto-practice-5.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-5.png) 3. View Grafana Dashboard > Go to the AUTO monitor page, click the Grafana icon button, and view the integrated Grafana dashboard. - ![HertzBeat](/img/docs/start/springboot-auto-practice-6.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-6.png) ## Alarm and Notification Interlinkage @@ -188,7 +188,7 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > HertzBeat Page -> Alerting -> Threshold -> New -> New Threshold Rule - ![HertzBeat](/img/docs/start/springboot-auto-practice-7.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-7.png) > HertzBeat provides two types of threshold rule settings: **RealTime Calculation** and **Periodically execute**. Here, we use the **Periodically execute** threshold rule as an example. > @@ -205,21 +205,21 @@ Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring > >You can create many combinations of threshold rules. Users can set up richer alarm rules based on their specific needs. - ![HertzBeat](/img/docs/start/springboot-auto-practice-8.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-8.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/springboot-auto-practice-9.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-9.png) 3. Alarm Notification > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver - ![HertzBeat](/img/docs/start/springboot-auto-practice-10.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-10.png) > HertzBeat Page -> Notification -> Notice Policy -> New Notice Policy -> Select Recipient(s) and Enable Notification - ![HertzBeat](/img/docs/start/springboot-auto-practice-11.png) + ![HertzBeat](home/static/img/docs/start/springboot-auto-practice-11.png) 4. OK! When the threshold is triggered, we will receive the corresponding alarm message. If no notification is configured, you can also view the alarm information in the alarm center. diff --git a/home/versioned_docs/version-1.8.0/start/usecase/sslcert-practice.md b/home/versioned_docs/version-1.8.0/start/usecase/sslcert-practice.md index 1219bb6e617..07aa0e47f05 100644 --- a/home/versioned_docs/version-1.8.0/start/usecase/sslcert-practice.md +++ b/home/versioned_docs/version-1.8.0/start/usecase/sslcert-practice.md @@ -1,6 +1,6 @@ --- -id: ssl-cert-practice -title: SSL Certificate Monitoring Practice +id: ssl-cert-practice +title: SSL Certificate Monitoring Practice sidebar_label: SSL Certificate Monitoring Practice --- @@ -34,29 +34,29 @@ The production environment recommends a complete deployment method, refer [https > HertzBeat Page -> Monitors -> New Monitor -> Service Monitor -> Add SSL Certificate - ![HertzBeat](/img/docs/start/ssl_1.png) + ![HertzBeat](home/static/img/docs/start/ssl_1.png) 2. Configure the monitoring website - > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. + > Here we take the example of monitoring Baidu website, configure monitoring host domain name, name, collection interval, etc. > Click OK Note - ![HertzBeat](/img/docs/start/ssl_2.png) + ![HertzBeat](home/static/img/docs/start/ssl_2.png) 3. View the detection index data > In the monitoring list, you can view the monitoring status, and in the monitoring details, you can view the metric data chart, etc. - ![HertzBeat](/img/docs/start/ssl_3.png) + ![HertzBeat](home/static/img/docs/start/ssl_3.png) - ![HertzBeat](/img/docs/start/ssl_4.png) + ![HertzBeat](home/static/img/docs/start/ssl_4.png) 4. Set the threshold (triggered when the certificate expires) - > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule + > HertzBeat Page -> Alerting -> Threshold -> New Threshold -> ReadTime Threshold Rule > Configure the threshold, select the SSL certificate metric object, configure the alarm expression-triggered when the metric `expired` is `true`, that is, `equals(expired,"true")`, set the alarm level notification template information, etc. - ![HertzBeat](/img/docs/start/ssl_5.png) + ![HertzBeat](home/static/img/docs/start/ssl_5.png) > Threshold rule has others function you can try eg: associating thresholds with monitoring, trigger times so on. @@ -64,17 +64,17 @@ The production environment recommends a complete deployment method, refer [https > In the same way, switch coding threshold, add a new configuration threshold and configure an alarm expression - when the metric expires timestamp `end_timestamp`, the `now()` function is the current timestamp, if the configuration triggers an alarm one week in advance: `end_timestamp <= (now() + 604800000)` , where `604800000` is the 7-day total time difference in milliseconds. - ![HertzBeat](/img/docs/start/ssl_6.png) + ![HertzBeat](home/static/img/docs/start/ssl_6.png) > Finally, you can see the triggered alarm in the alarm center. - ![HertzBeat](/img/docs/start/ssl_7.png) + ![HertzBeat](home/static/img/docs/start/ssl_7.png) 6. Alarm notification (in time notification via Dingding WeChat Feishu, etc.) > HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Config the Feishu Receiver - ![HertzBeat](/img/docs/start/notice_receiver_1.png) + ![HertzBeat](home/static/img/docs/start/notice_receiver_1.png) For token configuration such as Feishu, please refer to the help document @@ -82,7 +82,7 @@ The production environment recommends a complete deployment method, refer [https > Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured - ![HertzBeat](/img/docs/start/notice_policy_1.png) + ![HertzBeat](home/static/img/docs/start/notice_policy_1.png) 7. OK When the threshold is triggered, we can receive the corresponding alarm message. If there is no notification, you can also view the alarm information in the alarm center. diff --git a/home/versioned_docs/version-1.8.0/start/usecase/tdengine-practice.md b/home/versioned_docs/version-1.8.0/start/usecase/tdengine-practice.md index 13831d1aa68..c58cf84c408 100644 --- a/home/versioned_docs/version-1.8.0/start/usecase/tdengine-practice.md +++ b/home/versioned_docs/version-1.8.0/start/usecase/tdengine-practice.md @@ -1,6 +1,6 @@ --- -id: tdengine-practice -title: TDengine Monitoring Practice +id: tdengine-practice +title: TDengine Monitoring Practice sidebar_label: TDengine Monitoring Practice --- @@ -40,7 +40,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Monitoring Center -> Add Monitoring -> Custom Monitoring -> TDengine-PromQL Task - ![HertzBeat](/img/docs/start/tdengine_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1.png) 2. Fill in key parameters @@ -52,15 +52,15 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > You can use tags to categorize tasks, such as adding business-related tags like `env=test`. - ![HertzBeat](/img/docs/start/tdengine_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_2.png) 3. View inspection indicator data > You can view task statuses in the monitoring list and view metric data charts and other information in the monitoring details. - ![HertzBeat](/img/docs/start/tdengine_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_3.png) - ![HertzBeat](/img/docs/start/tdengine_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_4.png) ## Monitor TDengine(Prometheus) @@ -68,7 +68,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Monitoring Center -> Add Monitoring -> AUTO -> Prometheus Task - ![HertzBeat](/img/docs/start/tdengine_1_1.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_1.png) 2. Fill in key parameters @@ -80,15 +80,15 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > You can use tags to categorize tasks, such as adding business-related tags like `env=test`. - ![HertzBeat](/img/docs/start/tdengine_1_2.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_2.png) 3. View inspection indicator data > You can view task statuses in the monitoring list and view metric data charts and other information in the monitoring details. - ![HertzBeat](/img/docs/start/tdengine_1_3.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_3.png) - ![HertzBeat](/img/docs/start/tdengine_1_4.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_4.png) ### Grafana visualization integration (optional) @@ -106,13 +106,13 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > For example: Select the Grafana data source `hertzbeat-victoria-metrics`, then click "Share" → "Export" → "Save to file" on the dashboard to download the template and upload it to HertzBeat monitoring. For reference, see: [taoskeeper-prometheus-dashboard](https://grafana.com/grafana/dashboards/15164-taoskeeper-prometheus-dashboard/) - ![HertzBeat](/img/docs/start/tdengine_1_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_5.png) 3. View Grafana charts > Go to the new AUTO monitoring page, click the Grafana icon button to view the Grafana chart. - ![HertzBeat](/img/docs/start/tdengine_1_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_1_6.png) ## Alarm and notification linkage @@ -120,7 +120,7 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > System Page -> Alerts -> Threshold Rules -> Add -> Add Threshold - ![HertzBeat](/img/docs/start/tdengine_5.png) + ![HertzBeat](home/static/img/docs/start/tdengine_5.png) > HertzBeat provides two types of threshold rule settings: **real-time calculation** and **scheduled cycle**. Here, we will use the **scheduled cycle** threshold rule as an example. > @@ -137,21 +137,21 @@ TDengine TSDB integrates multiple monitoring metric collection mechanisms and ag > > There are many combinations of threshold rules that can be set, and users can set more detailed alert rules according to their needs. - ![HertzBeat](/img/docs/start/tdengine_6.png) + ![HertzBeat](home/static/img/docs/start/tdengine_6.png) > Finally, you can see the triggered alerts in the Alert Center. - ![HertzBeat](/img/docs/start/tdengine_7.png) + ![HertzBeat](home/static/img/docs/start/tdengine_7.png) 3. Alert notification > System Page -> Message Notifications -> Notification Media -> Add New Recipient - ![HertzBeat](/img/docs/start/tdengine_8.png) + ![HertzBeat](home/static/img/docs/start/tdengine_8.png) > System Page -> Message Notifications -> Notification Policies -> Add Notification Policy -> Select recipients and enable notifications - ![HertzBeat](/img/docs/start/tdengine_9.png) + ![HertzBeat](home/static/img/docs/start/tdengine_9.png) 4. OK! When the threshold rule is triggered, we will receive the corresponding alert message. If no notification is configured, you can also view the alert information in the alert center. diff --git a/home/versioned_docs/version-1.8.0/template.md b/home/versioned_docs/version-1.8.0/template.md index b88ebcd9325..80ea874935a 100644 --- a/home/versioned_docs/version-1.8.0/template.md +++ b/home/versioned_docs/version-1.8.0/template.md @@ -1,6 +1,6 @@ --- -id: template -title: Monitoring Template Here +id: template +title: Monitoring Template Here sidebar_label: Monitoring Template --- @@ -11,11 +11,11 @@ sidebar_label: Monitoring Template Here is the architecture. -![HertzBeat](/img/docs/hertzbeat-arch.png) +![HertzBeat](home/static/img/docs/hertzbeat-arch.png) **We define all monitoring collection types (mysql, website, jvm, k8s) as yml templates, and users can import these templates into the hertzbeat system to support corresponding types of monitoring, which is very convenient!** -![HertzBeat](/img/docs/advanced/extend-point-1.png) +![HertzBeat](home/static/img/docs/advanced/extend-point-1.png) **Welcome everyone to contribute your customized general monitoring type YML template during use. The available templates are as follows:**