Type to search.

Use the select metrics emitted directly to your monitoring cluster

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

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.

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