# Self-host HertzBeat

> 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.

- Page: https://levelrail.com/templates/hertzbeat/
- JSON: https://levelrail.com/templates/hertzbeat.json
- Category: Monitoring
- Licence: Apache-2.0 (Permissive license)
- Source: https://github.com/apache/hertzbeat
- Upstream docs: https://hertzbeat.apache.org/docs/

## Requirements
- Memory: about 1 GiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 1.7.3

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| hertzbeat | apache/hertzbeat | 1.7.3 | 1157 | hertzbeat_data -> /opt/hertzbeat/data |

## Deploy

### CLI

```bash
levelrail-cli templates deploy hertzbeat --name my-hertzbeat
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/hertzbeat/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## First run
1. Sign in as admin with the password hertzbeat and change it right away, because it is public knowledge.

## Questions

### 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.

Self-host HertzBeat, HertzBeat docker compose file, deploy HertzBeat on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
