Explore your data with New Relic's log analytics

Use the New Relic log analytics user interface to:

  • Quickly spot interesting patterns in your logs; for example, discovering that a majority of the errors occurred on a single host.
  • Explore and manipulate your logging data by using attributes as search conditions.
  • Control what attributes appear in the line chart, and add or remove columns in the logs table, so that you can understand the structure of your data at a glance.
  • Examine more context around a particular log line; for example, see what was happening on a particular host leading up to the error.
  • Share the data with charts, add to dashboards, etc.
  • Set up alert conditions for problems you want to prevent.

Working with the Logs UI

New Relic Logs UI
one.newrelic.com > Logs: This example shows the attributes included in the selected log. You can include or exclude them in your search, and view surrounding logs. Also notice that the attributes dropdown on the left side of the Logs UI indicates a significant number of errors have come from a specific service.

To help you get the most out of the Logs user interface, follow this basic workflow.

  1. Go to one.newrelic.com > Logs.
  2. Search:

    Search with keywords or phrases to find the results you want; for example, process failed.


    From the search field, use the type-ahead dropdowns to select an attribute, operator, and value; for example:

    service_name equals my service

    For more information, see the Logs query syntax documentation.

  3. Look for patterns:

    To spot suspicious spikes or drops in log messages, skim the Volume chart. Then, to zoom in to a specific area, click and drag. Or, to jump directly to logs for a specific point in time, click that point on the chart.

  4. Narrow your focus:

    To narrow the focus of your initial search results or quickly find outliers, expand any of the attributes to view the ten most common values within the results. For example, if a host listed under the hostname attribute is generating significantly more error messages than the others, select that value to apply it to your search.

  5. Examine log details:

    To see which attributes are included in a log message, select the log line. Add or remove columns as needed to help you focus on the details you need. Then, to control which attributes appear in the results, select a value or highlight text to include or exclude it from your search.

  6. Get related logs:

    To view all the logs for a specific value: From the selected log's Log details attributes list, select Show surrounding logs.

You can also use any of the core New Relic One functions (specific account, time range, data explorer, query builder, etc.).


Here are a few examples of how you can use the Logs UI to get detailed information. To use some of these examples, you must be able to see logs in context.

Create an alert from log data

You can create alert conditions directly in the Logs UI:

  1. Go to one.newrelic.com > Logs.
  2. Search for results that you want to alert on; for example, service_name:"your service" "fatal error".
  3. In the search bar, click the plus icon, then select Create an alert from this.
  4. Complete the Create alert condition that slides out, then review the NRQL query that will power the alert condition.

After you save the Logs alert condition, you can view it in the Alerts UI, where you can make additional changes as needed.

Add log volume chart to a dashboard

You can add log charts to a dashboard directly from the Logs UI.

  1. Go to one.newrelic.com > Logs.
  2. Search for results you want to plot; for example, service_name:"checkout service" "process failed".
  3. From the attribute list, select an attribute to facet the chart; for example, hostname.
  4. At the top right of the chart, select the chart options ... button, click Add to dashboard, and complete the form.

You can also create charts with the data explorer or the query builder in New Relic One.

Troubleshoot an error (logs in context)

To troubleshoot errors this way, you must be able to see logs in context. Then, to have a better understanding of what was happening on the host at the time an error occurred in your app:

  1. Go to APM > (select an app) > Events > Error analytics and select an error trace.
  2. From the error trace Details, click See logs.
  3. From the Logs UI, browse the related log details.
  4. To identify the host generating the error, click Show surrounding logs.
Troubleshoot latency (logs in context)

To troubleshoot latency this way, you must be able to see logs in context. Then, to have a better understanding of how your systems were operating when performance noticeably slowed:

  1. Go to one.newrelic.com > Distributed tracing.

  2. Select a particularly slow trace.
  3. From the trace Details, click See logs for this trace.
  4. Browse related logs in the Logs UI.

Depending on your New Relic subscription, you can access your logs from several places in the New Relic UI. For some of these options, you must be able to see logs in context.

To view logs... Do this...
Directly from the Logs UI Go to one.newrelic.com > Logs.
From an entity Go to one.newrelic.com > Entity explorer > (select an entity) > Logs (if available).
From distributed tracing Go to one.newrelic.com > Distributed tracing > (select a trace > Logs (if available).
From Kubernetes Go to one.newrelic.com > Kubernetes cluster explorer > (select a cluster) > (select a pod or container) > See logs (if available).
From your app in New Relic APM (logs in context) Go to one.newrelic.com > APM > (select an app) > Events > Logs (if available).
From an error trace in New Relic APM (logs in context) Go to one.newrelic.com > APM > (select an app) > Error analytics > (select an error trace) > See logs (if available).

For more help

If you need more help, check out these support and learning resources: