3.4.1

• fix: allow pm2 register / pm2 monitor
• fix: restore trace indicator

3.4.0

3.4.0

• use @pm2/io version 4
• disable @pm2/io for node.js v4 and v5

/!\ Warning, built-in custom metrics are not supported anymore on Node 4 and 5

New builtin metrics when starting a Node.js application:

• Heap Size
• Heap Usage
• Used Heap Size
• Active Requests
• Active handles
• Event loop latency
• Event loop latency p95
• HTTP queries per minutes
• HTTP Mean Latency
• HTTP P95 Latency

3.3.1

• add pm2 profile:cpu [timeout]
• add pm2 profile:mem [timeout]

3.3.0

Upgrade pmx to ^3

3.2.9

fix windows issue when spawning PM2 daemon

3.2.7

Revert fix tentative to support Node.js managed by Ubuntu snap

3.2.5

3.2.5 (09/01/19)

• feat: enhance pm2 report
• feat: support snap Ubuntu system
• fix: pm2 register/monitor command
• fix: consolidate spawn function on unhealthy systems to avoid pm2 crash
• fix: error message if extra lang interpreter are not installed when runing tests
• fix: (pm2 deploy) command line bug when passing env variables to post-deploy hook
• fix: (pm2 deploy) always deploy to default branch problem
• fix: (pm2 deploy) pm2 deploy exec now accept multiple commands
• fix: print full env + skip extra internal fields when using programmatic pm2

3.2.4

3.2.4 (19/12/18)

Feat

• display cron configuration when doing pm2 desc <id>
• refactor test suite (benchmark/simplification)

Fix

• pm2 flush flush only one app
• resolve uid properly on pm2 ls / pm2 desc
• keep wait_ready option on process reload
• keep stringification of environment variable behavior
• return an error when using pm2 api on starting json configuration if one app is errored

#4080 #4079 #4074 #4069 #4039

3.2.3

• medium rare bug: fix issue when acting on process file (#3987 + #3192)
• concurrent action to 1 if acting on only 2 processes
• fix cluster syntax
• add more test on port release

3.2.2

3.2.2 (5/10/18)

Fix

• minor bug: fix bug when passing -i 'max' or -i 0 #3943