Thursday, April 30, 2020 - 16:00
- Support for W3C Trace Context, with easy upgrade from New Relic trace context
- Distributed Tracing now supports W3C Trace Context headers for HTTP when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format.
- When distributed tracing is enabled with
<distributedTracing enabled="true" />, the .NET agent will now accept W3C's
tracestateheaders when calling Transaction.AcceptDistributedTraceHeaders. When calling Transaction.InsertDistributedTraceHeaders, the .NET agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using
<distributedTracing enabled="true" excludeNewrelicHeader="true" />.
- The existing
Transaction.CreateDistributedTracePayloadAPIs are deprecated in favor of Transaction.AcceptDistributedTraceHeaders and Transaction.InsertDistributedTraceHeaders.
- Fixes issue which prevented Synthetics from working when distributed tracing is enabled.
- Fixes issue where our RPM package for installing the agent on RPM-based Linux distributions included a 32-bit shared library, which created unnecessary dependencies on 32-bit system libraries.
- Fixes issue where the TransportDuration metric for distributed traces was always reporting 0.