Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a -q, --quiet option, and reduce the default level of verbosity. #59

Closed
nathanpeck opened this issue Jul 25, 2013 · 5 comments
Closed

Comments

@nathanpeck
Copy link
Contributor

pm2 is very verbose by default even without the -v, --verbose option. I feel that some of this default verbosity could be reduced and output only if the -v option is specified. Additionally, I feel pm2 needs a -q, --quiet option where it does not output to the console except in case of errors.

For an example of what I mean by reducing the default level of verbosity consider what happens when executing pm2 stopAll

$ pm2 stopAll
⌬ PM2 Stopping all processes
  ◡ Processing...

┌────────┬────┬─────┬────────┬───────────┬──────────────┬────────┬──────────┐
│ Script │ id │ PID │ status │ Restarted │ Last restart │ memory │ err logs │
└────────┴────┴─────┴────────┴───────────┴──────────────┴────────┴──────────┘

If pm2 stopped all processes then there shouldn't be any processes to list, and this process list below the command is useless nearly 100% of the time except perhaps if pm2 has a bug which caused a process to not be stopped.

This is just one example of where excessive console output could be trimmed out and only output if the user explicitly specifies the -v option.

What are your thoughts on this? Does anyone else agree? If so I may spend some time creating a less verbose fork and submit a pull request.

@Unitech
Copy link
Owner

Unitech commented Jul 29, 2013

Mmm yes would be nice but not critical for now, closing

@Unitech Unitech closed this as completed Jul 29, 2013
@ryanjrose
Copy link

3 years later and here I am hoping for the same thing..

@Unitech
Copy link
Owner

Unitech commented Dec 16, 2016

PM2_SILENT=true pm2 <command>

@ryanjrose
Copy link

Ah, thats great! Thanks!

@azarus
Copy link

azarus commented Jun 7, 2017

3 years later and here I am hoping for the same thing..

4 years later i am wondering what is the issue when i only get this error:
Deploy failed
I think pm2 needs the oposite (more proper error logging than this..)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants