Infinite Tracing on New Relic Edge
This release adds support for Infinite Tracing on New Relic Edge. Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems.
You configure your agent to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network.
Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative.
Error attributes now added to each span that exits with an error or exception
error.messageare now included on the span event in which an error or exception was noticed, and, in the case of unhandled exceptions, on any ancestor spans that also exit with an error. The public API method
NoticeErrornow attaches these error attributes to the currently executing span.
Spans with error details are now highlighted red in the Distributed Tracing UI, and error details will expose the associated
error.message. It is also now possible to see when an exception leaves the boundary of the span, and if it is caught in an ancestor span without reaching the entry span. NOTE: This “bubbling up” of exceptions will impact the error count when compared to prior behavior for the same trace. It is possible to have a trace that now has span errors without the trace level showing an error.
If multiple errors occur on the same span, only the most recent error information is added to the attributes. Prior errors on the same span are overwritten.
These span event attributes conform to ignored errors configuration.
- Fixes issue in the MSI installer which prevented the
InstrumentAllNETFrameworkfeature selection from working as expected on the command line.
- Fixes issue for Azure App Service environments running on Linux that caused both the application and its Kudu process to be instrumented by the agent. The Kudu process is no longer instrumented.
- Fixes issue when using the
ignoreErrorsconfiguration. Previously, when an exception contained a inner exception(s), the
ignoreErrorsconfig was only applied to the outer-most exception. Now, both the outer-most and inner-most exception type are considered when evaluating the
- Fixes an issue that could cause an exception to occur in the instrumentation for StackExchange Redis. This exception caused the instrumentation to shut down leaving StackExchange Redis uninstrumented.