Skip to content

Commit

Permalink
Update CHANGELOG.md
Browse files Browse the repository at this point in the history
  • Loading branch information
jvarney authored and GitHub Enterprise committed Jan 15, 2020
1 parent 0c52dcb commit e746f8e
Showing 1 changed file with 19 additions and 17 deletions.
36 changes: 19 additions & 17 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,23 +2,25 @@

### New Features

* Support for W3C Trace Context, with easy upgrade from New Relic trace context
* Distributed Tracing now supports W3C Trace Context headers for HTTP and
gRPC protocols 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
`Config.DistributedTracer.Enabled = true`, the Go agent will now accept
W3C's `traceparent` and `tracestate` headers when calling
[`Transaction.AcceptDistributedTraceHeaders`](https://godoc.org/github.com/newrelic/go-agent/v3/newrelic#Transaction.AcceptDistributedTraceHeaders). When calling
[`Transaction.InsertDistributedTraceHeaders`](https://godoc.org/github.com/newrelic/go-agent/v3/newrelic#Transaction.InsertDistributedTraceHeaders), the Go agent will include the
W3C headers along with the New Relic distributed tracing header, unless
the New Relic trace header format is disabled using
`Config.DistributedTracer.ExcludeNewRelicHeader = true`.
* Support for W3C Trace Context, with easy upgrade from New Relic trace context.

Distributed Tracing now supports W3C Trace Context headers for HTTP and
gRPC protocols 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
`Config.DistributedTracer.Enabled = true`, the Go agent will now accept
W3C's `traceparent` and `tracestate` headers when calling
[`Transaction.AcceptDistributedTraceHeaders`](https://godoc.org/github.com/newrelic/go-agent/v3/newrelic#Transaction.AcceptDistributedTraceHeaders). When calling
[`Transaction.InsertDistributedTraceHeaders`](https://godoc.org/github.com/newrelic/go-agent/v3/newrelic#Transaction.InsertDistributedTraceHeaders), the Go agent will include the
W3C headers along with the New Relic distributed tracing header, unless
the New Relic trace header format is disabled using
`Config.DistributedTracer.ExcludeNewRelicHeader = true`.

* Added support for [elastic/go-elasticsearch](https://github.com/elastic/go-elasticsearch)
in the new [v3/integrations/nrelasticsearch-v7](https://godoc.org/github.com/newrelic/go-agent/v3/integrations/nrelasticsearch-v7)
Expand Down

0 comments on commit e746f8e

Please sign in to comment.