Exception that crashes cluster node not reported to newrelic

[itaifrenkel]

When using the nodejs cluster module, I would like to get the exception that caused the node (child process) to crash. This could be done with domains, the question is whether there is a way for the agent to do it automatically.

[othiym23]

Hi, Ital!

When New Relic for Node is running under cluster, each worker (and the master) maintains its own connection to New Relic, as well as its own periodic harvest cycle.Because of this, there's no guaranteed way for it to send a message back to New Relic when it crashes. The module's connection to New Relic isn't persistent, and worker processes are unlikely to get enough time to establish a new one while they're crashing. Also, it's pretty important that New Relic not alter your app's crashing behavior itself.

So, no, we can't do this. We might come up with a way to do,something cluster-specific in the future, but that's uncertain, and so a ways off even if we do decide to do it. Sorry we don't have a better answer right now!