Our log management capabilities help you to collect, process, explore, query, and alert on your log data. To get your logs into New Relic, you can use any of these options:
If you want to do this...
Use any of these log forwarding options
Collect logs that are written to a local file on disk
Use our solutions to forward logs from operating systems, including our infrastructure monitoring agent, Fluent Bit, Fluentd, Logstash, and syslog/TCP. Use our guided install for infrastructure monitoring as a lightweight data collector for your apps' and hosts' logs.
Use your cloud forwarding platform
Collect logs from apps running in Docker containers, either standalone or when using Kubernetes
Collect logs directly from your apps, regardless of where they are hosted
Use our APM agent and infrastructure monitoring agent. Let your app's APM agent forward log data directly to New Relic with APM logs in context. No need to install or maintain additional third-party software!
Do something else
If our log forwarding options don't meet your needs, you can:
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. Here's how:
- If you don't have one already, create a New Relic account. It's free, forever.
- Have your New Relic account's license key.
- Install a compatible log forwarder.
- Ensure that outbound connectivity on TCP port 443 is allowed to the CIDR range that matches your region.
- Depending on where your account data is stored in New Relic, use the DNS name
- If applicable, configure your app's APM agent by following the manual logs in context procedures.
We provide several solutions to forward your logs to New Relic.
Use our guided install process to quickly and easily install log management and infrastructure monitoring together! This is the easiest solution to get both your app's logging data and your host's logging data into New Relic. Watch a video of how this works.
If you don't need the host metrics automatically included with infrastructure log forwarding, or if you already have a log forwarder, you can use any of the following supported options to forward your logs to New Relic from operating systems:
We support the following Amazon log forwarders:
We support the following Microsoft log forwarder:
We also support these log forwarders:
- Akamai DataStream 2
- Cloudflare Logpush
- Google Cloud Platform Pub/Sub
- Heroku log streaming
- Kubernetes plugin
- Vector plugin
In some situations you may not have log forwarders; for example, with CDNs, hardware devices, or managed services. You can use syslog protocols such as
syslog-ng, and forward your logs to New Relic via a TCP endpoint.
If you prefer to connect to New Relic without installing a plugin, we offer an HTTP input integration. This option sends your monitored log data directly to New Relic via the Log API.
You can quickly and easily forward your log data using our infrastructure agent's guided install process. To learn how, including examples of how to use your logging data in New Relic, watch this Nerdlog video on YouTube (14:46 minutes):
After you enable your log forwarder, make the most of your data in New Relic with our log management capabilities:
- Explore the logging data across your platform with our Logs UI.
- See your logs in context of your app's performance in the APM UI. Troubleshoot errors with distributed tracing, stack traces, application logs, and more.
- Get deeper visibility into both your application and your platform performance data if you are forwarding your logs with our infrastructure monitoring agent. Review your infrastructure logs in the UI.
- Set up alerts.
- Query your data and create dashboards. For example, see our NerdGraph tutorials to query and manage your data partition rules and your log parsing rules.