The data collection system provides a flexible and an extensible suite of collectors.

The generic Kafka collector is one collector used to collect fault and performance data from an external Kafka bus.
Collector Type Description
VeloCloud-SDWAN Collects data from a VeloCloud SD-WAN deployment. VeloCloud versions 3.4.0 and 3.4.1 are supported.
Viptela Collects data from a Viptela SD-WAN deployment. Viptela vManage version 18.3.x, 19.2.x, is supported in this release.
Cisco ACI Collects data from a Cisco Application Centric Infrastructure (ACI) deployment. Cisco ACI version 4.1 is supported.
vIMS Collects data from a Virtual IP Multimedia Subsystem (vIMS) deployment. vIMS Cloudify Orchestrator 4.5 is supported.
NetFlow Collects NetFlow vX and Sflow-compatible devices data.
Kafka Collects data from an external Kafka bus.
Smarts-event-data-smarts-sam Collects event data from the smart domain manager.
Smarts-topology-data-smarts-sam Collects topology data from the smart domain manager.
VMware Telco Cloud Operations Gateway Collects metric data from an external system like MnR to VMware Telco Cloud Operations.

You can create collector instances using the VMware Telco Cloud Operations user interface. The steps to create collector instances are described in the following sections. To collect data from the devices, the user needs to configure the collector by selecting the collector type in the Data Collector Store page. The user can provide the properties for the collector in the configuration page.

Different collectors require modified configurations. In general, the collectors require the following specifications:
  • Location of the devices to monitor, such as an IP addresses and port number.
  • Credentials to use when communicating with the device, such as a token or user name and password.
  • How frequently data is collected (the polling interval).