Added support for W3C Trace Context, with easy upgrade from New Relic trace context.
Distributed Tracing now supports W3C Trace Context headers for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both the W3C trace header format and the 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
distributed_tracing.enabled: true, the Node agent will now accept W3C's
tracestateheaders when calling
TransactionHandle#acceptDistributedTraceHeadersor automatically via
httpinstrumentation. When calling
Transaction#insertDistributedTraceHeaders, or automatically via
httpinstrumentation, the Node agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using
TransactionHandle#acceptDistributedTraceHeadersAPI for accepting both New Relic and W3C TraceContext distributed traces.
TransactionHandle#acceptDistributedTracePayloadwhich will be removed in a future major release.
TransactionHandle#insertDistributedTraceHeadersAPI for adding outbound distributed trace headers. Both W3C TraceContext and New Relic formats will be included unless
TransactionHandle#createDistributedTracePayloadwhich will be removed in a future major release.
Known Issues and Workarounds
- If a .NET agent is initiating traces as the root service, do not upgrade your downstream Node New Relic agents to this agent release.
Improved Transaction and Trace ID generation.
- Added collection of additional AWS Lambda event source meta data.
- Added event type detection for lambda invocation events.
- Expanded ARN harvest to include ALB and CloudWatch.
Fixed issue where lambda invocation errors were not noticed in Node 10 or Node 12 environments.
Pins Node 12 CI/testing version to
v12.15to avoid breakages with
v12.16.0until cause(s) resolved.
Updated publish-docs script to use
npm runinstead of