This functionality is in beta and is subject to change. The design and code is considered to be less mature than official GA features. Elastic will take a best effort approach to fix any issues, but beta features are not subject to the support SLA of official GA features.
« TLS encryption layer fields Monitoring configuration options »
Elastic Docs ›Heartbeat Reference [6.3]

Monitoring Heartbeat

edit

Monitoring Heartbeat

edit

X-Pack monitoring for Heartbeat requires Elasticsearch 6.2 or later.

X-Pack monitoring enables you to easily monitor Heartbeat from Kibana. For more information, see Monitoring the Elastic Stack and Beats Monitoring Metrics.

To configure Heartbeat to collect and send monitoring metrics:

  1. Create a user that has appropriate authority to send system-level monitoring data to Elasticsearch. For example, you can use the built-in beats_system user or assign the built-in beats_system role to another user. For more information, see Setting Up User Authentication and Built-in Roles.

  2. Add the xpack.monitoring settings in the Heartbeat configuration file. If you configured Elasticsearch output, specify the following minimal configuration:

    xpack.monitoring.enabled: true

    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: beats_system
    password: beatspassword

    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.

  3. Configure monitoring in Kibana.
  4. 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 kibana_user and monitoring_user roles.
« TLS encryption layer fields Monitoring configuration options »