Debug No-Data

Problem

You are unable to determine why a device or rule displays a “no-data” status on the Configuration > Devices page and the Configuration > Rules page. You are unable to debug this error.

Solution

You can use the debug no-data tool to determine why a device or rule displays a “no-data” status. The tool goes through a step-by-step process to determine at which stage incoming data gets dropped or blocked.

The step-by-step process is as follows:

1. Verifies that all common and device group-related services are up and running.

2. Tests connectivity to the device by using ping and SSH.

3. Verifies that configured ingest sessions are established.

   This verification is limited to OpenConfig, iAgent, and SNMP-based ingests.

4. Verifies whether the ingest is receiving any raw data from the devices.

5. (Within rules) Verifies that the fields process sensor-related information and that this information is populated in the database.

6. (Within rules) Verifies that the trigger settings work as intended and that trigger status information is populated in the database.

7. Checks for API timeouts that might be affecting the GUI.

To debug the no-data status of a device or rule:

1. Access the debug no-data tool by navigating to either of the following pages:

   • Monitoring > Network Health

     On this page, click any tile that shows "no-data."

   • Configuration > Data Ingest > Diagnostics

   The Diagnostics page appears.

2. Click No Data to view the No-Data Settings tabbed page.

3. From the No-Data Settings tabbed page, configure the following settings:

   1. Select a device group from the Device Group drop-down list.

   2. Select a device from the Device drop-down list.

   3. Select a topic from the Topic drop-down list.

   4. Select one or more rules from the Rule(s) drop-down list.

4. Click Test to run the debug no-data test.

   The test results appear after a few minutes.

   The color coding for the test results is as follows:

   • Green status = pass

   • Yellow status = error (unable to test)

   • Red status = fail (test failed)

   • Yellow or red status includes a message with details about the issue.

   High-level information about the results of the test is also displayed.