Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Use the No-Data Tool

You can use the debug no-data tool to determine why a device or rule displays a “no-data” status.

These usage notes describe the features in the no-data tool.

  • The tool runs through the entire sequence of checks, regardless of any issues along the way.

  • The test results provide root cause information and advise where to focus your troubleshooting efforts.

  • While this feature is generally intended to debug a device when it is marked as no-data, you can use it any time to verify that deployed rules are receiving data.

  • This tool does not support rules using a syslog sensor, as the sensor data is event driven and not periodic.

To run the test:

  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."

      Figure 1: No-Data Tile No-Data Tile
    • 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.

    The example above shows that all devices are working as expected.