-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
31 additions
and
0 deletions.
There are no files selected for viewing
31 changes: 31 additions & 0 deletions
31
...ent/docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-37-0.mdx
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
subject: Go agent | ||
releaseDate: '2025-02-026' | ||
version: 3.37.0 | ||
downloadLink: 'https://github.com/newrelic/go-agent/tree/v3.37.0' | ||
features: ["Created a 2.0 version of slog integration","Now custom application tags (labels) may be added to all forwarded log events","Added memory allocation limit detection/response mechanism to facilitate calling custom functions to perform application-specific resource management functionality"] | ||
bugs: [] | ||
security: [] | ||
--- | ||
|
||
<Callout variant="important"> | ||
We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about [keeping your agent up to date](/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/). | ||
</Callout> | ||
|
||
## 3.37.0 | ||
### Added | ||
- Implemented a new approach to integrating New Relic with SLOG that is more lightweight, out of the way, and collects richer data. These changes have been constructed to be completely backwards-compatible with v1 of nrslog. Changes include: | ||
- Wrapping slog.Handler objects with errors to allow users to handle invalid use cases | ||
- A complete rework of log enrichment so that New Relic linking metadata does not invalidate JSON, BSON, or YAML scanners. This new approach will instead inject the linking metadata as a key-value pair. | ||
- Complete support for With(), WithGroup(), and attributes for automatic instrumentation. | ||
- Performance operations. | ||
- Robust testing (close to 90% coverage). | ||
- *This updates logcontext-v2/nrslog to v1.4.0.* | ||
- Now custom application tags (labels) may be added to all forwarded log events. | ||
- Enabled if ConfigAppLogForwardingLabelsEnabled(true) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_ENABLED=TRUE | ||
- May exclude labels named in ConfigAppLogForwardingLabelsExclude("label1","label2",...) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_EXCLUDE="label1,label2,..." | ||
- Labels are defined via ConfigLabels(...) or NEW_RELIC_LABELS | ||
- Added memory allocation limit detection/response mechanism to facilitate calling custom functions to perform application-specific resource management functionality, report custom metrics or events, or take other appropriate actions, in response to rising heap memory size. | ||
### Support statement | ||
We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. | ||
See the [Go agent EOL Policy](/docs/apm/agents/go-agent/get-started/go-agent-eol-policy) for details about supported versions of the Go agent and third-party components. |