PM2 v5 not reporting machine total RAM and CPU type to app.pm2.io

What's going wrong?

PM2 v5 is not reporting RAM and CPU like v4 did.

How could we reproduce this issue?

Update from PM2 v4 to v5.

Supporting information

$ pm2 report

--- Daemon logs --------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2        | 2022-07-06T06:50:37: PM2 log: ===============================================================================
PM2        | 2022-07-06T06:50:37: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2        | 2022-07-06T06:50:37: PM2 log: Time                 : Wed Jul 06 2022 06:50:37 GMT-0400 (Eastern Daylight Time)
PM2        | 2022-07-06T06:50:37: PM2 log: PM2 version          : 5.2.0
PM2        | 2022-07-06T06:50:37: PM2 log: Node.js version      : 16.15.1
PM2        | 2022-07-06T06:50:37: PM2 log: Current arch         : x64
PM2        | 2022-07-06T06:50:37: PM2 log: PM2 home             : /root/.pm2
PM2        | 2022-07-06T06:50:37: PM2 log: PM2 PID file         : /root/.pm2/pm2.pid
PM2        | 2022-07-06T06:50:37: PM2 log: RPC socket file      : /root/.pm2/rpc.sock
PM2        | 2022-07-06T06:50:37: PM2 log: BUS socket file      : /root/.pm2/pub.sock
PM2        | 2022-07-06T06:50:37: PM2 log: Application log path : /root/.pm2/logs
PM2        | 2022-07-06T06:50:37: PM2 log: Worker Interval      : 30000
PM2        | 2022-07-06T06:50:37: PM2 log: Process dump file    : /root/.pm2/dump.pm2
PM2        | 2022-07-06T06:50:37: PM2 log: Concurrent actions   : 2
PM2        | 2022-07-06T06:50:37: PM2 log: SIGTERM timeout      : 1600
PM2        | 2022-07-06T06:50:37: PM2 log: ===============================================================================
PM2        | 2022-07-06T06:50:37: PM2 log: App [pm2-logrotate:0] starting in -fork mode-
PM2        | 2022-07-06T06:50:37: PM2 log: App [pm2-logrotate:0] online
PM2        | 2022-07-06T06:50:37: PM2 log: App [api:1] starting in -fork mode-
PM2        | 2022-07-06T06:50:37: PM2 log: App [api:1] online

Start by reproducing the upgrade from PM2 v4 to v5 and compare the machine information sent to app.pm2.io. The issue provides no source file or test entry point, so trace the reporting path from the reproduction and verify that machine total RAM and CPU type are reported as they were in v4.