About the Diagnostics Page
Paragon Insights supports four verification and troubleshooting features:
Paragon Insights Self Test — To know how to run the test, see Use the Self Test Tool.
Device Reachability Test — To know how to run the test, see Use the Reachability Test.
Ingest Connectivity Test — To know how to run the test, see Use the Ingest Test Tool.
Debug No-Data — To know how to run the test, see Use the No-Data Tool
Paragon Insights Self Test | The self-test tool validates the core functionality of Paragon Insights. To perform the self test, the tool performs a typical set of tasks:
The self-test instance essentially acts as a fully working setup, running entirely within the Paragon Insights system. When testing is complete, the tool provides a report. In addition to validating the Paragon Insights installation, the self-test feature also provides:
|
Device Reachability Test | Earlier, you would need to get through the entire setup procedure - add the device, setup a device group, apply playbooks, monitor devices - at which point the health pages would indicate “no data” indicating that the setup did not work correctly. But, “no data” does not indicate whether the problem is a reachability issue or data streaming issue. In Paragon Insights, the device reachability tool can verify connectivity to a device. The tool performs tests using ping and SSH. Paragon Insights uses the device’s IP address or host name, based on what was configured when adding the device. |
Ingest Connectivity Test | The ingest connectivity tool can verify ingest methods where Paragon Insights initiates the connection, such as OpenConfig, iAgent, and SNMP. Paragon Insights does not test UDP-based ingest methods, such as syslog and Native GPB, as the UDP parameters are common to a device group and not specific to a device. This tool provides multiple benefits such as:
Paragon Insights validates each supported ingest method in its own way:
|
Debug No-Data | The debug no-data tool helps to determine why a device or rule is showing a status of “no-data”. The tool takes a sequential, step-by-step approach to determine at which stage incoming data is getting dropped or blocked, as follows:
|