apache/hertzbeat

★ 7,228JavaAudience · ops devopsComplexity · 4/5LicenseSetup · moderate

Mindmap

mindmap
  root((HertzBeat))
    What it monitors
      Websites
      Databases
      Servers
    Protocols used
      HTTP
      SSH
      JDBC and SNMP
    Alert channels
      Email
      Slack Telegram
      Webhooks
    Key features
      No agents needed
      Status page
      Log collection

mindmap root((HertzBeat)) What it monitors Websites Databases Servers Protocols used HTTP SSH JDBC and SNMP Alert channels Email Slack Telegram Webhooks Key features No agents needed Status page Log collection

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Monitor website uptime and receive instant Slack or email alerts when a site goes down.

USE CASE 2

Track database performance metrics without installing any agent software on the database server.

USE CASE 3

Publish a public-facing status page showing whether your services are up so customers can check during outages.

Tech stack

JavaHTTPSSHJDBCSNMPOTLP

Getting it running

Difficulty · moderate Time to first run · 1h+

Requires running the HertzBeat service (Docker or JAR) and configuring monitoring templates for each target type.

Open source under Apache 2.0, use freely for any purpose including commercial products.

In plain English

Apache HertzBeat is an open-source monitoring and alerting platform that watches over your websites, databases, servers, and applications in real time, then notifies you when something goes wrong. It rolls four functions into one place: collecting data from your systems, analyzing that data, triggering alerts when thresholds are crossed, and sending those alerts to wherever your team pays attention, such as email, Slack, Telegram, DingTalk, WeChat, or a plain webhook. One of its key selling points is that you do not need to install any extra software on the machines you want to monitor. HertzBeat reaches out and collects what it needs over standard protocols like HTTP, SSH, JDBC for databases, and SNMP for network devices. Each type of thing you want to monitor is described in a simple configuration file, so adding a new kind of target, say a new database type or a cloud service, means writing or importing a short template rather than deploying more software. HertzBeat also handles logs alongside metrics, pulling them in through a standard protocol called OTLP so everything lands in one dashboard. It includes a status page builder, which lets you publish a public-facing page showing whether your services are up, useful for communicating with customers during outages. The project recently added AI-powered features under the label HertzBeat AI, including a built-in MCP Server capability, though the README does not detail exactly what these AI features do at the user level. The system is built to scale horizontally, meaning you can add more collector nodes as your monitoring needs grow. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1

I want to monitor my PostgreSQL database with HertzBeat. Show me how to set up JDBC monitoring without installing anything on the database server.

Prompt 2

How do I configure HertzBeat to send alerts to a Slack channel when a monitored service goes down? Walk me through the alert rule and notification setup.

Prompt 3

I want to add a custom monitoring template to HertzBeat for a REST API endpoint. Show me the YAML configuration file format.

Prompt 4

Set up a HertzBeat status page that shows green/red for three of my services, and explain how to embed it on my website.

Open on GitHub → Explain another repo

← apache on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.