• Log inStart now

No log data appears in the UI

Problem

You're not seeing expected log data in the New Relic UI after ten minutes of installing the infrastructure agent, the APM agent, or setting up log forwarding.

Solutions

If no data appears after you set up a log-reporting solution and wait about five minutes, try the following:

Logs troubleshooting

Comments

Infrastructure and APM agents

These agents are designed to automatically report log data. This is referred to as logs-in-context. If you don't see that data, or want to do additional configuration, some options:

Access to data

It's possible you may not have the right permissions or account access. See Factors affecting access to features and data.

Compatibility

If you've set up log forwarding, ensure you've installed a compatible log forwarder.

Status codes

Check the response status code being returned from the New Relic log collection endpoint. For example, you might see:

HTTP Error 403: Forbidden. Review your license key.

This error means that you're using an invalid security key. New Relic requires a license key to enable log shipping.

An HTTP 202 response indicates success.

Errors

Run a query using the NrIntegrationErrors event to see if any errors are related to logging. For example, look for messages like:

Error unmarshalling message payload

Query Log

Try querying the Log data type:

SELECT * FROM Log

If no data appears in the query builder, then no data will appear in the Logs UI. For more information, see our docs about data query options.

Copyright © 2022 New Relic Inc.

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