- Heartbeat Reference: other versions:
- Overview
- Contributing to Beats
- Getting Started With Heartbeat
- Setting up and running Heartbeat
- Configuring Heartbeat
- Set up Heartbeat monitors
- Specify general settings
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and Enhance the exported data
- Parse logs by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Set up logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- heartbeat.reference.yml
- Exported Fields
- Securing Heartbeat
- Troubleshooting
WARNING: Version 6.0 of Heartbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Heartbeat and X-Pack Security
editHeartbeat and X-Pack Security
editIf you want Heartbeat to connect to a cluster that has X-Pack Security enabled, there are extra configuration steps.
To send data to a secured cluster through the elasticsearch output,
Heartbeat needs to authenticate as a user who can manage index templates,
monitor the cluster, create indices, and read, and write to the indices
it creates. See Configuring Authentication Credentials for Heartbeat.
If encryption is enabled on the cluster, you also need to enable HTTPS in the Heartbeat configuration. See Configuring Heartbeat to use Encrypted Connections.
In addition to configuring authentication credentials for the Heartbeat itself, you need to grant authorized users permission to access the indices it creates. See Granting Users Access to Heartbeat Indices.
For more information about X-Pack Security, see Securing Elasticsearch and Kibana.