New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
« Use Metricbeat to send monitoring data APM APIs »
Elastic Docs ›Elastic Observability [8.17] ›Application and service monitoring ›Application performance monitoring (APM) ›Monitor APM Server ›Monitor the APM Server binary

Use the select metrics emitted directly to your monitoring cluster

edit
Use the select metrics emitted directly to your monitoring cluster
edit

In 8.11 and later, we emit a selected set of metrics directly to the monitoring cluster. The benefit of using local collection instead of internal collection is that the metrics are sent directly to your main monitoring index, making it easier to view shared data.

The select metrics

edit

We only ship a select list of metrics, to avoid overwhelming your monitoring cluster. If you need the entire set of metrics and traces we can expose, you should use Self Instrumentation instead of local collection.

Here is the list of every metrics we currently expose:

  • http.server.request.count
  • http.server.request.duration
  • http.server.response.valid.count
  • http.server.response.errors.count
  • http.server.errors.timeout
  • http.server.errors.ratelimit
  • grpc.server.request.count
  • grpc.server.request.duration
  • grpc.server.response.valid.count
  • grpc.server.response.errors.count
  • grpc.server.errors.timeout
  • grpc.server.errors.ratelimit
« Use Metricbeat to send monitoring data APM APIs »

On this page

Was this helpful?
Feedback