Use internal collectors to send Beats monitoring data directly to your monitoring cluster. Or as an alternative to internal collection, use Metricbeat collection. The benefit of using internal collection instead of Metricbeat is that you have fewer pieces of software to install and maintain.
To learn about monitoring in general, see Monitor a cluster.
Create a user that has appropriate authority to send system-level monitoring
data to Elasticsearch. For example, you can use the built-in
beats_systemuser or assign the built-in
beats_systemrole to another user. For more information, see Grant privileges and roles needed for monitoring.
monitoringsettings in the Metricbeat configuration file. If you configured the Elasticsearch output and want to send Metricbeat monitoring events to the same Elasticsearch cluster, specify the following minimal configuration:
monitoring: enabled: true elasticsearch: username: beats_system password: somepassword
If you configured a different output, such as Logstash or you want to send Metricbeat monitoring events to a separate Elasticsearch cluster (referred to as the monitoring cluster), you must specify additional configuration options. For example:
monitoring: enabled: true cluster_uuid: PRODUCTION_ES_CLUSTER_UUID elasticsearch: hosts: ["https://example.com:9200", "https://example2.com:9200"] username: beats_system password: somepassword
This setting identifies the Elasticsearch cluster under which the monitoring data for this Metricbeat instance will appear in the Stack Monitoring UI. To get a cluster’s
cluster_uuid, call the
GET /API against that cluster.
This setting identifies the hosts and port numbers of Elasticsearch nodes that are part of the monitoring cluster.
- Start Metricbeat.
- View the monitoring data in Kibana.
Intro to Kibana
ELK for Logs & Metrics