chore(deps): Update module github.com/newrelic/go-agent/v3 to v3.14.1 (main)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/newrelic/go-agent/v3	require	minor	v3.13.0 -> v3.14.1

---

Release Notes

newrelic/go-agent

v3.14.1

Compare Source

3.14.1

Fixed

• A typographical error in the nrgrpc unit tests was fixed. Fixes Issue #​344.
  This updates the nrgrpc integration to version 1.3.1.

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.

v3.14.0

Compare Source

3.14.0

Fixed

• Integration tags and go.mod files for integrations were updated so that pkg.go.dev displays the documentation for each integration correctly.
• The nrgrpc server integration was reporting all non-OK grpc statuses as errors. This has now been changed so that only selected grpc status codes will be reported as errors. Others are shown (via transaction attributes) as "warnings" or "informational" messages. There is a built-in set of defaults as to which status codes are reported at which severity levels, but this may be overridden by the caller as desired. Also supports custom grpc error handling functions supplied by the user.
  • This is implemented by adding WithStatusHandler() options to the end of the UnaryServerInterceptor() and StreamServerInterceptor() calls, thus extending the capability of those functions while retaining the existing functionality and usage syntax for backward compatibility.
• Added advice on the recommended usage of the app.WaitForConnection() method. Fixes [https://github.com/newrelic/go-agent/issues/296]\(Issue #​296)

Added

• Added a convenience function to build distributed trace header set from a JSON string for use with the AcceptDistributedTraceHeaders() method. Normally, you must create a valid set of HTTP headers representing the trace identification information from the other trace so the new trace will be associated with it. This needs to be in a Go http.Header type value.
  • If working only in Go, this may be just fine as it is. However, if the other trace information came from another source, possibly in a different language or environment, it is often the case that the trace data is already presented to you in the form of a JSON string.
  • This new function, DistributedTraceHeadersFromJSON(), creates the required http.Header value from the JSON string without requiring manual effort on your part.
  • We also provide a new all-in-one method AcceptDistributedTraceHeadersFromJSON() to be used in place of AcceptDistributedTraceHeaders(). It accepts a JSON string rather than an http.Header, adding its trace info to the new transaction in one step.
  • Fixes [https://github.com/newrelic/go-agent/issues/331]\(Issue #​331)

Changed

• Improved the NR AWS SDK V2 integration to use the current transaction rather than the one passed in during middleware creation, if nil is passed into nrawssdk-v2.AppendMiddlewares. Thanks to @​HenriBeck for noticing and suggesting improvement, and thanks to @​nc-wittj for the fantastic PR! #​328

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.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.