Type to search.

Metrics

Serverless Observability

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

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.

APM Agent Node.js

The Elastic APM Node.js agent enables you to trace the execution of operations in your Node.js applications, sending performance metrics and errors to the Elastic APM Server.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

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.

The Node.js agent tracks various system and application metrics. These metrics will be sent regularly to the APM Server and from there to Elasticsearch. You can adjust the interval by setting metricsInterval.

The metrics will be stored in the apm-* index and have the processor.event property set to metric.

  • Type: Float
  • Format: Percent

The percentage of CPU time in states other than Idle and IOWait, normalized by the number of cores.

  • Type: Long
  • Format: Bytes

The total memory of the system in bytes.

  • Type: Long
  • Format: Bytes

Free memory of the system in bytes.

  • Type: Float
  • Format: Percent

The percentage of CPU time spent by the process since the last event. This value is normalized by the number of CPU cores and it ranges from 0 to 100%.

  • Type: Long
  • Format: Bytes

The Resident Set Size, the amount of memory the process occupies in main memory (RAM).

  • Type: Long
  • Format: Counter

The number of active libuv handles, likely held open by currently running I/O operations.

  • Type: Long
  • Format: Counter

The number of active libuv requests, likely waiting for a response to an I/O operation.

  • Type: Long
  • Format: Counter

The number of CPU cycles spent executing application code.

  • Type: Long
  • Format: Counter

The number of CPU cycles spent executing kernel code as a result of application activity.

  • Type: Float
  • Format: Milliseconds

The number of milliseconds of event loop delay. Event loop delay is sampled every 10 milliseconds. Delays shorter than 10ms may not be observed, for example if a blocking operation starts and ends within the same sampling period.

  • Type: Long
  • Format: Bytes

The current allocated heap size in bytes.

  • Type: Long
  • Format: Bytes

The currently used heap size in bytes.

  • Type: Long
  • Format: Bytes

Memory usage of C++ objects bound to JavaScript objects managed by V8.

  • Type: Long
  • Format: Bytes

Memory allocated for ArrayBuffers and SharedArrayBuffers, including all Node.js Buffers. This is also included in the nodejs.memory.external.bytes value.

  • Type: Long
  • Format: Milliseconds

The sum of all span self-times in milliseconds since the last report (the delta). The span.self_time.* metrics are referred to as "breakdown metrics".

You can filter and group by these dimensions:

  • transaction.name: The name of the transaction
  • transaction.type: The type of the transaction, for example request
  • span.type: The type of the span, for example app, template or db
  • span.subtype: The sub-type of the span, for example mysql (optional)
  • Type: Long
  • Format: Counter

You can filter and group by these dimensions:

  • transaction.name: The name of the transaction
  • transaction.type: The type of the transaction, for example request
  • span.type: The type of the span, for example app, template or db
  • span.subtype: The sub-type of the span, for example mysql (optional)