Pervasive Network Fabric Visibility.

Full visibility into every application flows without TAPs.

Pervasive Telemetry for All Traffic Flows

Pluribus’ FlowTracker application flow Telemetry is the unique ability of Netvisor to inspect every individual TCP, UDP, ICMP and infrastructure flow (DNS, DHCP, NTP) connection and aggregated connection statistics in the fabric. The unique architecture of Netvisor ONE running on high performance white box switches and DPUs opens up unmatched visibility to all flows that traverse the entire data center fabric. With Netvisor FlowTracker, containerized, virtualized as well as bare-metal workloads are now fully visible, end-to-end.

This functionality is much more powerful than sFlow and is more ubiquitous than Netflow. FlowTracker flow telemetry is not a single device hardware concept like a TAP or SPAN port. It does not depend on dedicated hardware and as a service of the fabric is inherently fabric-wide and software defined yet leverages the powerful Broadcom switching chip (ASIC) to gather telemetry data at wire speed. Since this functionality is scalable in software by design, there is virtually no limit to how many devices can report data in the fabric.


This application-flow-centric data is unique to Pluribus Netvisor and the Unified Cloud Fabric and provides the capability to quickly examine specific hosts or endpoints and instantly obtain a snapshot of current or historical traffic patterns. This enables not only application performance analysis, but also deep security visibility across all devices and endpoints throughout the entire Netvisor fabric.

Features and Benefits

Traditional Approaches to Telemetry and Visibility

Standard data center switch architectures that use sampling via sFlow or NetFlow do not have the ability to provide compressive per-flow telemetry. So in order to achieve full visibility many data center operators will build out a TAP and TAP aggregation parallel overlay network. In this case fiber or copper TAPs are placed at critical switch or even server connections, and then feed into this parallel TAP network with additional aggregation switches and monitoring devices. This parallel network adds significant capital and operational costs to deploy and maintain.

A Modern SDN Fabric Approach to Telemetry and Visibility

The beauty of the Netvisor ONE OS and the Unified Cloud Fabric software is that the FlowTracker fabric service provides this comprehensive visibility of every flow across the fabric at wire speed with no extra cost and without the need for any external hardware. Eliminating the parallel TAP and TAP aggregation network saves significant capital and operational expense and dramatically reduces complexity.

UNUM Insight Analytics

Customers may optionally choose to license and deploy the UNUM Insight Analytics platform which can ingest the flow meta data and store up to 2.5 billion flows (depending on storage capacity) for up to 30 days. Once the flow metadata is ingested UNUM Insight Analytics provides rich graphical dashboards, powerful search functionality and alarming.

KubeTracker™: Revolutionary NetOps Tool for East-West Pod-to-Pod Visibility and Network Correlation

While DevOps has a broad array of options to monitor a Kubernetes environment from inside the cluster, KubeTracker is a unique tool designed for NetOps to monitor Kubernetes applications from outside the cluster with no software loaded onto the host. KubeTracker is a service of the Unified Cloud Fabric that is supported on any switch or DPU that is part of the fabric (enabled on any of the nodes) and can correlate network performance issues with microservices performance issues. It subscribes to the Kubernetes API server to make the entire fabric aware of how Kubernetes microservices are distributed across the network and how their deployments dynamically change over time.

KubeTracker Time Machine

KubeTracker’s “time machine” enables NetOps to track how the deployments of a microservice evolves over time, which application it is supporting and how it elastically expands and contracts to respond to Kubernetes deployment changes. Now it is easy to correlate Kubernetes events with networking events (e.g. loss of connectivity, traffic congestion, etc.) even if the container has disappeared from the cluster.

Pervasive Network Fabric Visibility.​