Open ikb42 opened 9 years ago
It's a feature, not a bug.
The reasoning is because in Node.js apps which use cluster support all processes would report to the same component, and not allow you to drill down to a problem in a particular child process running on a given machine.
I don't particularly like the way that affects the reporting myself, but admittedly did not put that much thought into better alternatives. I'm open to suggestions.
I don't know enough about that type of use to make suggestions there, but perhaps this could be a configurable option?
It seems that a new "component" ID is generated each app restart, which makes any custom dashboard setup for a previous instance redundant meaning this would need to be changed in NewRelic every restart?