Key Monitoring Metrics for Node.js Applications and Open‑Source Tools

Running an application without monitoring is like operating a black box; you have no visibility into its current state and risk unexpected failures. This article introduces Node.js monitoring concepts and practical metrics.

Monitoring Metrics

1. CPU Usage

Node.js typically consumes little CPU due to its asynchronous non‑blocking I/O, but the event loop runs on the main thread and can be blocked by CPU‑intensive tasks, leading to high CPU usage and load. Avoid heavy CPU work on the main thread or offload it to workers.

CPU Usage

CPU Load

2. Memory Usage and Leaks

Understanding heap and stack is essential: the stack stores function contexts, while the heap holds dynamically allocated data. A single process can have up to 1.5 GB heap. Even with V8’s garbage collection, memory leaks are common and observable.

Released memory between Garbage Collection cycles

Process Heap Size

Process Heap Usage

3. Garbage Collection

Two types exist: incremental GC cycles, which process a portion of the heap quickly, and full GC cycles, which pause the program and run rarely. Measuring their frequency and the amount of memory reclaimed helps detect trends.

Time consumed for garbage collection

Counters for full garbage collection cycles

Counters for incremental garbage collection cycles

Released memory after garbage collection

4. Event Loop

The event loop dispatches asynchronous tasks but must also handle callbacks, which can lead to event‑loop lag caused by long‑running synchronous processes or an increasing number of tasks per loop. Use forks or child processes to avoid blocking, and consider cluster mode to mitigate load.

Slowest Event Handling (Max Latency)

Fastest Event Handling (Min Latency)

Average Event Loop Latency

5. Cluster‑Mode and Forking Worker Processes

Cluster mode and worker processes are widely used and should be monitored.

Worker count

Event loop latency per worker

6. Request/Response Latency

Since services ultimately handle requests and responses, monitoring these aspects is essential.

Response time

Request rate

Error rates

Request/Response content size

Open‑Source Monitoring Tools

Several ready‑to‑use tools are recommended:

Prometheus – a cloud‑native, language‑agnostic monitoring system (https://prometheus.io)

PM2 – process manager for Node.js (https://github.com/Unitech/pm2)

Appmetrics – performance monitoring for Node.js (https://github.com/RuntimeTools/appmetrics-dash)

Clinic.js – profiling and diagnostics suite (https://github.com/nearform/node-clinic)

Express Status Monitor – real‑time monitoring middleware (https://github.com/RafalWilinski/express-status-monitor)