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.
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 Logs RSS feed. More to come soon!
New public APIs
- In addition to the logs UI for data partition management, 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 NerdGraph tutorial.
- Parsing rules are also publicly accessible via the Log API. We already provide built-in parsing rulesets to facet or filter logs in useful ways. This in turn helps you build better charts and alerts.
- If you can't use log forwarders when collecting logs from CDNs, hardware devices, or managed services, you can use
syslogprotocols via a TCP endpoint.
Bug fixes
- Fixed link to see logs from the Fluentd forwarder.
- Fixed crash when browsing after using a saved view.
- Fixed scenario where logs in context for distributed tracing wouldn't work.
Changes
- Because of intermittent Fluent Bit build failures, SUSE will no longer be a supported platform for the infrastructure agent's log forwarder. We are working on adding SUSE support in the next six months.
- For tips on getting the most out of our changes to the logs UI, check out this workflow to explore your logs data.