Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 40 million developers.Sign up
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
tracestateheaders when calling
Transaction.AcceptDistributedTraceHeaders. When calling
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.
Event data is now sent to New Relic every five seconds, instead of every
minute. As a result, transaction, custom, and error events will appear in
near-realtime within APM and Insights.
Note that the overall limits on how many events can be sent per minute have
not changed. Also, metric and trace data is unaffected, and will still be
sent every minute.
We are pleased to announce the release of Go Agent v3.0.0! This is a major release
that includes some breaking changes that will simplify your future use of the Go
Please pay close attention to the list of Changes.
- A full list of changes and a step by step checklist on how to upgrade can
be found in the v3 Migration Guide.
Support for Go Modules. Our Go agent integration packages support frameworks
and libraries which are changing over time. With support for Go Modules, we
are now able to release instrumentation packages for multiple versions of
frameworks and libraries with a single agent release; and support operation
of the Go agent in Go Modules environments. This affects naming of our
integration packages, as described in the v3 Migration Guide (see under
Detect and set hostnames based on Heroku dyno names. When deploying an
application in Heroku, the hostnames collected will now match the dyno name.
This serves to greatly improve the usability of the servers list in APM since
dyno names are often sporadic or fleeting in nature. The feature is
controlled by two new configuration options