Release v3.11.0

New Features

• Aerospike is now included on the list of recognized datastore names. Thanks @vkartik97 for your PR! #233
• Added support for Verison 8 of go-redis. Thanks @ilmimris for adding this instrumentation! #251

Changes

• Changed logging level for messages resulting from Infinite Tracing load balancing operations which were previously logged as errors; now they are debugging messages. #276

Fixed

• When the agent is configured with cfg.ErrorCollector.RecordPanics set to true, panics would be recorded by New Relic, but stack traces would not be logged as the Go Runtime usually does. The agent now logs stack traces from within its panic handler, providing similar functionality. #278
• Added license files to some integrations packages to ensure compatibility with package.go.dev. Now the documentation for our integrations show up again on go.docs.

Support statement

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

Release v3.10.0

New Features

• To keep up with the latest security protocols implemented by Amazon Web
  Services, the agent now uses AWS IMDSv2 to find utilization data. #249

Changes

• Updated the locations of our license files so that Go docs https://pkg.go.dev
  will display our agent. Thanks @tydavis for your PR to fix this! #254
• Added an Open Source repo linter GitHub action that runs on push. #262
• Updated the README.md file to correctly show the support resources from New Relic. #255

Support statement

• New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months.
  As of this release, the oldest supported version is 2.2.0.

Release v3.9.0

3.9.0

Changes

• When sending Serverless telemetry using the nrlambda integration, support an externally-managed named pipe.

Release v3.8.1

Bug Fixes

• Fixed an issue that could cause orphaned Distributed Trace spans when using
  SQL instrumentation like nrmysql.

Release v3.8.0

Changes

• When marking a transaction as a web transaction using Transaction.SetWebRequest, it is now possible to include a Host field in the WebRequest struct, which defaults to the empty string.

Bug Fixes

• The Host header is now being correctly captured and recorded in the request.headers.host attribute, as described
  here.
• Previously, the timestamps on Spans and Transactions were being written using different data types, which sometimes caused rounding errors that could cause spans to be offset incorrectly in the UI. This has been fixed.

Release v3.7.0

Changes

• When Config.Transport is nil, no longer use the http.DefaultTransport
  when communicating with the New Relic backend. This addresses an issue with
  shared transports as described in golang/go#33006.

• If a timeout occurs when attempting to send data to the New Relic backend,
  instead of dropping the data, we save it and attempt to send it with the
  next harvest. Note data retention limits still apply and the agent will
  still start to drop data when these limits are reached. We attempt to keep
  the highest priority events and traces.

Release v3.6.0

New Features

• Added support for adding custom attributes directly to
  spans.
  These attributes will be visible when looking at spans in the Distributed
  Tracing UI.

  Example:

  txn := newrelic.FromContext(r.Context())
  sgmt := txn.StartSegment("segment1")
  defer sgmt.End()
  sgmt.AddAttribute("mySpanString", "hello")
  sgmt.AddAttribute("mySpanInt", 123)

• Custom attributes added to the transaction with txn.AddAttribute are now
  also added to the root Span Event and will be visible when looking at the
  span in the Distributed Tracing UI. These custom attributes can be disabled
  from all destinations using Config.Attributes.Exclude or disabled from Span
  Events specifically using Config.SpanEvents.Attributes.Exclude.

• Agent attributes added to the transaction are now also added to the root Span
  Event and will be visible when looking at the span in the Distributed Tracing
  UI. These attributes include the request.uri and the request.method along
  with all other attributes listed in the attributes section of our
  godocs.
  These agent attributes can be disabled from all destinations using
  Config.Attributes.Exclude or disabled from Span Events specifically using
  Config.SpanEvents.Attributes.Exclude.

Bug Fixes

• Fixed an issue where it was impossible to exclude the attributes
  error.class and error.message from the root Span Event. This issue has
  now been fixed. These attributes can now be excluded from all Span Events
  using Config.Attributes.Exclude or Config.SpanEvents.Attributes.Exclude.

