The following method involves sending the metrics to the production cluster, which ultimately routes them to the monitoring cluster. For an alternative method, see Metricbeat collection.
To learn about monitoring in general, see Monitoring 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
apm_systemuser or assign the built-in
apm_systemrole to another user. For more information, see User authentication and Built-in roles.
monitoringsettings in the APM Server configuration file. If you configured the Elasticsearch output and want to send APM Server monitoring events to the same Elasticsearch cluster, specify the following minimal configuration:
monitoring: enabled: true elasticsearch: username: apm_system password: somepassword
If you configured a different output, such as Logstash or you want to send APM Server monitoring events to a separate Elasticsearch cluster (referred to as the monitoring cluster), you must specify additional configuration options. For example:
This setting identifies the Elasticsearch cluster under which the monitoring data for this APM Server 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 APM Server.
- View the monitoring data in Kibana.