Please paste the [permalink] to the page in question below:
Please share your question/describe your issue below. Include any screenshots that may help us understand your question:
We use the New Relic node.js agent (specifically,
newrelic.endTransaction()) to capture transactions for scheduled jobs that we run on various schedules, which works great. We can generally get a view of which jobs are slow, and the specific instances of those jobs that are slowest show up in the list of slow Transaction Traces.
However, we have one job in particular that we recently discovered is taking so long that it never actually completes, and
newrelic.endTransaction() is never called. The transaction is still in progress when the node process is terminated (generally as a result of deploying a new version of the application each week). This job does not seem to appear at all in the list of transactions. Are incremental traces of transactions which are started but never end sent from the agent to New Relic? If so, is there some way to see these incomplete transactions? If not, do you have any advice for how we can ensure that these transactions are captured in some way even if the node process is terminated before the transaction completes?
New Relic edit
- I want this, too
- I have more info to share (reply below)
- I have a solution for this
We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.