wehub/apache--hertzbeat
1
0
Fork 0
Code Issues Pull Requests Actions Deployments Models Agent Notes Packages Projects Releases Wiki Activity

chore: import upstream snapshot with attribution
MCP Bash Server CI / Test MCP Bash Server (dev) (push) Has been cancelled
Details
MCP Bash Server CI / Test MCP Bash Server (release) (push) Has been cancelled
Details

Browse Source
This commit is contained in:
wehub-resource-sync
2026-07-13 13:11:39 +08:00
commit c8cebdfeee
4654 changed files with 626756 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
home/docs/start/usecase/linux-os-practice.md
+94
View File
@@ -0,0 +1,94 @@
---
id: linux-os-practice
title: Linux Operating System Monitoring Practice
sidebar_label: Linux Operating System Monitoring Practice
---
This article describes how to use the HertzBeat monitoring system to collect and monitor general performance metrics for Linux operating systems, and send us alert messages when file system usage is too high.
## What's HertzBeat
Apache HertzBeat™ is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, port availability, database, operating system, threshold alarms, alarm notification (email, WeChat, DingTalk, Feishu).
github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)
## Install
1. The `docker` environment can be installed with just one command
```bash
docker run -d -p 1157:1157 -p 1158:1158 --name hertzbeat apache/hertzbeat
```
2. After the installation is successful, the browser can access `http://ip:1157` to start, the default account password is `admin/hertzbeat`.
:::note
The production environment recommends a complete deployment method, refer [Install HertzBeat via Docker Compose](https://hertzbeat.apache.org/docs/start/docker-compose-deploy)
:::
## Monitoring Linux Operating System
### 1. Click Add Linux Operating System Monitor
> HertzBeat Page -> Monitors -> New Monitor -> OS Monitor -> Add OS Linux
![HertzBeat](/img/docs/start/linux-os-practice-1.png)
### 2. Configure the monitoring parameters
- **Target Host**：The IPV4, IPV6, or domain name of the host being monitored. No protocol header (e.g., https://, http://).
- **Port**：The port provided by Linux SSH, default is 22.
- **Timeout**：Sets the connection timeout in milliseconds, default is 6000 ms.
- **Reuse Connection**: Sets whether SSH connections are reused, default is :false. If false, a new connection is created each time information is retrieved.
- **Username**: SSH connection username
- **Password**: SSH connection password, optional.
> For more parameters and advanced settings, please refer to the help documentation: [Monitoring：Linux operating system monitoring](https://hertzbeat.apache.org/docs/help/linux)
Tasks can be managed using label classification, such as adding bind labels like `OS=Linux`.
![HertzBeat](/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](/img/docs/start/linux-os-practice-4.png)
### 4. Set the threshold
Here, we set a threshold rule to trigger an alert when **the usage rate of a certain directory in the file system is too high**.
> HertzBeat Page -> Alerting -> Threshold -> New Threshold -> RealTime Threshold Rule
>
> 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)
> 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)
### 5. Alarm notification
> HertzBeat Page -> Notification -> Notice Receiver -> New Receiver -> Configure the Email Receiver
![HertzBeat](/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)
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
The practice of monitoring linux operating system is here. Of course, for HertzBeat, this function is just the tip of the iceberg. If you think HertzBeat is a good open source project, please give us a Star on GitHub, thanks for your support.
**Github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)**
home/docs/start/usecase/springboot-auto-practice.md
+245
View File
@@ -0,0 +1,245 @@
---
id: springboot-auto-practice
title: SpringBoot Web Application Monitoring Practice
sidebar_label: SpringBoot Web Application Monitoring Practice
---
:::tip
In the cloud-native era, monitoring and visualization of SpringBoot applications have become core components of O&M (Operations & Maintenance) systems. Real-time monitoring of application performance is crucial for ensuring system stability.
:::
This article introduces an integrated solution using the HertzBeat monitoring system, covering metric collection, visualization, and alarm notifications. It demonstrates the complete operational procedure and monitoring practices.
## What is HertzBeat
Apache HertzBeat is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, PING connectivity, port availability, database, operating system, middleware, API monitoring, threshold alarms, alarm notification (email, WeChat, Ding Ding Feishu).
**github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)**
## Install HertzBeat
> For production environments, it is recommended to deploy HertzBeat using **PostgreSQL** + **VictoriaMetrics**.
1. Deploy HertzBeat
> Download the installation package
>
> Download the `apache-hertzbeat-xxx-incubating-bin.tar.gz` installation package corresponding to your system environment from the [Download Page](https://hertzbeat.apache.org/docs/download). Extract the package to a host directory, e.g., `/opt/hertzbeat`.
```sh
tar zxvf apache-hertzbeat-xxx-incubating-bin.tar.gz
```
2. Quick Install PostgreSQL + VictoriaMetrics Services
> Install PostgreSQL via Docker
```sh
docker run -d --name postgresql -p 5432:5432 -v "$PWD/postgresql:/var/lib/postgresql/data" -e POSTGRES_USER=root -e POSTGRES_PASSWORD=123456 -e TZ=Asia/Shanghai postgres:15
```
> Install VictoriaMetrics via Docker
```sh
docker run -d -p 8428:8428 -v "$PWD/victoria-metrics-data:/victoria-metrics-data" --name victoria-metrics victoriametrics/victoria-metrics:v1.95.1
```
3. Modify HertzBeat's Configuration File
> Switch the metadata storage data source
>
> Modify the `hertzbeat/config/application.yml` configuration file to use the PostgreSQL service.
:::note
For PostgreSQL configuration details, please refer to the documentation: [Meta Store PostgreSQL (Recommended)](https://hertzbeat.apache.org/docs/start/postgresql-change)
:::
> Configure the time-series database for metric storage
>
> Modify the `hertzbeat/config/application.yml` configuration file to enable the VictoriaMetrics service for storing metrics.
:::note
For VictoriaMetrics configuration details, please refer to the documentation: [Metrics Store VictoriaMetrics (Recommended)](https://hertzbeat.apache.org/docs/start/victoria-metrics-init)
:::
4. Start HertzBeat
> Use the `startup.sh` script located in the `bin` directory of the extracted installation folder. For Windows environments, use `startup.bat`.
>
> After successful startup, access `http://localhost:1157` in your browser to begin. The default username and password are `admin/hertzbeat`.
```sh
./startup.sh
```
## SpringBoot Application Configuration
1. Enable Actuator Configuration
> Add the following dependencies to project's `pom.xml`:
```xml
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>
<dependency>
<groupId>io.micrometer</groupId>
<artifactId>micrometer-registry-prometheus</artifactId>
</dependency>
```
> Configure `application.yml` to expose endpoints:
```yml
management:
endpoints:
web:
exposure:
include: '*'
enabled-by-default: true
metrics:
export:
prometheus:
enabled: true
```
> *Note: If your project also introduces authentication related dependencies, such as springboot security, the interfaces exposed by SpringBoot Actor may be intercepted. In this case, you need to manually release these interfaces. Taking springboot security as an example, you should add the following code to the Security Configuration class:*
```java
public class SecurityConfig extends WebSecurityConfigurerAdapter{
@Override
protected void configure(HttpSecurity httpSecurity) throws Exception{
httpSecurity
// Configure the interfaces to be opened
.antMatchers("/actuator/**").permitAll()
.antMatchers("/metrics/**").permitAll()
.antMatchers("/trace").permitAll()
.antMatchers("/heapdump").permitAll()
// ...
}
}
```
2. Verify Endpoints
> After starting SpringBoot application, request the following URL:
>
> * `http://<your-host>:<port>`/actuator`: Verify the enabled endpoints.
> * `http://<your-host>:<port>`/actuator/prometheus`: Should return metric data in Prometheus format.
## Monitor SpringBoot Application
1. Add AUTO Monitor
> HertzBeat Page -> Monitors -> New Monitor -> AUTO -> Prometheus Task
![HertzBeat](/img/docs/start/springboot-auto-practice-1.png)
2. Fill in Key Parameters
> **Target Host**: The server address of the SpringBoot application (without the protocol prefix like `http://` or `https://`).
>
> **Port**: The application service port (e.g., `8080`).
>
> **Endpoint Path**: `/actuator/prometheus`
>
> Tasks can be managed using label classification, such as adding Bind Labels like `env=test`.
![HertzBeat](/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](/img/docs/start/springboot-auto-practice-4.png)
## Grafana Visualization Integration (Optional)
1. Grafana Dashboard Configuration
> Enable Grafana's embedding feature and enable anonymous access.
:::note
For complete configuration details, please refer to the documentation: [Grafana Historical Charts](https://hertzbeat.apache.org/docs/help/grafana_dashboard)
:::
2. Embed Grafana Dashboard in HertzBeat Monitor
> After configuring and enabling Grafana, restart the HertzBeat service. Then, in the newly added AUTO monitor settings, enable Grafana Templates and upload a Grafana dashboard template.
>
> 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)
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)
## Alarm and Notification Interlinkage
1. HertzBeat Alarm Configuration
> HertzBeat Page -> Alerting -> Threshold -> New -> New Threshold Rule
![HertzBeat](/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.
>
> * **Rule Name**: Name of the threshold rule.
> * **Threshold Rule**: Enter the rule for monitoring the metric (supports `PromQL`).
> * **Execution Period**: The time interval for periodically executing the threshold calculation.
> * **Alarm Severity**: The alarm level that triggers the threshold, from low to high: Warning，Critical，Emergency.
> * **Trigger Times**: Set how many times the threshold is triggered before sending an alarm.
> * **Alarm Content**: Enter the content of the monitoring alarm(supports variables).
2. Set Threshold Rule
> For example, to monitor the CPU usage of the SpringBoot application, add a threshold rule like: `system_cpu_usage{job="Jolly_Vulture_43vT"}` > 0.01`
>
>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)
> Finally, you can see the triggered alarm in the alarm center.
![HertzBeat](/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 Page -> Notification -> Notice Policy -> New Notice Policy -> Select Recipient(s) and Enable Notification
![HertzBeat](/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.
## Quick Summary
This article demonstrates how users can build a complete monitoring system within minutes using simple configurations, highlighting several advantages of HertzBeat:
* Monitors SpringBoot Actuator endpoints without needing to deploy Exporter or Agent, supporting custom metric collection and alert rules.
* Lightweight: Compared to the traditional Prometheus + AlertManager combination, HertzBeat simplifies the deployment and maintenance process.
* Seamless Integration with Grafana: HertzBeat pushes collected time-series data to Grafana in real-time for building visualization dashboards.
* Integrated Monitoring + Alerting + Notification: Combines full protocol coverage, real-time/periodic threshold detection, and multi-channel notifications (DingTalk/Feishu/Webhook, etc.).
------
## Wrapping Up
That concludes this practical guide on monitoring SpringBoot applications with HertzBeat. Of course, this functionality is just the tip of the iceberg for HertzBeat. If you think hertzbeat is a good open source project, please give it a **Star** on GitHub and Gitee! Your Star motivate our continuous improvement! Feel free to light up the little star ✨
**Making monitoring simpler, looking forward to building the ecosystem together!** 💝
**GitHub: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)**
**Gitee: [https://gitee.com/hertzbeat/hertzbeat](https://gitee.com/hertzbeat/hertzbeat)**
home/docs/start/usecase/sslcert-practice.md
+95
View File
@@ -0,0 +1,95 @@
---
id: ssl-cert-practice
title: SSL Certificate Monitoring Practice
sidebar_label: SSL Certificate Monitoring Practice
---
:::tip
Most websites now support HTTPS by default. The certificate we apply for is usually 3 months or 1 year. It is easy to expire the SSL certificate over time, but we did not find it the first time, or did not update the certificate in time before it expired.
:::
This article introduces how to use the hertzbeat monitoring tool to detect the validity period of our website's SSL certificate, and send us a warning message when the certificate expires or a few days before the certificate expires.
## What is HertzBeat
Apache HertzBeat™ is a real-time monitoring tool with powerful custom monitoring capabilities without Agent. Website monitoring, PING connectivity, port availability, database, operating system, middleware, API monitoring, threshold alarms, alarm notification (email, WeChat, Ding Ding Feishu).
github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)
## Install HertzBeat
1. The `docker` environment can be installed with just one command
`docker run -d -p 1157:1157 -p 1158:1158 --name hertzbeat apache/hertzbeat`
2. After the installation is successful, the browser can access `localhost:1157` to start, the default account password is `admin/hertzbeat`
:::note
The production environment recommends a complete deployment method, refer [https://hertzbeat.apache.org/docs/start/docker-compose-deploy](https://hertzbeat.apache.org/docs/start/docker-compose-deploy)
:::
## Monitoring SSL Certificates
1. Click Add SSL Certificate Monitor
> HertzBeat Page -> Monitors -> New Monitor -> Service Monitor -> Add SSL Certificate
![HertzBeat](/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)
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](/img/docs/start/ssl_4.png)
4. Set the threshold (triggered when the certificate expires)
> 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)
> Threshold rule has others function you can try eg: associating thresholds with monitoring, trigger times so on.
5. Set the threshold (triggered one week before the certificate expires)
> 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)
> Finally, you can see the triggered alarm in the alarm center.
![HertzBeat](/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)
For token configuration such as Feishu, please refer to the help document
[https://hertzbeat.apache.org/docs/help/alert_feishu](https://hertzbeat.apache.org/docs/help/alert_feishu)
> Notification -> Notice Policy -> New Notice Policy -> Enable Notification for the Recipient Just Configured
![HertzBeat](/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.
----
## The End
The practice of monitoring SSL certificates is here. Of course, for hertzbeat, this function is just the tip of the iceberg. If you think hertzbeat is a good open source project, please give us a Gitee star on GitHub, thank you very much. Thank you for your support. Refill!
**github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)**
home/docs/start/usecase/tdengine-practice.md
+166
View File
@@ -0,0 +1,166 @@
---
id: tdengine-practice
title: TDengine Monitoring Practice
sidebar_label: TDengine Monitoring Practice
---
:::tip
TDengine TSDB is an open-source, high-performance, cloud-native time series database (TSDB) optimized for IoT, vehicle networking, industrial Internet, finance, IT operations, and other scenarios. It also comes with built-in caching, streaming computing, data subscription, and other system functions that greatly reduce system design complexity and lower R&D and operational costs, making it an extremely simple time series data processing platform.
:::
This article introduces how to use the HertzBeat monitoring system to collect and monitor TDengine general performance indicators.
## What is HertzBeat?
Apache HertzBeat™ is a real-time monitoring tool with powerful customization capabilities that does not require an agent. It monitors websites, PING connectivity, port availability, databases, operating systems, middleware, APIs, threshold alerts, and alert notifications (email, WeChat, DingTalk, Feishu).
> **github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)**
## Install HertzBeat
1. The `docker` environment can be installed with just one command.
`docker run -d -p 1157:1157 -p 1158:1158 --name hertzbeat apache/hertzbeat`
2. Once installed, you can start by accessing `localhost:1157` in your browser. The default username and password are `admin/hertzbeat`.
:::note
Recommended deployment method for production environments, reference: [https://hertzbeat.apache.org/docs/start/docker-compose-deploy](https://hertzbeat.apache.org/docs/start/docker-compose-deploy)
:::
## Enable TDengine monitoring
:::tip
TDengine TSDB integrates multiple monitoring metric collection mechanisms and aggregates them through taosKeeper. taosKeeper is a monitoring metric export tool for TDengine TSDB version 3.0. With just a few simple configurations, you can obtain the runtime status of TDengine TSDB. For reference: [https://docs.taosdata.com/reference/components/taoskeeper/](https://docs.taosdata.com/reference/components/taoskeeper/)
:::
## Monitor TDengine(PromQL)
1. Added TDengine-PromQL monitoring
> System Page -> Monitoring Center -> Add Monitoring -> Custom Monitoring -> TDengine-PromQL Task
![HertzBeat](/img/docs/start/tdengine_1.png)
2. Fill in key parameters
> **Target Host**: Prometheus application server address (without protocol header, e.g., https://, http://)
>
> **Port**: Prometheus API port, default value: 9090
>
> **Endpoint path**: The URL for Prometheus to query PromQL. Default value: `/api/v1/query`
>
> You can use tags to categorize tasks, such as adding business-related tags like `env=test`.
![HertzBeat](/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](/img/docs/start/tdengine_4.png)
## Monitor TDengine(Prometheus)
1. New AUTO monitoring
> System Page -> Monitoring Center -> Add Monitoring -> AUTO -> Prometheus Task
![HertzBeat](/img/docs/start/tdengine_1_1.png)
2. Fill in key parameters
> **Target Host** taosKeeper service address (without protocol header, e.g., https://, http://)
>
> **Port**: taosKeeper service port (e.g., 6043)
>
> **Endpoint path**: `/metrics`
>
> You can use tags to categorize tasks, such as adding business-related tags like `env=test`.
![HertzBeat](/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](/img/docs/start/tdengine_1_4.png)
### Grafana visualization integration (optional)
1. Grafana chart configuration
> You need to enable Grafana's embeddable feature and allow anonymous access.
:::note
For complete configuration, please refer to the documentation: [Grafana Historical Charts](https://hertzbeat.apache.org/zh-cn/docs/help/grafana_dashboard)
:::
2. Embedding Grafana dashboards in HertzBeat monitoring
> After enabling Grafana, restart the HertzBeat service, enable it in the newly added AUTO monitoring, and upload the Grafana template.
>
> 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)
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)
## Alarm and notification linkage
1. HertzBeat Alert Configuration
> System Page -> Alerts -> Threshold Rules -> Add -> Add Threshold
![HertzBeat](/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.
>
> * **Threshold Name**: Threshold rule name
> * **Threshold rules**: Fill in the rules for monitoring indicators (supports `PromQL`).
> * **Execution cycle**: The time interval for calculating the periodic execution threshold.
> * **Alarm Level**: The alarm level triggered by the threshold, from low to high: Warning, Critical, Emergency.
> * **Trigger count**: Set the threshold number of times the trigger must occur before an alert is sent.
> * **Alarm content**: Fill in the content of the monitoring alarm (supports filling in variables)
2. Set threshold rules
> For example, to monitor the CPU percentage used by the Dnode node system, add a threshold rule: `taos_dnodes_info_cpu_system_value > 20`
>
> 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)
> Finally, you can see the triggered alerts in the Alert Center.
![HertzBeat](/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)
> System Page -> Message Notifications -> Notification Policies -> Add Notification Policy -> Select recipients and enable notifications
![HertzBeat](/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.
## Summary
That concludes our practical guide to monitoring TDengine applications. Of course, this feature is just the tip of the iceberg for HertzBeat. If you like this open-source project, please give it a star on GitHub or Gitee. Your stars are what motivate us to keep improving! Please light up the little stars ✨
**Making monitoring simpler, we look forward to building an ecosystem with you!** 💝
**github: [https://github.com/apache/hertzbeat](https://github.com/apache/hertzbeat)**
**gitee: [https://gitee.com/hertzbeat/hertzbeat](https://gitee.com/hertzbeat/hertzbeat)**