Release 3.17.0 #531
Merged
Release 3.17.0 #531
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version has a fix that we need.
Added intergation for ms sql server
Merge branch 'nrecho-test' of https://github.com/mirackara/go-agent into nrecho-test
Update gin-gonic to version 1.7.7
Nrecho test fixed
Adds the ability to ingest and harvest log events that have been structured and formatted to the proper json spec. This is meant to be used by wrapper libraries for popular logging frameworks, and should not be called by users.
Modifies the agent to support passing log data from the new zerolog plugin into the harvest pool and sending that data to our servers.
Creates a suite of tests to measure and benchmark the performance of features of the Go agent at scale.
Json speed issue 505
gRPC attributes rename
Added integration for ms sql server with newrelic
Update nrgin go.mod to mitigate security issue in 3rd party dependency
Added noop operations for js/wasm build target
Zerolog in Context
Require 1.20.0 of aws-lambda-go
Revert "Added noop operations for js/wasm build target"
update aws gomod
Allows custom events to be configured by users and adds tests to verify changes.
clean up some style issues and exported functions that should be private
|
Mirac Kara seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
updates to release 3.17.0 of the agent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3.17.0
Added
* Adds support for logging metrics which shows the rate of log messages by severity in the Logs chart in the APM Summary view. This is enabled by default in this release.
* Adds support for forwarding application logs to New Relic. This automatically sends application logs that have been enriched to power APM logs in context. This is disabled by default in this release. This will be on by default in a future release.
* To learn more about APM logs in context see the documentation here.
* Includes the
RecordLogfunction for recording log data from a single log entry* An integrated plugin for zerolog to automatically ingest log data with the Go Agent.
* Resolves issue 178, issue 488, issue 489, issue 490, and issue 491 .
* This introduces the
nrmssqlintegration v1.0.0.Fixed
GrpcStatusLevel,GrpcStatusMessage, andGrpcStatusCodetogrpcStatusLevel,grpcStatusMessage, andgrpcStatusCoderespectively, to conform to existing naming conventions for New Relic agents. Fixes issue 492.go.modfor thenrginintegration to mitigate security issue in 3rd party dependency.go.modfor thenrawssdk-v1integration to properly reflect its dependency on version 3.16.0 of the Go Agent.go.modfor thenrlambdaintegration to requireaws-lambda-goversion 1.20.0. (PR 356; thanks MattWhelan!)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.