pmx icon indicating copy to clipboard operation
pmx copied to clipboard

(DEPRECATED) use @pm2/io instead (drop-in replacement) https://github.com/keymetrics/pm2-io-apm

Results 24 pmx issues
Sort by recently updated
recently updated
newest added

So after switching from fork to cluster metrics works incorrectly (rps for example gone from 10 to 1.4 in 8 clusters), how to solve that? It's inccorect just to multiply...

See screenshots. This is a continued and sharp rise in use over 8 hour period. The box has consistent processing flow. The leak appears to be from the global include...

I feel as though I'm just misusing this package somehow, but I can't figure out what I'm doing wrong. I've setup 4 different trackers for my app that is run...

I am constantly getting this error, could it be from Node version being 9.9.0? `Error message: Probe Active handles has reached value null`

Sometimes I want to delete the `metric`, what should I do?

We use Webpack to package our node app, but we can't make pmx work because it looks for some conf in the `package.json`. We get the below exception on `require(pmx)`...

![image](https://user-images.githubusercontent.com/757747/35160506-a1a874c2-fd3d-11e7-9440-38179dbf996a.png) + all custom metrics = 0

Probe

Unless require('pmx').init({ports: true}) is called before express app.listen() is called, the custom event will not properly report which port app is listening to. Should it matter when init is called?...

I'm not sure I understand how this works: ```ts export const cacheReloadAvg = pmxProbe.meter({ name: "cache reload", seconds: 60 }); ``` I would assume setting `mark()` twice over 60 second...