• Fixed an issue that caused Go's data race warnings to trigger in certain situations
  when using the newrelic.NewRoundTripper. There were no reports of actual data corruption,
  but now the warnings should be resolved. Thank you to @blixt for bringing this to our
  attention!

Release v3.5.0

New Features

• Added 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.

  As part of this change, the Go Agent now has an added dependency on gRPC.
  This is true whether or not you enable the Infinite Tracing feature. The gRPC dependencies include these two libraries:

  • github.com/golang/protobuf v1.3.3
  • google.golang.org/grpc v1.27.0

  You can see the changes in the go.mod file

Changes

• nrgin.Middleware
  uses
  Context.FullPath()
  for transaction names when using Gin version 1.5.0 or greater. Gin
  transactions were formerly named after the
  Context.HandlerName(),
  which uses reflection. This change improves transaction naming and reduces
  overhead. Please note that because your transaction names will change, you
  may have to update any related dashboards and alerts to match the new name.
  If you wish to continue using Context.HandlerName() for your transaction
  names, use
  nrgin.MiddlewareHandlerTxnNames
  instead.

  // Transactions previously named
  "GET main.handleGetUsers"
  // will be change to something like this match the full path
  "GET /user/:id"

  Note: As part of agent release v3.4.0, a v2.0.0 tag was added to the nrgin
  package. When using go modules however, it was impossible to install this
  latest version of nrgi

Release v3.4.0

New Features

• Attribute http.statusCode has been added to external span events
  representing the status code on an http response. This attribute will be
  included when added to an ExternalSegment in one of these three ways:

  1. Using
     NewRoundTripper
     with your http.Client
  2. Including the http.Response as a field on your
     ExternalSegment
  3. Using the new
     ExternalSegment.SetStatusCode
     API to set the status code directly

  To exclude the http.statusCode attribute from span events, update your
  agent configuration like so, where cfg is your newrelic.Config object.

  cfg.SpanEvents.Attributes.Exclude = append(cfg.SpanEvents.Attributes.Exclude, newrelic.SpanAttributeHTTPStatusCode)

• Error attributes error.class and error.message are now included on the
  span event in which the error was noticed, or on the root span if an error
  occurs in a transaction with no segments (no chid spans). Only the most recent error
  information is added to the attributes; prior errors on the same span are
  overwritten.

  To exclude the error.class and/or error.message attributes from span events, update your
  agent configuration like so, where cfg is your newrelic.Config object.

  cfg.SpanEvents.Attributes.Exclude = append(cfg.SpanEvents.Attributes.Exclude, newrelic.newrelic.SpanAttributeErrorClass, newrelic.SpanAttributeErrorMessage)

Changes

• Use
  Context.FullPath()
  for transaction names when using Gin version 1.5.0 or greater. Gin
  transactions were formerly named after the
  Context.HandlerName(),
  which uses reflection. This change improves transaction naming and reduces
  overhead. Please note that because your transaction names will change, you
  may have to update any related dashboards and alerts to match the new name.

  // Transactions previously named
  "GET main.handleGetUsers"
  // will be change to something like this match the full path
  "GET /user/:id"

Release 3.3.0

New Features

• Added support for GraphQL in two new integrations:

  • graph-gophers/graphql-go with v3/integrations/nrgraphgophers.
    • Documentation
    • Example
  • graphql-go/graphql with v3/integrations/nrgraphqlgo.
    • Documentation
    • Example

• Added database instrumentation support for snowflakedb/gosnowflake.

  • Documentation
  • Example

Changes

• When using newrelic.StartExternalSegment or newrelic.NewRoundTripper, if existing cross application tracing or distributed tracing headers are present on the request, they will be replaced instead of added.

• The FromContext API which allows you to pull a Transaction from a context.Context will no longer panic if the provided context is nil. In this case, a nil is returned.