- Heartbeat Reference: other versions:
- Overview
- Getting Started With Heartbeat
- Setting up and running Heartbeat
- Configuring Heartbeat
- Set up monitors
- Specify general settings
- Configure the internal queue
- Configure the output
- Configure index lifecycle management
- Specify SSL settings
- Filter and Enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Drop events
- Drop fields from events
- Keep fields from events
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure the Kibana endpoint
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- heartbeat.reference.yml
- Exported fields
- Monitoring Heartbeat
- Securing Heartbeat
- Troubleshooting
- Contributing to Beats
Heartbeat and systemd
editHeartbeat and systemd
editThe DEB and RPM packages include a service unit for Linux systems with systemd. On these systems, you can manage Heartbeat by using the usual systemd commands.
Start and stop Heartbeat
editUse systemctl to start or stop Heartbeat:
systemctl start heartbeat
systemctl stop heartbeat
By default, the Heartbeat service starts automatically when the system boots. To enable or disable auto start use:
systemctl enable heartbeat
systemctl disable heartbeat
Heartbeat status and logs
editTo get the service status, use systemctl:
systemctl status heartbeat
Logs are stored by default in journald. To view the Logs, use journalctl:
journalctl -u heartbeat.service
The unit file included in the packages sets the -e flag by default.
This flag makes Heartbeat log to stderr and disables other log outputs.
Systemd stores all output sent to stderr in journald.
Customize systemd unit for Heartbeat
editThe systemd service unit file includes environment variables that you can override to change the default options.
| Variable | Description | Default value |
|---|---|---|
BEAT_LOG_OPTS |
Log options |
|
BEAT_CONFIG_OPTS |
Flags for configuration file path |
|
BEAT_PATH_OPTS |
Other paths |
|
To override these variables, create a drop-in unit file in the
/etc/systemd/system/heartbeat.service.d directory.
For example a file with the following content placed in
/etc/systemd/system/heartbeat.service.d/debug.conf
would override BEAT_LOG_OPTS to enable debug for Elasticsearch output.
[Service] Environment="BEAT_LOG_OPTS=-e -d elasticsearch"
To change the logging output from the Heartbeat configuration file, empty the environment variable. For example:
[Service] Environment="BEAT_LOG_OPTS="
To apply your changes, reload the systemd configuration and restart the service:
systemctl daemon-reload systemctl restart heartbeat
It is recommended that you use a configuration management tool to
include drop-in unit files. If you need to add a drop-in manually, use
systemctl edit heartbeat.service.