WARNING: Version 6.2 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.
X-Pack monitoring for Heartbeat requires Elasticsearch 6.2 or later.
To configure Heartbeat to collect and send monitoring metrics:
Create a user that has appropriate authority to send system-level monitoring
data to Elasticsearch. For example, you can use the built-in
logstash_systemuser or assign the built-in
logstash_systemrole to another user. For more information, see Setting Up User Authentication and Built-in Roles.
xpack.monitoringsettings in the Heartbeat configuration file. If you configured Elasticsearch output, specify the following minimal configuration:
If you configured a different output, such as Logstash, you must specify additional configuration options. For example:
xpack.monitoring: enabled: true elasticsearch: hosts: ["https://example.com:9200", "https://example2.com:9200"] username: elastic password: changeme
Currently you must send monitoring data to the same cluster as all other events. If you configured Elasticsearch output, do not specify additional hosts in the monitoring configuration.
- Configure monitoring in Kibana.
To verify your monitoring configuration, point your web browser at your Kibana
host, and select Monitoring from the side navigation. Metrics reported from
Heartbeat should be visible in the Beats section. When X-Pack Security is enabled,
to view the monitoring dashboards you must log in to Kibana as a user who has the