• Log in

Forward your logs to New Relic

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:

For example:

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 service-level logs, application logs, infrastructure logs, or all of the above from your cloud platform, including Amazon AWS, Google Cloud Platform, Microsoft Azure, and Heroku.

Collect logs from apps running in Docker containers, either standalone or when using Kubernetes

Use our Kubernetes plugin or our infrastructure monitoring agent with Docker.

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:

Get started with log forwarders

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:

  1. If you don't have one already, create a New Relic account. It's free, forever.
  2. Have your New Relic account's license key.
  3. Install a compatible log forwarder.
  4. Ensure that outbound connectivity on TCP port 443 is allowed to the CIDR range that matches your region.
  5. Depending on where your account data is stored in New Relic, use the DNS name log-api.newrelic.com or log-api.eu.newrelic.com for configuration.
  6. If applicable, configure your app's APM agent by following the manual logs in context procedures.

Log forwarding options

We provide several solutions to forward your logs to New Relic.

Infrastructure agent (recommended) and OS solutions

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:

Amazon

We support the following Amazon log forwarders:

Microsoft

We support the following Microsoft log forwarder:

Other supported log forwarders

We also support these log forwarders:

TCP endpoint

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 rsyslog and syslog-ng, and forward your logs to New Relic via a TCP endpoint.

Log API

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.

How log forwarding works

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):

What's next?

After you enable your log forwarder, make the most of your data in New Relic with our log management capabilities:

Copyright © 2022 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.