- 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
- Set up index lifecycle management
- Specify SSL settings
- Filter and Enhance the exported data
- Parse data by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- 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 features that require authorization
editHeartbeat features that require authorization
editAfter securing Heartbeat, make sure your users have the roles (or associated privileges) required to use these Heartbeat features. Note that some of the roles shown here are built-in, and some are user-defined.
Feature | Role |
---|---|
Send data to a secured cluster |
|
Load index templates |
|
Load Heartbeat dashboards into Kibana |
|
Load machine learning jobs |
|
Read indices created by Heartbeat |
|
View Heartbeat dashboards in Kibana |
|
Load index lifecycle policies and use index lifecycle management |
|
To create the user-defined roles shown here, see Configure authentication credentials and Grant users access to Heartbeat indices. You may want to define additional roles to provide more restrictive access.