Logs release notesRSS

Correctif pour la vulnérabilité CVE-2025-53643 dans la fonction Lambda aws-log-ingestion

La vulnérabilité CVE-2025-53643 est corrigée dans aws-log-ingestion lambda avec la dernière mise à jour.

Modifié

• Mise à jour de la bibliothèque aiohttp vers la version 3.13.2 et la version de poésie à 1.8.3 et la dépendance associée mise à jour

Remarques

Pour rester au courant des correctifs et améliorations les plus récents, abonnez-vous à notre flux RSS de Logs.

Support for .Net specific log payload formats

The user can now process .NET specific payloads more effectively.

Changed

• Introduced a new environment variable NEW_RELIC_FORMAT_LOGS to enable proper processing of .NET specific log payload formats.

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

Users will now receive Fluent Bit version 3.2.10. For more details, refer https://fluentbit.io/announcements/.

Changed

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

Notes

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

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.