Logs release notesRSS

Removal of aws.region, aws.realm, aws.accountId and plugin.type attributes for the new AWS logs onboarding integrations

The recent release of New Relic's one-step observability for AWS services logs included some unwanted attributes in the ingested logs. This issue has been resolved in the current release.

Changed

• The AWS Lambda and Firehose log shipping integrations released on December 18th 2024 will no longer include the aws.region, aws.realm and aws.accountId attributes in the ingested logs. These attributes, meant for internal use in the Logs product, and shouldn't appear as attributes on log data.
• The Firehose log shipping integration released on December 18th 2024 shouldn't have included a plugin.type: "aws-firehose" attribute in the ingested logs. We're removing this attribute in favor of the newly introduced instrumentation.provider: "aws" and instrumentation.name: "firehose" attributes.

Notes

To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed.

Accelerated AWS logs forwarding with New Relic's One-Step Observability

New Relic's one-step observability now includes accelerated AWS services logs onboarding. This enhanced AWS integration offers experienced and new New Relic users a seamless and flexible experience for onboarding logs and metrics within minutes—all in a streamlined workflow.

Changed

• Simplified logs onboarding with cloudFormation template: Effortless set up experience for both logs and metrics using ready-made templates that simplify the deployment of AWS resources.
• Enhanced operational Efficiency: In a single onboarding workflow users can set up log forwarding from many sinks (CloudWatch or S3), using various paths (Lambda-based or Kinesis integration), and setting up triggers for up to 40 S3 buckets and log groups, all in one go.
• Advanced Security: New Relic's API keys can securely stored in AWS Secrets Management, for enhances security posture.

Notes

To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed.

Enhanced Syslog License Key Handling

Users can now send the license key as part of the syslog message by prefixing it with nrLicenseKey=<LICENSE_KEY>. With this enhancement, syslog integration is compatible with more platforms that don't permit modification of the syslog message format.

Related Documentation

Use TCP endpoint to forward logs to New Relic

Notes

To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed.

Support for Fluent Bit 3.1.9

Users that rely on Fluent Bit to collect and forward logs to New Relic will now receive the latest available version, 3.1.9, which includes fixes for multiple known vulnerabilities. For more details, please reference https://fluentbit.io/announcements/.

Changed

• Infrastructure agent recommends Fluent Bit 3.1.9 packages
• Fluent Bit Output Plugin Docker image uses Fluent Bit 3.1.9
• New Relic Logging Helm chart installs the new plugin image

Notes

To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed.

Update to AWS-log-ingestion Lambda function

Users no longer need to manually enable logging for New Relic. The NRLoggingEnabled parameter is now set to true by default.

Changed

The default value of the NRLoggingEnabled parameter for the New Relic Lambda function has been changed from false to true. Users were required to manually enable this parameter to forward logs to New Relic, adding an extra step to the setup process. This change simplifies the setup process and ensures logs are automatically sent to New Relic.

Notes

To stay up to date the most recent fixes and enhancements, subscribe to our Logs RSS feed.

Support for Amazon Linux 2023 (AArch64)

The infrastructure agent now supports Amazon Linux 2023 (AArch64). This enhancement ensures broader compatibility and better performance on these platforms.

Changed

When users attempt to install the Infrastructure Agent from Add Integrations in New Relic, the installation process now correctly includes the necessary definitions for Amazon Linux 2023 (AArch64). Previously, logs-integration support was not available for these platforms. This issue has now been resolved, ensuring Fluent Bit is correctly installed on these platforms. This guarantees that logs are properly forwarded to New Relic, maintaining seamless log monitoring and analysis. To see all supported OS distributions for the Infrastructure Agent, please refer to infrastructure agent's log forwarder.

Notes

To stay up to date the most recent fixes and enhancements, subscribe to our Logs RSS feed.

Support for Ubuntu 24.04 and SUSE 15.5(x86_64)

The Infrastructure Agent now supports Ubuntu 24.04 and SUSE 15.5(x86_64). This enhancement ensures broader compatibility and better performance on these platforms.

Changed

When users attempt to install the Infrastructure Agent from Add Integrations in New Relic, the installation process now correctly includes the necessary definitions for Ubuntu 24.04 and SUSE 15.5 (x86_64). Previously, logs-integration support was not available for these platforms. This issue has now been resolved, ensuring Fluent Bit is correctly installed on these platforms. This guarantees that logs are properly forwarded to New Relic, maintaining seamless log monitoring and analysis. To see all supported OS distributions for the Infrastructure Agent, please refer to infrastructure agent's log forwarder.

Notes

To stay up to date the most recent fixes and enhancements, subscribe to our Logs RSS feed.

New versions of the New Relic Logs integrations have been released with a fix for CVE-2024-4323. New Relic recommends you follow the procedures below to update the relevant logs integrations:

Changed

• Update Fluent Bit output plugin to version 1.22.0 as a fix for CVE-2024-4323, which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution.
• Update nri-bundle to version 5.0.80 as fix for CVE-2024-4323, which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution.
• Update Fluent Bit to version 3.0.4 as fix for CVE-2024-4323, which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution.

Enhanced functionality for log tables in dashboards

We've made it even easier for you to explore your logs data as table widgets in dashboards. After you create your dashboard, you can:

• Use standard dashboard widget functions, such as copying, editing, deleting, etc.
• Click any log row to show details about it.
• Update your query to add more columns.
• Query log data from other available accounts, and add more charts (for example, as comparative data) to your dashboard.
• Click Open in logs to go directly to the Logs UI for additional troubleshooting.

APM logs in context available for Node.js

APM logs in context is now available for Node.js! (It was also released earlier this month for Java, .NET, and Ruby.) For more information, see our Node.js logs in context procedures for agent v8.11.0 or higher.

If your APM agent doesn't support our automatic logs in context solution yet, you can continue to use our manual logs in context solutions, and forward your logs via our infrastructure agent or supported third-party forwarder.

Notes

To stay up to date the most recent fixes and enhancements, subscribe to our Logs RSS feed.