Open janvda opened 5 years ago
This might be a similar problem as https://github.com/RuntimeTools/appmetrics-dash/issues/151
Same issue here. I tried multiple node versions no difference.
Had the same issue when using .attach()
along with .monitor()
I removed it and only kept .monitor()
Seems to work fine that way.
Hi - is there anything we can do to help resolve this? It has been a long standing issue and we (in the Node-RED project) keep getting asked why it isn't working.
@knolleary I was able to make appmetrics work on nodered just like this:
var dash = require('appmetrics-dash');
dash.monitor({port:3335}); // different port
And making NodeRED running on the different port. Taking advantage of the issue, In nodered, there is a way to capture a node's input and output events and throw this to something like jaeger?
Hi
I have tried to follow the instructions specified in the tutorial https://developer.ibm.com/node/2017/07/26/visualize-node-red-flow-performance-using-node-application-metrics/ but I get below error log:
I have added the following 2 instructions after the first line in my red.js which are causing the error:
The following release specifies the setup of the container node-red-test that has this problem : https://github.com/janvda/balena-node-red-mqtt-nginx-TIG-stack/tree/appmetrics-dash-error