Metrics

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.

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

The total memory of the system in bytes.

Free memory of the system in bytes.

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%.

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

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

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

The number of CPU cycles spent executing application code.

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

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.

The current allocated heap size in bytes.

The currently used heap size in bytes.

The sum of all transaction durations in ms since the last report (the delta)

You can filter and group by these dimensions:

The count of all transactions since the last report (the delta)

You can filter and group by these dimensions:

The number of transactions for which breakdown metrics (span.self_time) have been created. Breakdown metrics are only collected for sampled transactions.

You can filter and group by these dimensions:

The sum of all span self-times in milliseconds since the last report (the delta)

You can filter and group by these dimensions:

You can filter and group by these dimensions: