How to Configure Data Sources

Faddom collects network traffic from on-premises, cloud, and hybrid environments. For on-premises deployments, Faddom uses IPFix, Netflow, and sFlow protocols. In the cloud, traffic is collected by enabling traffic logging and providing Faddom with API access to the logs.

VMware

Nutanix
​Hyper-V and KVM Based hypervisors
​AWS
​Azure
​Kubernetes
​Physical Environments
​Load Balancers

For initial discovery and traffic collection in VMware, you will need enhanced permissions. Once the initial configuration is complete, you can revert to read-only access. You will need to either enable NetFlow for distributed switches or deploy sensors for standard switches. See How to Enable Traffic Collection in VMware for detailed instructions.

Faddom discovers Nutanix environments and collects traffic via IPFix. See How to Discover Nutanix AHV for instructions on initial discovery and enabling IPFix to receive traffic.

Faddom uses host sFlow to provide traffic and performance data in Hyper-V. To configure it in Hyper-V, follow the guide Hyper-V sFlow Configuration. For Proxmox and similar hypervisors, see How to Setup Faddom on Proxmox. For other KVM-based hypervisors, you can download host sFlow and configure it according to the documentation.

To enable discovery of AWS, Faddom requires read-only credentials to the account with EC2 instances and to S3 where you will store the VPC Flow Logs. See Mapping an AWS Subscription Using Faddom for full details.

For Azure discovery, Faddom requires read-only credentials to the account after creating an app registration and access to the storage where you will store the VPC Flow Logs. See Mapping an Azure Subscription Using Faddom for full details.

For Google Cloud Platform discovery, Faddom requires read-only credentials to the account. See the relevant GCP configuration guide for full details.

For OCI discovery, follow the relevant Oracle Cloud configuration guide for credential and access requirements.

To discover Kubernetes, you need to install host sFlow on the nodes and provide a Kubecfg file. See How To Integrate My Kubernetes Cluster With Faddom? for full instructions.

For physical environments, enable traffic monitoring on your network devices. In cases where this is not possible or for standalone machines, you can perform discovery through the Faddom agent. See Capturing network traffic using agents for instructions.

Faddom uses SNMP v2 or v3 to read the configuration of your load balancers. If your load balancers support IPFix protocols, you can also forward the traffic to Faddom for a more complete picture. Faddom supports F5, Citrix, A10, Kemp, Radware, and VMware Avi load balancers. See How to Set Up a Load Balancer for more information.

When viewing data sources in Settings > Data Sources, each data source displays a colored border to indicate its configuration status. Green indicates the data source is fully configured and working properly. Yellow indicates a partial configuration or warning, such as incomplete setup steps or configuration issues. Red indicates an error, such as a failed discovery task or authentication problem. Grey indicates the data source has not been configured. A legend at the bottom of the page explains these status indicators.

For additional help with data sources, contact support@faddom.com.