apache

hertzbeat: Monitor Systems, Metrics, Logs, and Alerts

Apache HertzBeat is a self-hosted observability platform for collecting metrics and logs, managing alerts, and publishing service status pages. It suits teams seeking agentless monitoring with configurable collection and optional collector clusters.

View on GitHub Compare
Stars
7.4k
Forks
1.3k
Stars, last 30 days
+40

Our take

Health score

66/100

How it is scored
Activity
67
Community
87
Issues
58
Pull requests
53

+40 stars in the last 30 days

  • Merges more pull requests than 92% of the projects we track
  • More contributors than 78% of the projects we track
  • Slower to merge pull requests than 86% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

7,470

Forks

1,368

Change since Nov 15, 2026: +1 stars·0 forks

Overview

Apache HertzBeat brings metrics collection, log intake, alert management, and status pages into one observability platform. It is designed to help teams monitor infrastructure and services without installing an agent on every target, while also supporting centralized alert processing and notifications.

It may suit teams that want configurable monitoring across varied systems, or a self-hosted alternative to assembling separate tools for collection, alerting, and service status. Collection can be extended through YAML templates, and collector clusters support scaling and monitoring across isolated networks.

Key Features

  • Collect metrics from applications, databases, operating systems, middleware, networks, and other supported targets without requiring an agent on each one.
  • Configure collection for supported protocols such as HTTP, JMX, SSH, SNMP, JDBC, and Prometheus through YAML templates.
  • Receive logs from multiple sources using OTLP.
  • Process alerts with threshold rules, grouping, silencing, and suppression.
  • Send notifications through channels including email, Discord, Slack, Telegram, and webhooks.
  • Scale collection with multiple collectors and support cloud-edge or isolated-network monitoring.
  • Build status pages to share service availability with users.
  • Use built-in MCP Server capabilities and AI-oriented interactions described by the project.

Use Cases

  • Infrastructure teams can monitor servers and networked systems without deploying an agent on each target.
  • Database and platform operators can configure metrics collection for databases, caches, middleware, and applications in one system.
  • On-call teams can consolidate alert sources, apply grouping and suppression, and route notifications to their chosen channels.
  • Service owners can publish status pages to communicate current service health to users.
  • Organizations with separated or edge environments can distribute collectors while managing monitoring centrally.

Getting Started

Start the server with Docker:

docker run -d -p 1157:1157 -p 1158:1158 --name hertzbeat apache/hertzbeat

Open http://localhost:1157. The README lists the default login and additional deployment options. See the repository README for setup details.

Alternatives

  • Prometheus: Prometheus focuses on time-series metrics, PromQL, and rule-based alerts, while HertzBeat also offers configurable agentless collection, logs, and status pages.
ProjectLanguageLicenseStarsStatus
hertzbeatJavaApache-2.07.4kNot checked yet
prometheus/prometheusGoApache-2.066.3kActive

Considerations

  • The Docker command starts the main server; deploying separate collectors is optional but requires configuring their identity and connection to the manager.
  • Source-based development requires Java 25, Maven 3 or later, and Node.js with pnpm for the web application.
  • Collection depends on the supported protocols, integrations, and configured templates. Some database monitoring setups may need external JDBC drivers or the JVM collector package.
  • The project combines several observability functions, so teams should review its deployment documentation and storage choices before operating it at scale.

Found this useful?

Share it with someone who would like hertzbeat.

Comparisons