Self-host HertzBeat with Levelrail
A real time monitoring system with agentless collection, alerts and a web console, on the embedded database with a data volume. Change the default login after the first sign in.
- Authorapache
- LicenceApache-2.0
- Memory1 GiB
- Services1
How to self-host HertzBeat
-
Pull the images
One image is pulled on your server.
Show images
apache/hertzbeat:1.7.3
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 1157.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Sign in as admin with the password hertzbeat and change it right away, because it is public knowledge.
HertzBeat requirements
- Memory
- About 1 GiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 1157
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then HertzBeat. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the HertzBeat docs page.
Deploy HertzBeat your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy HertzBeat from the CLI
levelrail-cli templates deploy hertzbeat --name my-hertzbeat Deploy HertzBeat with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/hertzbeat/deploy HertzBeat configuration
HertzBeat services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| hertzbeat | apache/hertzbeat:1.7.3 | 1157 | hertzbeat_data -> /opt/hertzbeat/data |
HertzBeat environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 1157
- Volumes
- 1 named mount: hertzbeat_data -> /opt/hertzbeat/data
HertzBeat FAQ
How much memory does HertzBeat need?
The catalog lists about 1 GiB of memory for HertzBeat.
Does HertzBeat run on arm64?
For HertzBeat, arm64 support is not confirmed; amd64 is unknown.
What licence is HertzBeat under?
HertzBeat is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does HertzBeat need configuration before it starts?
No. The template fills in its own defaults.
Which ports does HertzBeat use?
HertzBeat listens on port 1157 inside the stack.
Where does HertzBeat keep its data?
In a named volume: hertzbeat_data mounted at /opt/hertzbeat/data.
Can I deploy HertzBeat on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for HertzBeat, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image apache/hertzbeat:1.7.3 is what you deploy there.