WARNING: Version 6.2 of Auditbeat 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.

« Kubernetes fields Monitoring configuration options »
Elastic Docs ›Auditbeat Reference [6.2]

Monitoring Auditbeat

edit

Monitoring Auditbeat

edit

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

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

To configure Auditbeat 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 logstash_system user or assign the built-in logstash_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 Auditbeat 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: 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.

  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 Auditbeat 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.
« Kubernetes fields Monitoring configuration options »