No data appears (Infrastructure)

Problem

You installed the New Relic Infrastructure agent and waited a few minutes, but no data appears in the New Relic Infrastructure UI.

Solution

Data should appear in the Infrastructure UI within a few minutes for accounts with previously installed agents.

For accounts installing the Infrastructure agent for the first time, the latency for data appearing in the Infrastructure UI can be tens of minutes. If the following steps verify the installation and no obvious error conditions appear in the verbose logs, monitor the Infrastructure UI for a longer period before contacting support.newrelic.com for assistance.

If no data appears in the UI, try the following steps to diagnose the problem:

  1. Use your package manager to verify that the Infrastructure agent is installed:

    Verify install for apt (Debian or Ubuntu)
    1. Use dpkg to verify that the agent is installed:

      dpkg -l | grep newrelic-infra
    2. If dpkg returns no output, see Install with apt.
    Verify install for yum (Amazon Linux, CentOS, or RHEL)
    1. Use rpm to verify that agent is installed:

      rpm -qa | grep newrelic-infra
    2. If rpm returns no output, see Install with yum.
    Verify install for Windows Server
    1. Use the Windows command prompt or Powershell to verify that the agent directory exists:

      dir "C:\Program Files\New Relic\newrelic-infra"
    2. If you receive a File not found error, see Install for Windows Server.
  2. Use your init system to verify that the agent is running:

    Verify status with SystemD

    Use SystemD commands with CentOS 7, Debian 8, RHEL 7, and Ubuntu 15.04 or higher:

    1. Check that the agent is running:

      sudo systemctl status newrelic-infra
    2. If the agent isn't running, start the agent manually:

      sudo systemctl start newrelic-infra
    Verify status with System V

    Use System V commands with Debian 7:

    1. Check that the agent is running:

      sudo /etc/init.d/newrelic-infra status
    2. If the agent isn't running, start the agent manually:

      sudo /etc/init.d/newrelic-infra start
    Verify status with Upstart

    Use Upstart commands with Amazon Linux, CentOS 6, RHEL 6, and Ubuntu 14.10 or lower:

    1. Check that the agent is running:

      sudo initctl status newrelic-infra
    2. If the agent isn't running, start the agent manually:

      sudo initctl start newrelic-infra
    Verify status with Windows

    Use the Windows command prompt:

    1. Check that the agent is running:

      sc query "newrelic-infra" | find "RUNNING"
    2. If the agent isn't running, start the agent manually with the Windows command prompt:

      net start newrelic-infra
  3. Use New Relic Diagnostics to try to automatically identify the issue.
  4. Verify that your newrelic-infra.yml configuration file contains a valid license_key setting.
  5. Verify that the host has a unique hostname, and verify that the hostname is not localhost. For more information, see this Online Technical Community post.

  6. Verify that no firewalls or proxies are blocking outbound connections from the agent process to the Infrastructure domains and ports.

  7. Confirm the host is reporting correctly even though it is not appearing in the Infrastructure UI by creating a basic query in Insights, like:

    SELECT * FROM SystemSample SINCE 60 minutes ago LIMIT 100

    Use the query results to note the timestamps, which show when the data was reported. To determine when data was first received, look at the earliest timestamp.

  8. Generate verbose logs and examine the logs for errors.

If you need additional help, get support at support.newrelic.com.

If you are missing data from an integration with New Relic Infrastructure, see troubleshooting procedures for:

For more help

Recommendations for learning more: