Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Feature Idea: Failed external requests not appearing in external calls

http-requests
feature-idea

#1

Hello, we have noticed that outgoing requests (via superagent library) that failes with error (EABORTED, ECONNRESET, ETIMEDOUT) are not instrumented/tracked in newrelic; successfull calls show up in traces if they take long enough.

This is valid both for node-newrelic 1.40 and 2.3(.1)

Is there any help you could provide with this?

Thank you


New Relic edit

  • I want this, too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

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.


#2

okay, after more investigation

done in https://github.com/tomasstrejcek/node-newrelic-superagent/blob/master/index.js

it looks like whenever request fails, it doesnt get tracked … how should we approach this?

also this is experimental apm we used to look into this

https://rpm.newrelic.com/accounts/1150820/applications/90350457/transactions


#3

Hey there @tomas.s! I see that you also sent in a support ticket regarding this. As was expressed in the ticket, what you are describing is considered a feature request at this time. I have added a poll so that others can vote based on interest in seeing this! :blush: Thanks!