141b38a083
The built-in 'remote_monitoring_user' has full permissions on monitoring indices, which is more than Metricbeat needs to collect metrics from remote components. |
||
|---|---|---|
| .. | ||
| config | ||
| .dockerignore | ||
| Dockerfile | ||
| README.md | ||
| heartbeat-compose.yml | ||
README.md
Heartbeat
Heartbeat is a lightweight daemon that periodically checks the status of your services and determines whether they are available.
Usage
This extension requires the beats_system user to be created and initialized with a password. In case you haven't
done that during the initial startup of the stack, please refer to How to re-execute the setup to run the setup
container again and initialize this user.
To include Heartbeat in the stack, run Docker Compose from the root of the repository with an additional command line
argument referencing the heartbeat-compose.yml file:
$ docker-compose -f docker-compose.yml -f extensions/heartbeat/heartbeat-compose.yml up
Configuring Heartbeat
The Heartbeat configuration is stored in config/heartbeat.yml. You can modify this file
with the help of the Configuration reference.
Any change to the Heartbeat configuration requires a restart of the Heartbeat container:
$ docker-compose -f docker-compose.yml -f extensions/heartbeat/heartbeat-compose.yml restart heartbeat
Please refer to the following documentation page for more details about how to configure Heartbeat inside a Docker container: Run Heartbeat on Docker.