What it does
Apache HertzBeat is a self-hosted monitoring system that combines metrics collection, alert handling, notifications, and OTLP log ingestion in one web-managed product. It connects to targets through protocols such as HTTP, SNMP, JMX, SSH, JDBC, and Prometheus instead of requiring an agent on each monitored host. Built-in monitoring templates cover infrastructure and common services, while custom YAML templates let teams define additional collection. It is aimed at operators who want an adaptable monitoring control plane and can provide network access and credentials for the systems it polls.
Add a target through a monitoring template
The project documents a Docker-based local deployment, followed by adding a monitor in the web interface. Choose a built-in type for a service such as a database, Linux host, web endpoint, or network device, then provide the target address, port, and any required credentials. HertzBeat pulls measurements using the selected protocol; it can also consume Prometheus-compatible metrics. Custom monitor types are defined with YAML templates that describe protocol settings and how returned values become metrics.
Route alerts from the same console
Threshold rules can use current values or scheduled expressions. The alert workflow includes grouping, silence, and suppression, with notification destinations such as email, Slack, Discord, Telegram, and webhooks. Separate collector nodes can be added for larger installations or isolated networks, while OTLP can bring log data into the platform. This makes HertzBeat a collection-and-alerting system, not an automatic repair tool.
The agentless design avoids installing a separate exporter on each target, but the monitoring server still needs the right network path and credentials to query those targets. One material storage detail is easy to miss: the documentation says historical metric charts need an external time-series database for full functionality. Plan that dependency before treating a basic Docker start as a complete production deployment. The workflow here is documentation-based; no HertzBeat instance or target was configured.
Strengths
- Uses common protocols including HTTP, SNMP, JMX, SSH, JDBC, and Prometheus for agentless collection.
- Combines collection, threshold alerts, alert grouping or silence, and multi-channel notifications in one product.
- Provides built-in monitoring templates and lets users define additional collection through YAML templates in the web interface.
Watch out for
- Agentless polling still requires network reachability and suitable credentials for monitored systems.
- The documentation says an external time-series database is needed for full historical metric-chart functionality.
- Custom monitoring depends on understanding the supported protocol and template configuration.
Best for
- Platform teams that want one self-hosted console for infrastructure and service metrics without installing an agent on every target.
- Operators who need editable monitoring templates and built-in threshold notifications across mixed environments.
Sources
- Apache HertzBeat - Agentless Monitoring System (Oct 26, 2026)
- Apache HertzBeat - Open Source Real-Time Monitoring System (Oct 26, 2026)
- GitHub - apache/hertzbeat: An open source real-time observability system (Oct 26, 2026)