5.0.0

System Monitoring

A new local system monitoring feature has been added, allowing to monitor numerous vital server metrics.

Most important metrics will be displayed when doing a pm2 ls:

┌─────┬─────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name            │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼─────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 4   │ app             │ default     │ 1.0.0   │ fork    │ 164618   │ 2s     │ 1670 │ online    │ 0%       │ 41.8mb   │ unitech  │ disabled │
└─────┴─────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
host metrics | cpu: 1.6% 42.9º | mem free: 52.0% | wlp0s20f3: ⇓ 0mb/s ⇑ 0mb/s | disk: ⇓ 0.199mb/s ⇑ 0mb/s /dev/nvme0n1p3 88.25% |

All server metrics will be available to pm2.io:

┌─────────────────────────────┬──────────────────────────────────┐
│ PM2 CPU Usage               │ 0.0 %                            │
│ PM2 Memory Usage            │ 67.4 mb                          │
│ PM2 Agent CPU Usage         │ 0 %                              │
│ PM2 Agent Memory Usage      │ 0 mb                             │
│ CPU Usage                   │ 1.5 %                            │
│ CPUs Usage                  │ 0|0|0|0|2|0|0|1|0|0|0|1|0|1|2|8  │
│ CPU Temperature             │ 42.9 °C                          │
│ RAM Total                   │ 15.34 gb                         │
│ RAM Free                    │ 1.18 gb                          │
│ RAM Active                  │ 7.35 gb                          │
│ RAM Available               │ 7.99 gb                          │
│ RAM Usage                   │ 47.9 %                           │
│ FD Opened                   │ 15072                            │
│ Disk Writes                 │ 0 mb/s                           │
│ Disk Reads                  │ 0.24 mb/s                        │
│ Disk Usage                  │ 88.25 %                          │
│ Disk Size                   │ 465.60 gb                        │
│ Total TX                    │ 0.005 mb/s                       │
│ Total RX                    │ 0.004 mb/s                       │
│ fs:use:/dev/nvme0n1p3       │ 88.25 %                          │
│ fs:size:/dev/nvme0n1p3      │ 465.60 gb                        │
│ net:tx_5:wlp0s20f3          │ 0.005 mb/s                       │
│ net:rx_5:wlp0s20f3          │ 0.004 mb/s                       │
│ net:rx_errors_60:wlp0s20f3  │ 0 /min                           │
│ net:tx_errors_60:wlp0s20f3  │ 0 /min                           │
│ net:rx_dropped_60:wlp0s20f3 │ 0 /min                           │
│ net:tx_dropped_60:wlp0s20f3 │ 0 /min                           │
│ graphics:mem:total          │ 3878 mb                          │
│ graphics:mem:used           │ 1260 mb                          │
│ graphics:temp               │ 46 °C                            │
└─────────────────────────────┴──────────────────────────────────┘

Disabling system monitoring

# Disable system monitoring
pm2 set pm2:sysmonit false
# Enable system monitoring
pm2 set pm2:sysmonit true

PM2.io bandwidth reduction

Data quantity sent from PM2 to PM2.io has been reduced by 80%, thanks for a json patch differential system. Much more data can now be exposed (metrics, actions) to PM2.io

Other fixes

• feat: added args and full script path to monitoring data
• fix: regular local ip check
• fix: pm2 agent watchdog has been consolidated and fixes freezing issues
• fix: modules bumped

4.5.6

• all submodules version bumped
• supress all "security" warnings

4.5.5

• bump debug
• remove systeminformation

4.5.4

• drop non used package
• bump vizion from 0.2.13 to 2.2.1 (Snyk CVE)
• bump chokidar to 3.5.1

4.5.2

• bump @pm2/js-api (axios CVE)

4.5.1

• fix: cron in cluster mode was not restarting process after one pass - fixes #4834 #4733 #4307 #4834
• fix: restore --sort option on pm2 ls - fix #4536
• fix: fix tests with npm7
• fix: restore warning message about process list changed and not dumped
• chore: alias --cron with --cron-restart
• chore: test PM2 againt Node.js 15.x
• chore: upgrade systeminformation and debug module to latest - PR #4892 by @AdamMajer
• chore: drop Node 9.x from travis testing
• chore: remove ps-list module

4.5.0

4.5.0

• fix: creating log folder in sync mode. #4846 - PR #4844 by @QS20199
• fix: PM2 unable to run ESM packages: ERR_UNSUPPORTED_ESM_URL_SCHEME #4839 - PR #4841 by @ox-harris
• fix: Use opts.namespace if it was passed in. Previously, it was ignored. #4778 - PR #4791 by @sbleon
• fix: Prevent reloadLogs command from hanging. #4781 - PR #4782 by @mbrooks and Franck Danard
• fix: backward compatibility fix for tarball modules - PR #4767 by @ykolbin
• fix: Operation not permitted on call setgid #2957 - PR #4681 by @guard43ru
• chore: upgrade dependencies

4.4.1

• feature drop: autodump fixes #4763
• fix: fix starting pm2 script from inside an app #4761 (need use PM2_PROGRAMMATIC)

4.4.0

• feat: fixes for Node.js 14

4.3.1

• Rollback to vizion < 1.0