how see running process error showing on pm2 list command?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
hello dear friends
how can i see why pm2 process restarted?
Due to the large number of online users, the logs fill up very quickly and the volume of the current log file is very large.
I want to see exactly the same error that caused the restart and in the attached image the value of 1 error is recorded. Is there a way?
i attached an image about my question
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
The issue concerns the pm2 list command and asks whether restart-causing errors can be shown without relying on rapidly growing logs. Start by reproducing a restart and inspecting the current pm2 list output; define done as exposing the relevant error details there or documenting that this is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100