Logs release notesRSS

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.

More telemetry data with APM logs in context

Logs are more valuable in the context of the application, transaction, or error they belong to. Our latest APM agents support automatically adding context and forwarding logs without the need to install or maintain third-party software!

Your logs will automatically include attributes such as span.id, trace.id, hostname, entity.guid, entity.name, and more. This metadata links your logs to traces, spans, infrastructure data, and other telemetry, making it easier for you to troubleshoot without having to leave the UI page where you are investigating the issue.

For more information, see our documentation about APM logs in context and the agent-specific information for the following APM agents:

• Java logs in context procedures for agent v7.6.0 or higher
• .NET logs in context procedures for agent v9.7.0.0 or higher
• Ruby logs in context procedures for agent v8.6.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.

Logs are everywhere (no, really!)

We've released several enhancements throughout New Relic One to make it easy for you to see relevant logs from multiple pages in the UI. When you're trying to troubleshoot a problem for your app or its related entities and services, you won't need to search through thousands of logs.

By adding links to relevant logs directly in the context of your app's UI, you won't lose context of what you were tracking down. This includes:

• Logs counts and errors for your app's related entities from the right panel on APM's Summary menu
• See logs link for a selected trace from APM's Summary > Monitor > Distributed tracing menu
• See logs link for a selected error from APM's Summary > Events > Errors menu
• Log patterns and attributes for your app from APM's Summary > Triage > Logs menu

From here, you can go directly to the more detailed logs UI by clicking Open in logs. You can also go directly to the Logs UI from the top-level Explorer in New Relic One.

In addition, if you have not installed logs in context for hosts related to your app, you can install our infrastructure monitoring's log forwarder capabilities directly from the app's Summary > Triage > Logs menu. From there, you can click on the popup menu to go directy to the guided install.

Notes

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

Bug fixes

Sometimes our log forwarding functionality for Amazon Kinesis Data Firehose was prepending attributes with logEvent. For example, in some AWS logs you might see logEvent.message, logEvent.timestamp, etc. This prevented default JSON parsing and also applied the ingestion time rather than the timestamp. This bug has been fixed.

Notes

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

New public APIs

• Public APIs are now available for parsing and pipeline configuration, such as drop filters. For more information, try out NerdGraph, our GraphQL-format API explorer, at api.newrelic.com/graphiql. Also see our NerdGraph parsing rules tutorial and drop data tutorial.

Headerless HTTP ingest

• Added support for headerless HTTP log ingest. This enables Logs customers to send data to New Relic from sources that do not permit the customization of HTTP request headers (for example, Api-Key or X-License-Key). This approach is most often used when forwarding logs from cloud-based platforms.

More data, more power

• Increased maximum attribute value size. The Logs team recognizes that keeping all data from a log is extremely important, and so we are providing additional functionality to store more data and reduce the chances of truncation. Attributes can now store and display up to 128 kb, the first 4096 bytes of which are searchable. For more information, see our documentation about finding data in long logs (blobs) and the Log Event API.
• Added ARM support to our Helm-based Kubernetes integration.

Bug fixes

• Fixed several styling issues in Logs UI.
• Corrected typos on Add Your Data page.

Notes

In partnership with our customers, the New Relic log team has been rapidly innovating our log management capabilities since the initial release in 2019. Our goal is to give you the best log experience to advance observability and provide measurable impact to your business.

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