WATCHLOG INTEGRATION
P
Monitor PM2.
Monitor PM2-managed Node.js processes — CPU, memory, restart count, uptime, and process status for every application in your fleet.
18 metrics·Per-process visibility·30s setup
WHAT WATCHLOG COLLECTS
Complete PM2 observability.
The Watchlog Agent collects these metrics automatically once the PM2 integration is enabled.
pm2.process.cpuProcess CPU %
CPU usage for each individual PM2-managed process
pm2.process.memoryProcess Memory (RSS)
Resident Set Size — RAM used by each process in bytes
pm2.process.heapUsedHeap Used
V8 heap memory actively in use by Node.js's garbage collector
pm2.process.heapTotalHeap Total
Total V8 heap allocated for the process
pm2.process.pm_uptimeProcess Uptime
Seconds the process has been running continuously
pm2.process.restart_timeRestart Count
Total number of times the process has been restarted
pm2.process.statusProcess Status
Current state: online, stopped, errored, or launching
pm2.process.pidProcess ID (PID)
Operating system PID for the running process
pm2.cluster.instancesCluster Instances
Number of worker instances in cluster mode
pm2.event_loop.delayEvent Loop Delay
Node.js event loop lag in milliseconds — key for async performance
pm2.http.activeActive Requests
HTTP requests currently being handled by the process
pm2.error.rateErrors/min
Uncaught exceptions and unhandled rejections per minute
LIVE DASHBOARD
PM2 at a glance.
A pre-built PM2 dashboard activates the moment you enable the integration — no configuration required.
● PM2 Dashboard● Live
api-server (cluster×4)
online
CPU (api-server)
18%
Memory (api-server)
312 MB
Restarts (24h)
3
Event Loop Delay
4.2ms
Active Requests
87
USE CASES
What engineers use PM2 monitoring for.
Memory leak detection
Track heap usage and RSS over time per process. A steadily climbing heap with no ceiling usually means a memory leak.
Restart loop alerting
Alert when a PM2 process exceeds a restart threshold — a common signal of uncaught exceptions or misconfigured environment variables.
Event loop performance monitoring
High event loop delay means your Node.js process is CPU-bound or blocking. Catch it before it degrades request latency.
Cluster mode visibility
Monitor each worker independently in PM2 cluster mode. See which workers are hot and which are idle or crashing.
WHY WATCHLOG
Fewer blind spots. Earlier warnings.
Engineering teams that monitor PM2 with Watchlog catch failure signals before they become incidents.
- ✓Catch memory leaks in Node.js processes before they cause OOM restarts
- ✓Alert on restart loops that indicate uncaught exceptions in production
- ✓Track event loop delay — the most important Node.js performance signal
- ✓Monitor cluster workers individually to detect uneven load distribution
- ✓Know when a PM2 process has stopped before the API it powers goes dark
QUICK SETUP
PM2 monitoring in under 2 minutes.
No YAML. No config files. The Watchlog Agent detects PM2 on your host and begins collecting immediately.
01
Install the Watchlog Agent
One command on your Node.js host. The agent reads PM2 process data via the pm2 list API.
02
Enable PM2 integration
Go to Watchlog → Integrations → PM2 and click Enable. The agent detects running PM2 processes automatically.
03
Process metrics in 60s
CPU, memory, uptime, restart count, and event loop delay per process appear immediately.
INSTALL WATCHLOG AGENT
sudo apiKey="$WATCHLOG_API_KEY" server="$WATCHLOG_SERVER" MEMORY="300M" bash -c "$(curl -L https://watchlog.io/ubuntu/watchlog-script.sh)The agent automatically detects PM2 running on your host and begins collecting metrics immediately.
GET STARTED
Start monitoring PM2 now.
Full PM2 visibility in under 2 minutes. No credit card required.
Questions? Contact us at [email protected]