---
title: No data appears (Infrastructure)
source: https://docs.newrelic.com/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure
---

## Problem

You installed the infrastructure agent and waited a few minutes, but no data appears in the [infrastructure UI](https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-ui-overview).

## Solution

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

> #### ⚠️ IMPORTANT
>
> For accounts installing the infrastructure agent for the first time, the latency for data appearing in the infrastructure monitoring 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](https://support.newrelic.com) for assistance.

> #### ⚠️ IMPORTANT
>
> By default, the infrastructure agent doesn't send data about the operating system's processes. To enable the sending of process data set [`enable_process_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#enable-process-metrics) to `true`. To fine-tune which processes you want to monitor, configure [`include_matching_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#include-matching-metrics) or [`exclude_matching_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#exclude-matching-metrics).

### Missing infrastructure data [#missing-infra]

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:

        ```sh
        dpkg -l | grep newrelic-infra
        ```
    2.  If `dpkg` returns no output, see [Install with apt](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-linux#apt-based).

    **Verify install for yum (Amazon Linux, CentOS, or RHEL)**

    1.  Use `rpm` to verify that agent is installed:

        ```sh
        rpm -qa | grep newrelic-infra
        ```
    2.  If `rpm` returns no output, see [Install with yum](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-linux#yum-based).

    **Verify install for Windows Server**

    1.  Use the Windows command prompt or Powershell to verify that the [agent directory](https://docs.newrelic.com/docs/agents/manage-apm-agents/troubleshooting/find-agent-root-directory#infra-agent) exists:

        ```sh
        dir "C:\Program Files\New Relic\newrelic-infra"
        ```
    2.  If you receive a `File not found` error, see [Install for Windows Server](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-windows-server).
2.  Use [your init system](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#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:

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

        ```sh
        sudo systemctl start newrelic-infra
        ```

    **Verify status with System V**

    Use System V commands with Debian 7:

    1.  Check that the agent is running:

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

        ```sh
        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:

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

        ```sh
        sudo initctl start newrelic-infra
        ```

    **Verify status with Windows**

    Use the Windows command prompt:

    1.  Check that the agent is running:

        ```sh
        sc query "newrelic-infra" | find "RUNNING"
        ```

    2.  If the agent isn't running, start the agent manually with the Windows command prompt:

        ```sh
        net start newrelic-infra
        ```

        If running `net start newrelic-infra` returns `The service name is invalid`, the infrastructure agent may not have been installed correctly and the service was not properly created.

        To test this:

    3.  From Powershell, run the command `get-service newrelic-infra`, which will return the status of the service.

    4.  If it returns an error `Cannot find any service with service name newrelic-infra`, then follow standard procedures to reinstall the agent.
3.  Use [New Relic Diagnostics](https://docs.newrelic.com/docs/agents/manage-apm-agents/troubleshooting/new-relic-diagnostics) to try to automatically identify the issue.
4.  Verify that your [`newrelic-infra.yml`](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent#config-file) configuration file contains a valid [`license_key`](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent#conf-license_key) setting.
5.  Verify that the host has a [unique hostname](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure#hostname), and verify that the hostname is not `localhost`. For more information, see this [Support Forum post](https://support.newrelic.com/s/hubtopic/aAX8W0000008ZJa/relic-solution-a-common-reason-host-failing-the-infrastructure-dashboard).
6.  Verify that no firewalls or proxies are blocking outbound connections from the agent process to the [Infrastructure domains and ports](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/networks#infrastructure).
7.  Confirm the host is reporting correctly even though it is not appearing in the infrastructure monitoring UI by creating a basic query in Query builder, like:

    ```sql
    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](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/troubleshooting/generating-logs-troubleshooting-infrastructure) and examine the logs for errors.

### Missing integration data [#missing-integrations]

If you are missing data from an integration, see troubleshooting procedures for:

-   [APM data missing from infrastructure monitoring](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/troubleshooting/apm-data-missing-infrastructure)
-   [Amazon/AWS integrations](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/troubleshooting/no-data-appears-amazonaws-integrations)

## Other factors affecting access [#more-info]

For more on factors that can affect your ability to access New Relic features, see [Factors affecting access](https://docs.newrelic.com/docs/accounts/accounts-billing/general-account-settings/factors-affecting-access-features-data).