Logs release notesRSS

Handling of Unpaired UTF Surrogates

Previously, logs that contained surrogate characters, such as \uD800, were discarded and not ingested.

Changes

With this improvement, these logs can now be successfully ingested.

Notes

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

Enhanced AWS Lambda Log Processing with Request ID Injection

New Relic enhances log processing for AWS Lambda functions by ensuring that request IDs are consistently added to logs lacking default runtime annotations. This improves traceability and observability across Lambda invocations.

Changed

• Consistent Request ID Annotation: Logs from AWS Lambda functions now have request IDs added to every message using the UUID found in the first and last log entries. This ensures comprehensive traceability and completeness in log data, enabling more effective monitoring and debugging.

Notes

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

Support for Fluent Bit 3.2.7

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

Changed

• Infrastructure agent recommends Fluent Bit 3.2.7 packages
• Fluent Bit Output Plugin Docker image uses Fluent Bit 3.2.7
• 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.

New Feature: AWS Logs in Context

We are excited to introduce the new AWS Logs in Context feature in our latest release. This feature enhances log management by providing a seamless linkage between logs and their corresponding AWS resources (entities), including automatic entity creation and association, and seamless bidirectional navigation between entities and logs.

Added

• AWS Logs in Context: your AWS service logs will automatically be associated with the specific AWS resource (entity) that generated them. If the entity does not yet exist, the system will automatically create it. This features enables you to use the Entity Explorer to search for specific AWS resources and navigate quickly between logs and their generating entities. The following AWS entity types are currently supported:
  • Application Load Balancer (ALB)
  • Classic Load Balancer (ELB)
  • CloudFront Distribution
  • Elastic Beanstalk EC2 Instance
  • Lambda Function
  • Network Load Balancer (NLB)
  • Relational Database Service (RDS) Instance
  • S3 Bucket

Notes

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

Support for Fluent Bit 3.2.2

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

Changed

• Infrastructure agent recommends Fluent Bit 3.2.2 packages
• Fluent Bit Output Plugin Docker image uses Fluent Bit 3.2.2
• New Relic Logging Helm chart installs the new plugin image (newrelic-logging chart version 1.25.0)

Notes

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

OpenTelemetry: Support for complex data structures

New Relic now supports complex data structures in OTLP Logs. Checkout the details in the OTEL best practices docs.

Added

• Support complex data structures in OTLP Logs: Your LogRecord#body and LogRecord#attrbitues can hold non-primitive values, such as arrays and maps.

Notes

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

New Feature: Key-Value Parsing with Grok

We are excited to introduce key-value parsing with Grok in our latest release. This feature allows you to extract key-value pairs from your logs more efficiently, enhancing your log management capabilities.

Added

• Key-Value Parsing with Grok: You can now use Grok patterns to parse key-value pairs from your logs. This feature simplifies the extraction of structured data from unstructured log messages, making it easier to analyze and visualize your log data.

Notes

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

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.