Customers using the Collector
Though red/green server status may be sufficient for availability monitoring, Flowmon's market-leading NPMD solution will give clear insight for user experience monitoring, troubleshooting and capacity planning.
Flowmon Collector can process data in all standard formats such as NetFlow, IPFIX, sFlow, jFlow or NetStream. It supports data exported from any device, allowing for smooth integration into any network.
Native cloud traffic mirroring combined with the ability to process and normalize heterogeneous data from multiple sources, the Collector provides a uniform level of transparency throughout the public cloud, on-premise or hybrid environments.
Flowmon Collector can serve as a tool for network data analysis, allowing the user to see the “big picture”. It can also be used as a proxy to forward the data to security or analytical platforms, or it can serve as a comprehensive and reliable data storage. The Collector simply adapts to the user’s needs.
Small businesses or global networks with distributed architecture - Flowmon Collector can serve as a central point of network data storage and analysis with unlimited scalability. Add more Collectors or Flowmon Probes for larger networks and get complete, cost-effective coverage.
The Collector has the highest performance in flows/s per appliance on the market. Its database system is built for fast data processing and it has enough space to store the resulting amounts of data.
Flowmon Collector is able to process flow data from a variety of different network devices - routers, switches, firewalls, packet brokers or dedicated Flowmon Probes. In this way, it maximizes prior investments into the network infrastructure.
Configuration of flow sources is simple - the Collector performs it automatically. For instance, when a router is configured to export flow data, the Collector recognizes it as a new source, contacts it using SNMP, retrieves information and configures the system accordingly.
Flowmon Collector is delivered as a cloud application available in AWS, Azure and Google Cloud, as a virtual appliance for use in virtualized environments or as a hardware device with a wide range of configuration choices (flows per second, storage capacity, RAID type).
Apart from data from Flowmon Probes as well as all the other supported formats the Collector supports IPFIX extensions and proprietary formats from other vendors as well:
Flowmon Probe is an in-built functionality of the Collector as a virtual appliance that analyses packets and extracts the most useful information from L2, L3-L4 and L7 layers even within encapsulated traffic.
It then generates IPFIX records, which are NetFlow enriched with additional data such as network performance metrics, hostnames, URLs, SSL/TLS encryption data and much more. This allows scaling network analytics across the entire IT environment while keeping a granular level of detail for troubleshooting and forensics.
Extra standalone Probes can be added in large networks for complete coverage.
Flowmon’s Monitoring Center is the software natively installed on Collector. This powerful tool analyzes the collected data and provides well-arranged results within a smart interface. Learn more about the Monitoring Center.
Flowmon can be easily scaled by adding Collectors as needed to cover very large networks distributed over multiple distant locations. The central node, called Master Unit, will serve as a main console and storage point, and data from all branches will be seamlessly integrated and presented within one dashboard for perfect visibility. All the configuration and updating of the entire architecture, as well as its individual nodes, is performed from the central Collector.
Data can be stored for months or even years, depending on what capacity the user chooses - from 0.5TB to 192TB per appliance. The Collector does not aggregate or sample data – it keeps it all available for as long as specified in disk quotas for auditing or post-compromise purposes. Data can also be exported to network storage and then restored whenever needed.
Unlike full packet capture, flow data does not contain the content of the communication, which results in a significant size reduction of up to 500:1 in the case of NetFlow and 250:1 in IPFIX, consuming a mere 0.2 % and 0.4 % of bandwidth respectively. In this way, a much longer history, reserving full packet analysis only for when it is really needed.