This section provides an overview of how FlowLink works and the supported flow records.
FlowLink can receive the flow data by connecting to a data source provided by you and adheres to your organizations' data format. It may consume flows at a rate that is slower than the source speed. Therefore, the flow sender caches the flow data for 48 hours or more. If the PCE is unable to accept flow data because of the rate of flow or availability issues, FlowLink caches the data locally to a disk for a configurable period of time or disk space and retries periodically (user-configurable number of minutes). It aggregates data flows and sends them to the PCE once every configurable number of minutes. It does not have access to the PCE data and therefore no knowledge of workloads, virtual services, and other objects.
The following types of flow records are supported:
AWS VPC flows
IPFIX v10
NetFlow v5, v7, v9, and v10
sFlow v5
Text (customizable parser configured by the user. For example, Syslog or Kafka).