Pm2: Disable default probes in ProcessContainer.

[ghost]

I notice that custom probes are not available on keymetrics.io and CliUx in cluster mode. I add loging to https://github.com/Unitech/PM2/blob/master/lib/God/ClusterMode.js#L61 and get logs like:

PM2 { type: 'axm:monitor',
  data: 
   { 'Loop delay': { value: '44.61ms', agg_type: 'avg' },
     'Active connections': { value: 0, agg_type: 'avg' },
     'Registered': { value: 0, agg_type: 'avg' },
     'Default queue length': { value: 0, agg_type: 'avg' },
     'Failed jobs': { value: 0, agg_type: 'avg' },
     HTTP: { value: '0req/s', agg_type: 'avg' },
     'pmx:http:latency': { value: '0ms', agg_type: 'avg' } } }
PM2 { type: 'axm:monitor',
  data: 
   { 'Loop delay': { value: '48.08ms', agg_type: 'avg' },
     HTTP: { value: '0req/s', agg_type: 'avg' },
     'pmx:http:latency': { value: '0ms', agg_type: 'avg' } } }

It seems that default cover custom probes on every tick. If disable pmx.init here everything work fine.
Reproduced on Debian GNU/Linux 8 (jessie), 2 servers, pm2 v0.14.2. On Ubuntu 15.04 all data available, logs still get entries of default probes, but in reverse order:

PM2 { type: 'axm:monitor',
  data: 
   { 'Loop delay': { value: '48.08ms', agg_type: 'avg' },
     HTTP: { value: '0req/s', agg_type: 'avg' },
     'pmx:http:latency': { value: '0ms', agg_type: 'avg' } } }
PM2 { type: 'axm:monitor',
  data: 
   { 'Loop delay': { value: '44.61ms', agg_type: 'avg' },
     'Active connections': { value: 0, agg_type: 'avg' },
     'Registered': { value: 0, agg_type: 'avg' },
     'Default queue length': { value: 0, agg_type: 'avg' },
     'Failed jobs': { value: 0, agg_type: 'avg' },
     HTTP: { value: '0req/s', agg_type: 'avg' },
     'pmx:http:latency': { value: '0ms', agg_type: 'avg' } } }

How can I disable ProcessContainer pmx.init?

[Unitech]

duplicate #1181

[jshkurti]

pm2 start app.js --no-pmx : https://github.com/Unitech/PM2/commit/5faefd2ac8e67f4ca1305b28bcbd35761684efc2