- 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
Configure Heartbeat to use X-Pack security
editConfigure Heartbeat to use X-Pack security
editIf you want Heartbeat to connect to a cluster that has X-Pack security enabled, there are extra configuration steps:
-
Grant users access to secured resources.
You can use role-based access control to grant Heartbeat users access to secured resources.
-
Configure authentication credentials.
To interact with a secured cluster, Heartbeat must either provide basic authentication credentials or present a client certificate.
-
Configure Heartbeat to use encrypted connections.
If encryption is enabled on the cluster, you need to enable HTTPS in the Heartbeat configuration.
-
Set the password for the built-in monitoring user.
Heartbeat uses the
beats_systemuser to send monitoring data to Elasticsearch. If you plan to monitor Heartbeat in Kibana and have not yet set up the password, set it up now.
For more information about X-Pack security, see Securing the Elastic Stack.