Why "You shouldn't use this module"?

[henry42]

Why "You shouldn't use this module"? I think it's a very useful module for me to monitor my processes and catch notifications.
And I didn't find a way to send notifications between processes using pm2 module in your suggestion.
(and also it's small enough)

[fredericosilva]

@henry42 have you found a way to extract those crash logs?

I'm using this module to have a single process per machine that report all the node.js crash logs to an error tracking platform.

[jmingov]

Hey guys, this repository is deprecated, and not updated.

The info about how to interact with pm2 programtically is explained here:

https://github.com/Unitech/PM2/blob/development/ADVANCED_README.md#using-pm2-programmatically

Cheers

[henry42]

@fredericosilva
I still use it for logs
@jmingov
it can not solve my problem, I need a way to "send message between processes"

[Unitech]

You should try this instead: https://github.com/Unitech/PM2/blob/master/doc/PROGRAMMATIC.md

CLI commands + BUS system (for logs, events etc)

[askhogan]

@Unitech @henry42 responded to your suggestion, and your response listed an answer which does not address the request. @henry42 wants to send messages between processes. PM2 programatic allows for remote execution commands but does not expose msgProcess. Also the PM2 programmatic commands are limited in that you can't pass a hash of data along with.

[thelonglqd]

When message was sent from worker to the master process, master needs something like
worker.on('message', function(handler)){} to handle this messages. Workers are forked automatically in pm2 so we can not have something like this.