Skydive is an open source real-time network topology and protocols analyzer providing a comprehensive way of understanding what is happening in your network infrastructure.
Captures network topology, interface, bridge, namespace attributes and keeps the history of all the modifications.
Distributed probe, L2-L4 classifier, GRE, VXLAN, GENEVE, MPLS/GRE, MPLS/UDP tunneling support. Ability to follow a flow along a path in the topology.
Support for external SDN Controllers or container based infrastructure, OpenStack, OpenContrail, Docker. Supports extensions throught API.
Distributed, scalable, easy to deploy, only one static binary.
With Skydive you can see how your SDN implements the virtual network even in nested environment like containers running on top of an OpenStack deployment. You can control and set alerts according to what is expected. Skydive keeps track of each modifications allowing to troubleshoot past events.
Skydive captures all the interface metrics and store them in a time series database. You can also start traffic capture allowing you to monitor metrics for specific protocols or according to topology informations. All the metrics are available through the API and a Grafana plugin is also available.
Skydive can be used in a continous integration/delivery process in order to validate network deployment or workload.
Capacity planning, abnormal traffic detection, unexpected performances...
In this 5 minute video I present howto install skydive realtime network topology analyzer onto a local k8s cluster using helm charts.
This post describes the Skydive-Prometheus connector, which translates data from Skydive captured flows into a format that can be consumed by Prometheus. The first implementation of the Skydive-Prometheus connector periodically provides the byte transfer counts for each network connection under observation. The code can be easily tailored to provide additional flow information.
In this demo we show how Skydive can help roll-out configuration changes across your Kubernetes landscape, helping in visualizing which pods are dependent on the configuration object and going beyond that by automatic the restarting of all dependent pods automatically by utilizing Skydive REST API.
Skydive is a powerful network topology and protocol analyzer. In this demo we use skydive to debug a storage related failure.
Skydive is a real-time topology and protocol analyzer, with it's Kubernetes plugin it can now be used to debug k8s applications. In this video we demonstrate how it can be used to identify issues within the bookinfo sample application.
This post demonstrates the Skydive network’s exploration capabilities for IBM Cloud Private over a reference cloud-native microservices application.
Skydive is “an open source real-time network topology and protocols analyzer”. It is a tool (with CLI and web interface) to help analyze and debug your network (OpenStack, OpenShift, containers, …). The Data Plane Development Kit (DPDK) is a set of data plane libraries and network interface controller drivers for fast packet processing. As Skydive uses flow probes to analyze packets, thanks to gopacket. As the bandwidth used by Software Defined Networks increases, we need a solution to capture and analyze packets at high speed from switch port mirroring.
Skydive is “an open source real-time network topology and protocols analyzer”. It is a tool (with CLI and web interface) to help analyze and debug your network (OpenStack, OpenShift, containers, …). Dropped packets somewhere? MTU issues? Routing problems? These are some issues where running skydive whill help. So as an update on my previous demo post (this time based on the Newton release), let’s see how we can trace SFC with this analyzer...
SDN products are evolving fast. The release cycles can be short and more and more features are added in each cycle. This is clearly a change that network administrators weren’t used to with hardware solutions. In this context the operational team in charge of the SDN functionnality of the platform must be confident when deploying new releases. For that matter the team must be able to test new builds for ISO functionality with the previous build, and detect possible regressions...