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-KeyorX-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!
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.