<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Logs release notes]]></title><description><![CDATA[Logs release notes]]></description><link>https://docs.newrelic.com</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Apr 2026 16:13:59 GMT</lastBuildDate><atom:link href="https://docs.newrelic.com/docs/release-notes/logs-release-notes/feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Logs v210728]]></title><guid isPermaLink="false">TG9ncy0yMTA3Mjg=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-21-07-28</link><pubDate>Wed, 28 Jul 2021 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Moving forward, we will be summarizing the most recent fixes and enhancements captured in this ongoing changelog. To stay up to date, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;. More to come soon!&lt;/p&gt;
&lt;h3&gt;New public APIs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;In addition to the logs UI for &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/data-partitions/&quot;&gt;data partition management&lt;/a&gt;, you can now use our public API. Data partitions help you query more efficiently by scanning less unrelated data and returning results faster. To get started, see our &lt;a href=&quot;https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-data-partition-rules-tutorial/&quot;&gt;NerdGraph tutorial&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Parsing rules are also publicly accessible via the &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api/&quot;&gt;Log API&lt;/a&gt;. We already provide &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/built-log-parsing-rulesets/&quot;&gt;built-in parsing rulesets&lt;/a&gt; to facet or filter logs in useful ways. This in turn helps you build better charts and alerts.&lt;/li&gt;
&lt;li&gt;If you can&apos;t use log forwarders when collecting logs from CDNs, hardware devices, or managed services, you can use &lt;code&gt;syslog&lt;/code&gt; protocols via a &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/log-api/use-tcp-endpoint-forward-logs-new-relic/&quot;&gt;TCP endpoint&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Bug fixes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fixed link to see logs from the &lt;a href=&quot;https://docs.newrelic.com/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/fluentd-plugin-log-forwarding/&quot;&gt;Fluentd forwarder&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Fixed crash when browsing after using a &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/use-logs-ui/#saved-views&quot;&gt;saved view&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Fixed scenario where &lt;a href=&quot;https://docs.newrelic.com/docs/logs/enable-log-management-new-relic/configure-logs-context/configure-logs-context-apm-agents/&quot;&gt;logs in context for distributed tracing&lt;/a&gt; wouldn&apos;t work.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Because of intermittent Fluent Bit build failures, SUSE will no longer be a supported platform for the &lt;a href=&quot;https://docs.newrelic.com/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/&quot;&gt;infrastructure agent&apos;s log forwarder&lt;/a&gt;. We are working on adding SUSE support in the next six months.&lt;/li&gt;
&lt;li&gt;For tips on getting the most out of our changes to the logs UI, check out this &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/use-logs-ui/&quot;&gt;workflow to explore your logs data&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;</content:encoded><description>ReleasedOn: Wed, 28 Jul 2021 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v210830]]></title><guid isPermaLink="false">TG9ncy0yMTA4MzA=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-21-08-30</link><pubDate>Mon, 30 Aug 2021 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;New public APIs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Public APIs are now available for &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/parsing/&quot;&gt;parsing&lt;/a&gt; and pipeline configuration, such as &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/drop-data-drop-filter-rules/&quot;&gt;drop filters&lt;/a&gt;. For more information, try out NerdGraph, our GraphQL-format API explorer, at &lt;a href=&quot;https://api.newrelic.com/graphiql&quot;&gt;api.newrelic.com/graphiql&lt;/a&gt;. Also see our &lt;a href=&quot;https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-log-parsing-rules-tutorial/&quot;&gt;NerdGraph parsing rules tutorial&lt;/a&gt; and &lt;a href=&quot;https://docs.newrelic.com/docs/telemetry-data-platform/manage-data/drop-data-using-nerdgraph/&quot;&gt;drop data tutorial&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Headerless HTTP ingest&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added support for &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api/#query-parameters&quot;&gt;headerless HTTP log ingest&lt;/a&gt;. This enables Logs customers to send data to New Relic from sources that do not permit the customization of HTTP request headers (for example, &lt;code&gt;Api-Key&lt;/code&gt; or &lt;code&gt;X-License-Key&lt;/code&gt;). This approach is most often used when forwarding logs from cloud-based platforms.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;More data, more power&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;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 &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/ui-data/long-logs-blobs/&quot;&gt;finding data in long logs (blobs)&lt;/a&gt; and the &lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-management/log-api/log-event-data/&quot;&gt;Log Event API&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Added ARM support to our Helm-based &lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;Kubernetes integration&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Bug fixes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fixed several styling issues in Logs UI.&lt;/li&gt;
&lt;li&gt;Corrected typos on &lt;strong&gt;Add Your Data&lt;/strong&gt; page.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;. More to come soon!&lt;/p&gt;</content:encoded><description>ReleasedOn: Mon, 30 Aug 2021 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v220216]]></title><guid isPermaLink="false">TG9ncy0yMjAyMTY=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-22-02-16</link><pubDate>Wed, 16 Feb 2022 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Logs are everywhere (no, really!)&lt;/h3&gt;
&lt;p&gt;We&apos;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&apos;re trying to troubleshoot a problem for your app or its related entities and services, you won&apos;t need to search through thousands of logs.&lt;/p&gt;
&lt;div class=&quot;block-image image&quot;&gt;&lt;img src=&quot;https:/docs.newrelic.com/images/logs-rn0222.webp&quot; alt=&quot;Logs everywhere in New Relic One&quot;&gt;&lt;/div&gt;
&lt;p&gt;By adding links to relevant logs directly in the context of your app&apos;s UI, you won&apos;t lose context of what you were tracking down.  This includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Logs counts and errors for your app&apos;s related entities from the right panel on APM&apos;s &lt;strong&gt;Summary&lt;/strong&gt; menu&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;See logs&lt;/strong&gt; link for a selected trace from APM&apos;s &lt;strong&gt;Summary &gt; Monitor &gt; Distributed tracing&lt;/strong&gt; menu&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;See logs&lt;/strong&gt; link for a selected error from APM&apos;s &lt;strong&gt;Summary &gt; Events &gt; Errors&lt;/strong&gt; menu&lt;/li&gt;
&lt;li&gt;Log patterns and attributes for your app from APM&apos;s &lt;strong&gt;Summary &gt; Triage &gt; Logs&lt;/strong&gt; menu&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&quot;block-image image&quot;&gt;&lt;img src=&quot;https:/docs.newrelic.com/images/logs-rn-triage.webp&quot; alt=&quot;Detailed log info in APM&quot;&gt;&lt;/div&gt;
&lt;p&gt;From here, you can go directly to the more detailed logs UI by clicking &lt;strong&gt;Open in logs&lt;/strong&gt;. You can also go directly  to the Logs UI from the top-level Explorer in New Relic One.&lt;/p&gt;
&lt;p&gt;In addition, if you have not installed logs in context for hosts related to your app, you can install our infrastructure monitoring&apos;s log forwarder capabilities directly from the app&apos;s &lt;strong&gt;Summary &gt; Triage &gt; Logs&lt;/strong&gt; menu. From there, you can click on the popup menu to go directy to the guided install.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 16 Feb 2022 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v211213]]></title><guid isPermaLink="false">TG9ncy0yMTEyMTM=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-21-12-13</link><pubDate>Mon, 13 Dec 2021 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Bug fixes&lt;/h3&gt;
&lt;p&gt;Sometimes our log forwarding functionality for &lt;a href=&quot;https://docs.newrelic.com/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose&quot;&gt;Amazon Kinesis Data Firehose&lt;/a&gt; was prepending attributes with &lt;code&gt;logEvent&lt;/code&gt;. For example, in some AWS logs you might see &lt;code&gt;logEvent.message&lt;/code&gt;, &lt;code&gt;logEvent.timestamp&lt;/code&gt;, etc. This prevented default JSON parsing and also applied the ingestion time rather than the timestamp. This bug has been fixed.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Mon, 13 Dec 2021 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v220404]]></title><guid isPermaLink="false">TG9ncy0yMjA0MDQ=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-22-04-04</link><pubDate>Mon, 04 Apr 2022 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;More telemetry data with APM logs in context&lt;/h3&gt;
&lt;p&gt;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!&lt;/p&gt;
&lt;p&gt;Your logs will automatically include attributes such as &lt;code&gt;span.id&lt;/code&gt;, &lt;code&gt;trace.id&lt;/code&gt;, &lt;code&gt;hostname&lt;/code&gt;, &lt;code&gt;entity.guid&lt;/code&gt;, &lt;code&gt;entity.name&lt;/code&gt;, 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.&lt;/p&gt;
&lt;p&gt;For more information, see our documentation about &lt;a href=&quot;https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/get-started-logs-context&quot;&gt;APM logs in context&lt;/a&gt; and the agent-specific information for the following APM agents:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/java-configure-logs-context-all/&quot;&gt;&lt;strong&gt;Java&lt;/strong&gt; logs in context procedures&lt;/a&gt; for agent &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/agent-release-notes/java-release-notes/java-agent-760&quot;&gt;v7.6.0 or higher&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/net-configure-logs-context-all/&quot;&gt;&lt;strong&gt;.NET&lt;/strong&gt; logs in context procedures&lt;/a&gt; for agent &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/agent-release-notes/net-release-notes/net-agent-9700&quot;&gt;v9.7.0.0 or higher&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/configure-logs-context-ruby/&quot;&gt;&lt;strong&gt;Ruby&lt;/strong&gt; logs in context procedures&lt;/a&gt; for agent &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-860&quot;&gt;v8.6.0 or higher&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If your APM agent doesn&apos;t support our automatic logs in context solution yet, you can continue to use our &lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/logs-in-context/&quot;&gt;manual logs in context solutions&lt;/a&gt;, and forward your logs via our infrastructure agent or supported third-party forwarder.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Mon, 04 Apr 2022 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v220518]]></title><guid isPermaLink="false">TG9ncy0yMjA1MTg=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-22-05-18</link><pubDate>Wed, 18 May 2022 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Enhanced functionality for log tables in dashboards&lt;/h3&gt;
&lt;p&gt;We&apos;ve made it even easier for you to explore your logs data as table widgets in dashboards. After you &lt;a href=&quot;https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards#dashboards-create&quot;&gt;create your dashboard&lt;/a&gt;, you can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use standard dashboard widget functions, such as copying, editing, deleting, etc.&lt;/li&gt;
&lt;li&gt;Click any log row to show details about it.&lt;/li&gt;
&lt;li&gt;Update your query to add more columns.&lt;/li&gt;
&lt;li&gt;Query log data from other available accounts, and add more charts (for example, as comparative data) to your dashboard.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Open in logs&lt;/strong&gt; to go directly to the &lt;a href=&quot;https://docs.newrelic.com/docs/logs/ui-data/use-logs-ui&quot;&gt;&lt;strong&gt;Logs&lt;/strong&gt; UI&lt;/a&gt; for additional troubleshooting.&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&quot;block-image image&quot;&gt;&lt;img src=&quot;https:/docs.newrelic.com/images/logs-dashboards-052722.webp&quot; alt=&quot;Screenshot of log tables in Dashboards UI&quot;&gt;&lt;/div&gt;
&lt;h3&gt;APM logs in context available for Node.js&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/get-started-logs-context&quot;&gt;APM logs in context&lt;/a&gt; is now available for Node.js! (It was also released earlier this month for Java, .NET, and Ruby.) For more information, see our &lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/configure-logs-context-nodejs&quot;&gt;Node.js logs in context procedures&lt;/a&gt; for agent &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/agent-release-notes/nodejs-release-notes/&quot;&gt;v8.11.0 or higher&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If your APM agent doesn&apos;t support our automatic logs in context solution yet, you can continue to use our &lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/logs-in-context/&quot;&gt;manual logs in context solutions&lt;/a&gt;, and forward your logs via our infrastructure agent or supported third-party forwarder.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 18 May 2022 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v240812]]></title><guid isPermaLink="false">TG9ncy0yNDA4MTI=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-08-12</link><pubDate>Mon, 12 Aug 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Ubuntu 24.04 and SUSE 15.5(x86_64)&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;p&gt;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 &lt;a href=&quot;https://docs.newrelic.com/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/&quot;&gt;infrastructure agent&apos;s log forwarder&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Mon, 12 Aug 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v240911]]></title><guid isPermaLink="false">TG9ncy0yNDA5MTE=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-09-11</link><pubDate>Wed, 11 Sep 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Amazon Linux 2023 (AArch64)&lt;/h3&gt;
&lt;p&gt;The infrastructure agent now supports Amazon Linux 2023 (AArch64). This enhancement ensures broader compatibility and better performance on these platforms.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;p&gt;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 &lt;a href=&quot;https://docs.newrelic.com/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/&quot;&gt;infrastructure agent&apos;s log forwarder&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 11 Sep 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v240912]]></title><guid isPermaLink="false">TG9ncy0yNDA5MTI=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-09-12</link><pubDate>Thu, 12 Sep 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Update to AWS-log-ingestion Lambda function&lt;/h3&gt;
&lt;p&gt;Users no longer need to manually enable logging for New Relic. The &lt;code&gt;NRLoggingEnabled&lt;/code&gt; parameter is now set to &lt;code&gt;true&lt;/code&gt; by default.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;p&gt;The default value of the &lt;code&gt;NRLoggingEnabled&lt;/code&gt; parameter for the New Relic Lambda function has been changed from &lt;code&gt;false&lt;/code&gt; to &lt;code&gt;true&lt;/code&gt;. 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.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Thu, 12 Sep 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v240610]]></title><guid isPermaLink="false">TG9ncy0yNDA2MTA=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-06-10</link><pubDate>Mon, 10 Jun 2024 00:00:00 +0000</pubDate><content:encoded>&lt;p&gt;New versions of the New Relic Logs integrations have been released with a fix for &lt;a href=&quot;https://nvd.nist.gov/vuln/detail/CVE-2024-4323&quot;&gt;CVE-2024-4323&lt;/a&gt;. New Relic recommends you follow the procedures below to update the relevant logs integrations:&lt;/p&gt;
&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;p&gt;Integration&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;Action Required&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;p&gt;Linux Infrastructure Agent&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;Upgrade the Infrastructure Agent to version 1.52.3 or later, &lt;strong&gt;AND&lt;/strong&gt; update Fluent Bit to version 3.0.4 or later&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;p&gt;Kubernetes Plugin&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;Upgrade using either &lt;a href=&quot;https://github.com/newrelic/helm-charts/releases/tag/newrelic-logging-1.22.0&quot;&gt;newrelic-logging-1.22.0&lt;/a&gt; or &lt;a href=&quot;https://github.com/newrelic/helm-charts/releases/tag/nri-bundle-5.0.80&quot;&gt;nri-bundle-5.0.80&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;p&gt;Fluent Bit Output Plugin&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;Update to version 2.0.0&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;
&lt;h2&gt;Changed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Update Fluent Bit output plugin to version 1.22.0 as a fix for &lt;a href=&quot;https://nvd.nist.gov/vuln/detail/CVE-2024-4323&quot;&gt;CVE-2024-4323&lt;/a&gt;, which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution.&lt;/li&gt;
&lt;li&gt;Update nri-bundle to version 5.0.80 as fix for &lt;a href=&quot;https://nvd.nist.gov/vuln/detail/CVE-2024-4323&quot;&gt;CVE-2024-4323&lt;/a&gt;, which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution.&lt;/li&gt;
&lt;li&gt;Update Fluent Bit to version 3.0.4 as fix for &lt;a href=&quot;https://nvd.nist.gov/vuln/detail/CVE-2024-4323&quot;&gt;CVE-2024-4323&lt;/a&gt;, which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution.&lt;/li&gt;
&lt;/ul&gt;</content:encoded><description>ReleasedOn: Mon, 10 Jun 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v241218]]></title><guid isPermaLink="false">TG9ncy0yNDEyMTg=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-12-18</link><pubDate>Wed, 18 Dec 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Accelerated AWS logs forwarding with New Relic&apos;s One-Step Observability&lt;/h3&gt;
&lt;p&gt;New Relic&apos;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.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Simplified logs onboarding with cloudFormation template:&lt;/strong&gt; Effortless set up experience for both logs and metrics using ready-made templates that simplify the deployment of AWS resources.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enhanced operational Efficiency:&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Advanced Security:&lt;/strong&gt;  New Relic&apos;s API keys can securely stored in AWS Secrets Management, for enhances security posture.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 18 Dec 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v241211]]></title><guid isPermaLink="false">TG9ncy0yNDEyMTE=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-12-11</link><pubDate>Wed, 11 Dec 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Enhanced Syslog License Key Handling&lt;/h3&gt;
&lt;p&gt;Users can now send the license key as part of the syslog message by prefixing it with &lt;code&gt;nrLicenseKey=&amp;#x3C;LICENSE_KEY&gt;&lt;/code&gt;.
With this enhancement, syslog integration is compatible with more platforms that don&apos;t permit modification of the syslog message format.&lt;/p&gt;
&lt;h3&gt;Related Documentation&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://docs.newrelic.com/docs/logs/log-api/use-tcp-endpoint-forward-logs-new-relic/#forwarders-that-doesnt-allow-to-modify-the-syslog-format&quot;&gt;Use TCP endpoint to forward logs to New Relic&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 11 Dec 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v241031]]></title><guid isPermaLink="false">TG9ncy0yNDEwMzE=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-10-31</link><pubDate>Thu, 31 Oct 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Fluent Bit 3.1.9&lt;/h3&gt;
&lt;p&gt;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 &lt;a href=&quot;https://fluentbit.io/announcements/&quot;&gt;https://fluentbit.io/announcements/&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Infrastructure agent recommends Fluent Bit 3.1.9 packages&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://hub.docker.com/r/newrelic/newrelic-fluentbit-output&quot;&gt;Fluent Bit Output Plugin Docker image&lt;/a&gt; uses Fluent Bit 3.1.9&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;New Relic Logging Helm chart&lt;/a&gt; installs the new plugin image&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Thu, 31 Oct 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250110]]></title><guid isPermaLink="false">TG9ncy0yNTAxMTA=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-01-10</link><pubDate>Fri, 10 Jan 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;New Feature: Key-Value Parsing with Grok&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Key-Value Parsing with Grok&lt;/strong&gt;: 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.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Fri, 10 Jan 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v241219]]></title><guid isPermaLink="false">TG9ncy0yNDEyMTk=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-12-19</link><pubDate>Thu, 19 Dec 2024 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Removal of aws.region, aws.realm, aws.accountId and plugin.type attributes for the new AWS logs onboarding integrations&lt;/h3&gt;
&lt;p&gt;The recent release of New Relic&apos;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.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The AWS Lambda and Firehose log shipping integrations &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-12-18&quot;&gt;released on December 18th 2024&lt;/a&gt; will no longer include the &lt;code&gt;aws.region&lt;/code&gt;, &lt;code&gt;aws.realm&lt;/code&gt; and &lt;code&gt;aws.accountId&lt;/code&gt; attributes in the ingested logs. These attributes, meant for internal use in the Logs product, and shouldn&apos;t appear as attributes on log data.&lt;/li&gt;
&lt;li&gt;The Firehose log shipping integration &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-24-12-18&quot;&gt;released on December 18th 2024&lt;/a&gt; shouldn&apos;t have included a &lt;code&gt;plugin.type: &quot;aws-firehose&quot;&lt;/code&gt; attribute in the ingested logs. We&apos;re removing this attribute in favor of the newly introduced &lt;code&gt;instrumentation.provider: &quot;aws&quot;&lt;/code&gt; and &lt;code&gt;instrumentation.name: &quot;firehose&quot;&lt;/code&gt; attributes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Thu, 19 Dec 2024 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250217]]></title><guid isPermaLink="false">TG9ncy0yNTAyMTc=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-02-17</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;OpenTelemetry: Support for complex data structures&lt;/h3&gt;
&lt;p&gt;New Relic now supports complex data structures in OTLP Logs. Checkout the details in the &lt;a href=&quot;https://docs.newrelic.com/docs/opentelemetry/best-practices/opentelemetry-best-practices-logs&quot;&gt;OTEL best practices docs&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Support complex data structures in OTLP Logs&lt;/strong&gt;: Your &lt;code&gt;LogRecord#body&lt;/code&gt; and &lt;code&gt;LogRecord#attrbitues&lt;/code&gt; can hold non-primitive values, such as arrays and &lt;a href=&quot;https://opentelemetry.io/docs/specs/otel/logs/data-model/#type-mapstring-any&quot;&gt;maps&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Mon, 17 Feb 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250227]]></title><guid isPermaLink="false">TG9ncy0yNTAyMjc=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-02-27</link><pubDate>Thu, 27 Feb 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Fluent Bit 3.2.7&lt;/h3&gt;
&lt;p&gt;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 &lt;a href=&quot;https://fluentbit.io/announcements/&quot;&gt;https://fluentbit.io/announcements/&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Infrastructure agent recommends Fluent Bit 3.2.7 packages&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://hub.docker.com/r/newrelic/newrelic-fluentbit-output&quot;&gt;Fluent Bit Output Plugin Docker image&lt;/a&gt; uses Fluent Bit 3.2.7&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;New Relic Logging Helm chart&lt;/a&gt; installs the new plugin image&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Thu, 27 Feb 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250226]]></title><guid isPermaLink="false">TG9ncy0yNTAyMjY=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-02-26</link><pubDate>Wed, 26 Feb 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;New Feature: AWS Logs in Context&lt;/h3&gt;
&lt;p&gt;We are excited to introduce the new &lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/aws-logs-in-context/&quot;&gt;AWS Logs in Context&lt;/a&gt; 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.&lt;/p&gt;
&lt;h3&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href=&quot;https://docs.newrelic.com/docs/logs/logs-context/aws-logs-in-context/&quot;&gt;AWS Logs in Context&lt;/a&gt;&lt;/strong&gt;: 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:
&lt;ul&gt;
&lt;li&gt;Application Load Balancer (ALB)&lt;/li&gt;
&lt;li&gt;Classic Load Balancer (ELB)&lt;/li&gt;
&lt;li&gt;CloudFront Distribution&lt;/li&gt;
&lt;li&gt;Elastic Beanstalk EC2 Instance&lt;/li&gt;
&lt;li&gt;Lambda Function&lt;/li&gt;
&lt;li&gt;Network Load Balancer (NLB)&lt;/li&gt;
&lt;li&gt;Relational Database Service (RDS) Instance&lt;/li&gt;
&lt;li&gt;S3 Bucket&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 26 Feb 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250220]]></title><guid isPermaLink="false">TG9ncy0yNTAyMjA=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-02-20</link><pubDate>Thu, 20 Feb 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Fluent Bit 3.2.2&lt;/h3&gt;
&lt;p&gt;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 &lt;a href=&quot;https://fluentbit.io/announcements/&quot;&gt;https://fluentbit.io/announcements/&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Infrastructure agent recommends Fluent Bit 3.2.2 packages&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://hub.docker.com/r/newrelic/newrelic-fluentbit-output&quot;&gt;Fluent Bit Output Plugin Docker image&lt;/a&gt; uses Fluent Bit 3.2.2&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;New Relic Logging Helm chart&lt;/a&gt; installs the new plugin image (newrelic-logging chart version 1.25.0)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Thu, 20 Feb 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250402]]></title><guid isPermaLink="false">TG9ncy0yNTA0MDI=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-04-02</link><pubDate>Wed, 02 Apr 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Handling of Unpaired UTF Surrogates&lt;/h3&gt;
&lt;p&gt;Previously, logs that contained surrogate characters, such as &lt;code&gt;\uD800&lt;/code&gt;, were discarded and not ingested.&lt;/p&gt;
&lt;h3&gt;Changes&lt;/h3&gt;
&lt;p&gt;With this improvement, these logs can now be successfully ingested.&lt;/p&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the latest fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Wed, 02 Apr 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250401]]></title><guid isPermaLink="false">TG9ncy0yNTA0MDE=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-04-01</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Enhanced AWS Lambda Log Processing with Request ID Injection&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Consistent Request ID Annotation:&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Tue, 01 Apr 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v250512]]></title><guid isPermaLink="false">TG9ncy0yNTA1MTI=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-05-12</link><pubDate>Mon, 12 May 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Fluent Bit 3.2.10&lt;/h3&gt;
&lt;p&gt;Users will now receive Fluent Bit version 3.2.10. For more details, refer &lt;a href=&quot;https://fluentbit.io/announcements/&quot;&gt;https://fluentbit.io/announcements/&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Infrastructure agent recommends Fluent Bit 3.2.10 packages.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://hub.docker.com/r/newrelic/newrelic-fluentbit-output&quot;&gt;Fluent Bit Output Plugin Docker image&lt;/a&gt; uses Fluent Bit 3.2.10.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;New Relic Logging Helm chart&lt;/a&gt; installs the new plugin image (newrelic-logging chart version 1.27.0)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Mon, 12 May 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v251120]]></title><guid isPermaLink="false">TG9ncy0yNTExMjA=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-11-20</link><pubDate>Thu, 20 Nov 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Fix for CVE-2025-53643 in aws-log-ingestion lambda&lt;/h3&gt;
&lt;p&gt;With the latest release CVE-2025-53643 is fixed in aws-log-ingestion lambda&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Updated the aiohttp library to 3.13.2 and poetry version to 1.8.3 and updated the related dependencies&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Thu, 20 Nov 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v251104]]></title><guid isPermaLink="false">TG9ncy0yNTExMDQ=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-11-04</link><pubDate>Tue, 04 Nov 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for .Net specific log payload formats&lt;/h3&gt;
&lt;p&gt;The user can now process .NET specific payloads more effectively.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Introduced a new environment variable &lt;code&gt;NEW_RELIC_FORMAT_LOGS&lt;/code&gt; to enable proper processing of &lt;code&gt;.NET&lt;/code&gt; specific log payload formats.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Tue, 04 Nov 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v251209]]></title><guid isPermaLink="false">TG9ncy0yNTEyMDk=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-25-12-09</link><pubDate>Tue, 09 Dec 2025 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Fluent Bit 4.2.0&lt;/h3&gt;
&lt;p&gt;Users will now receive Fluent Bit version 4.2.0. For more details, refer &lt;a href=&quot;https://fluentbit.io/announcements/&quot;&gt;https://fluentbit.io/announcements/&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Infrastructure agent recommends Fluent Bit 4.2.0 packages.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://hub.docker.com/r/newrelic/newrelic-fluentbit-output&quot;&gt;Fluent Bit Output Plugin Docker image&lt;/a&gt; uses Fluent Bit 4.2.0.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;New Relic Logging Helm chart&lt;/a&gt; installs the new plugin image (newrelic-logging chart version 1.33.0)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Tue, 09 Dec 2025 00:00:00 +0000.</description></item><item><title><![CDATA[Logs v260217]]></title><guid isPermaLink="false">TG9ncy0yNjAyMTc=</guid><link>https://docs.newrelic.com/docs/release-notes/logs-release-notes/logs-26-02-17</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><content:encoded>&lt;h3&gt;Support for Fluent Bit 4.2.2&lt;/h3&gt;
&lt;p&gt;Users will now receive Fluent Bit version 4.2.2. For more details, refer to the &lt;a href=&quot;https://fluentbit.io/announcements/&quot;&gt;Fluent Bit announcements&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This release includes New Relic Fluent Bit Output Plugin 3.4.0 with critical security updates and platform compatibility improvements.&lt;/p&gt;
&lt;h3&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Support for SLES 15.6 and 15.7&lt;/li&gt;
&lt;li&gt;New Relic Fluent Bit Output Plugin 3.4.0 with enhanced security and compatibility&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The Infrastructure agent recommends Fluent Bit 4.2.2 packages&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://hub.docker.com/r/newrelic/newrelic-fluentbit-output&quot;&gt;Fluent Bit Output Plugin Docker image&lt;/a&gt; uses Fluent Bit 4.2.2 with output plugin 3.4.0&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging&quot;&gt;New Relic Logging Helm chart&lt;/a&gt; installs the new plugin image (newrelic-logging chart version 1.35.0)&lt;/li&gt;
&lt;li&gt;aws-for-fluent-bit base image updated from 3.1.0 to 3.2.1&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;GLIBC compatibility issues on RHEL8 and Amazon Linux 2 using Zig cross-compilation targeting GLIBC 2.17&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Notes&lt;/h3&gt;
&lt;p&gt;To stay up to date with the most recent fixes and enhancements, subscribe to our &lt;a href=&quot;https://docs.newrelic.com/docs/release-notes/logs-release-notes/&quot;&gt;Logs RSS feed&lt;/a&gt;.&lt;/p&gt;</content:encoded><description>ReleasedOn: Tue, 17 Feb 2026 00:00:00 +0000.</description></item></channel></rss>