pm2 monit should not clear logs on navigation
Open
Nobody has claimed this yet.
S: Pending Release
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
No-one at Unitech making a statement about the uselessness of pm2 monit if it just clears the logs on navigation, making it pointless for investigations
How could we reproduce this issue?
pm2 monit- navigate between logs
Supporting information
#4565 for more details, OP gave up on preventing a stale
$ pm2 report
--- PM2 report ----------------------------------------------------------------
Date : Tue Nov 24 2020 17:25:46 GMT+0100 (Central European Standard Time)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version : 4.5.0
node version : 10.20.1
node path : not found
argv : /usr/local/bin/node,/usr/local/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : jondek
uid : 1000
gid : 1000
uptime : 11min
===============================================================================
--- CLI ----------------------------------------------------
local pm2 : 4.5.0
node version : 10.20.1
node path : not found
argv : /usr/local/bin/node,/usr/local/bin/pm2,report
argv0 : node
user : jondek
uid : 1000
gid : 1000
===============================================================================
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : AMD Ryzen 9 3900X 12-Core Processor
cpus nb : 12
freemem : 777572352
totalmem : 16789843968
home : /home/jondek
===============================================================================
--- PM2 list -----------------------------------------------
┌─────┬────────────────────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 6 │ mdt-app-client-seed │ default │ 0.0.1 │ fork │ 81917 │ 11m │ 0 │ online │ 0% │ 37.5mb │ jondek │ disabled │
│ 4 │ mdt-app-client-webapp │ default │ 0.0.1 │ fork │ 81744 │ 11m │ 0 │ online │ 0% │ 36.6mb │ jondek │ disabled │
│ 5 │ mdt-app-client-webapp:proxy │ default │ 0.0.1 │ fork │ 81840 │ 11m │ 0 │ online │ 0% │ 37.0mb │ jondek │ disabled │
│ 1 │ mdt-app-service-api │ default │ 0.0.1 │ fork │ 81452 │ 11m │ 0 │ online │ 0% │ 37.5mb │ jondek │ disabled │
│ 2 │ mdt-app-service-api-reports │ default │ 0.0.1 │ fork │ 81506 │ 11m │ 0 │ online │ 0% │ 37.0mb │ jondek │ disabled │
│ 3 │ mdt-app-service-session │ default │ 0.0.1 │ fork │ 81650 │ 11m │ 0 │ online │ 0% │ 36.1mb │ jondek │ disabled │
│ 0 │ mongo │ default │ 0.0.1 │ fork │ 81401 │ 11m │ 0 │ online │ 0.5% │ 36.2mb │ jondek │ disabled │
└─────┴────────────────────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/home/jondek/.pm2/pm2.log last 20 lines:
PM2 | 2020-11-24T17:14:27: PM2 log: Application log path : /home/jondek/.pm2/logs
PM2 | 2020-11-24T17:14:27: PM2 log: Worker Interval : 30000
PM2 | 2020-11-24T17:14:27: PM2 log: Process dump file : /home/jondek/.pm2/dump.pm2
PM2 | 2020-11-24T17:14:27: PM2 log: Concurrent actions : 2
PM2 | 2020-11-24T17:14:27: PM2 log: SIGTERM timeout : 1600
PM2 | 2020-11-24T17:14:27: PM2 log: ===============================================================================
PM2 | 2020-11-24T17:14:37: PM2 log: App [mongo:0] starting in -fork mode-
PM2 | 2020-11-24T17:14:37: PM2 log: App [mongo:0] online
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-service-api:1] starting in -fork mode-
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-service-api:1] online
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-service-api-reports:2] starting in -fork mode-
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-service-api-reports:2] online
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-service-session:3] starting in -fork mode-
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-service-session:3] online
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-client-webapp:4] starting in -fork mode-
PM2 | 2020-11-24T17:14:38: PM2 log: App [mdt-app-client-webapp:4] online
PM2 | 2020-11-24T17:14:39: PM2 log: App [mdt-app-client-webapp:proxy:5] starting in -fork mode-
PM2 | 2020-11-24T17:14:39: PM2 log: App [mdt-app-client-webapp:proxy:5] online
PM2 | 2020-11-24T17:14:39: PM2 log: App [mdt-app-client-seed:6] starting in -fork mode-
PM2 | 2020-11-24T17:14:39: PM2 log: App [mdt-app-client-seed:6] online
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with pm2 monit, then trace the monitor's log handling when navigating between logs. The issue references #4565 for additional context. Done means navigation no longer clears the logs needed for investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100