Sometimes, network troubleshooting will be implemented several weeks even months after a problem occurs. At that time, rich history data is required for further analysis. However, the fact is that history data analysis is difficult to implement in the system, not to mention the history data analysis capability in runbook automation. All of these demands lead to Proactive Data Collection that can help you respond to network issues much faster.

To proactively offer rich history data for network analysis and troubleshooting, V7.1 introduces a new independent mechanism to collect and parse target device data on a regular basis, as known as Crawl. The data retrieved and parsed via Crawl tasks is highly customizable, and mainly used for further analysis in more features, such as running Qapp/Gapp, and applying data views.

Different from benchmark (a system-wide snapshot regularly to update GDR data model, targeting all devices) or scheduled Qapp/Gapp (mainly for problem-based monitoring), the data types collected via Crawl tasks are rich and highly customizable for further analysis, targeting individual devices.

By default, a set of Crawl tasks are initialized via the system built-in template. You can enable/disable crawl tasks based on your needs, or customize a Crawl task by modifying the required parsers, target devices, or adjusting the frequency.

▪Enabling Built-in Crawl Tasks

▪Customizing a Crawl Task