Bump github.com/newrelic/go-agent/v3 from 3.13.0 to 3.15.0

[dependabot]

Bumps github.com/newrelic/go-agent/v3 from 3.13.0 to 3.15.0.

Release notes

Sourced from github.com/newrelic/go-agent/v3's releases.

Release v3.15.0

3.15.0

Fixed

• Updated mongodb driver version to 1.5.1 to fix security issue in external dependency. Fixes [Issue #358](newrelic/go-agent#358) and [Issue #370](newrelic/go-agent#370).

• Updated the go.mod file in the nrgin integration to require version 1.7.0 of the github.com/gin-gonic/gin package. This addresses CVE-2020-28483 which documents a vulnerability in versions of github.com/gin-gonic/gin earlier than 1.7.0.

Added

• New integration nrpgx added to provide the same functionality for instrumenting Postgres database queries as the existing nrpq integration, but using the pgx driver instead. This only covers (at present) the use case of the pgx driver with the standard library database/sql. Fixes [Issue #142](newrelic/go-agent#142) and [Issue #292](newrelic/go-agent#292)

Changed

• Enhanced debugging logs so that New Relic license keys are redacted from the log output. Fixes [Issue #353](newrelic/go-agent#353).

• Updated the advice in GUIDE.md to have correct go get commands with explicit reference to v3.

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.14.1

3.14.1

Fixed

• A typographical error in the nrgrpc unit tests was fixed. Fixes [Issue #344](newrelic/go-agent#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.

Release v3.14.0

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-redirect.dependabot.com/Add advice on correct usage of WaitForConnection function. newrelic/go-agent#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-redirect.dependabot.com/nrgrpc integration is now reporting non-errors as errors in the UI newrelic/go-agent#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

... (truncated)

Changelog

Sourced from github.com/newrelic/go-agent/v3's changelog.

3.15.0

Fixed

• Updated mongodb driver version to 1.5.1 to fix security issue in external dependency. Fixes [Issue #358](newrelic/go-agent#358) and [Issue #370](newrelic/go-agent#370).

• Updated the go.mod file in the nrgin integration to require version 1.7.0 of the github.com/gin-gonic/gin package. This addresses CVE-2020-28483 which documents a vulnerability in versions of github.com/gin-gonic/gin earlier than 1.7.0.

Added

• New integration nrpgx added to provide the same functionality for instrumenting Postgres database queries as the existing nrpq integration, but using the pgx driver instead. This only covers (at present) the use case of the pgx driver with the standard library database/sql. Fixes [Issue #142](newrelic/go-agent#142) and [Issue #292](newrelic/go-agent#292)

Changed

• Enhanced debugging logs so that New Relic license keys are redacted from the log output. Fixes [Issue #353](newrelic/go-agent#353).

• Updated the advice in GUIDE.md to have correct go get commands with explicit reference to v3.

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.

3.14.1

Fixed

• A typographical error in the nrgrpc unit tests was fixed. Fixes [Issue #344](newrelic/go-agent#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.

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 [Issue #296](newrelic/go-agent#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 [Issue #331](newrelic/go-agent#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.

Commits

• 779fa03 Merge pull request #374 from newrelic/develop
• 6459661 Merge pull request #372 from nr-swilloughby/3.15rel
• 9faa326 updated README
• a81fb17 updated README
• a2ec959 correction to url
• cfbd88b updated version
• 5ccbd29 Merge pull request #357 from RichVanderwal/update-gin-dependency
• 4d3f246 Merge pull request #370 from RichVanderwal/fix-mongo-test
• 3f2bbd3 slight tweak to changelog
• f7cd6b3 slight tweak to changelog
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #16.