Earlier quoted context omitted.
We watch addEventListener to do the callback timing which jQuery uses under the covers. Any requests going through the browser's xhr interface will get instrumented and reported (this is what $.get uses).
Based on what you said, it sounds like enabling this feature will have no impact on existing front-end load times. What about error reporting... are you guys satisfied with where it's at now or do you guys feel like there is more accurate and more in depth js error reporting in the future?
Announcing JS Error Reporting and Ajax Timing in New Relic
11–14 of 14 posts
Re: Announcing JS Error Reporting and Ajax Timing in New Relic
#12I've already got this set up. Looks like New Relic are going to be monitoring all the things! Soon
Indeed - we've already got http://newrelic.com/platform/ for monitoring things via plugins, we've got app server and mobile app monitoring, we've got server OS monitoring, and you are going to love what we've got coming with newrelic.com/software-analytics!
Re: Announcing JS Error Reporting and Ajax Timing in New Relic
#13Earlier quoted context omitted.
Indeed - we've already got http://newrelic.com/platform/ for monitoring things via plugins, we've got app server and mobile app monitoring, we've got server OS monitoring, and you are going to love what we've got coming with newrelic.com/software-analytics!
Is monitoring Go applications on the road map somewhere?
You could alternatively develop a Go agent using our Agent SDK: https://docs.newrelic.com/docs/features/agent-sdk