Skydive - An Open Source Real-Time Network Topology and Protocols Analyzer

Thursday, May 5, 2016

Skydive is an open source real-time network topology and protocols analyzer. It aims to provide a comprehensive way of understanding what is happening in the network infrastructure.

Skydive agents collect topology informations and flows and forward them to a central agent for further analysis. All the informations are stored in an Elasticsearch database.

Skydive is SDN-agnostic but provides SDN drivers in order to enhance the topology and flows informations. Currently only the Neutron driver is provided but more drivers will come soon.

Topology Probes
Topology probes currently implemented:
  • NetLINK
  • NetNS
  • Ethtool
Topology connectors:
  • Neutron
  • Docker

Flow Probes
Flow probes currently implemented:
  • sFlow
  • PCAP

  • Go >= 1.5
  • Elasticsearch >= 2.0

Make sure you have a working Go environment. See the install instructions .
Then make sure you have Godep installed. See the install instructions .
$ go get

Getting started
Skydive relies on two main components:
  • skydive agent, has to be started on each node where the topology and flows informations will be captured
  • skydive analyzer, the node collecting data captured by the agents

For a single node setup, the configuration file is optional. For a multiple node setup, the analyzer IP/PORT need to be adapted.
Processes are bound to by default, you can explicitly change binding address with "listen:" in the proper configuration sections.
See the full list of configuration parameters in the sample configuration file etc/skydive.yml.default .

$ skydive agent [--conf etc/skydive.yml]
$ skydive analyzer [--conf etc/skydive.yml]

To access to the WebUI of agents or analyzer:

Skydive client
Skydive client can be used to interact with Skydive Analyzer and Agents. Running it without any command will return all the commands available.
$ skydive client

  skydive client [command]

Available Commands:
  alert       Manage alerts
  capture     Manage captures

  -h, --help[=false]: help for client
      --password="": password auth parameter
      --username="": username auth parameter
Specifying the subcommand will give the usage of the subcommand.
$ skydive client capture
If an authentication mechanism is defined in the configuration file the username and password parameter have to be used for each command. Environment variables SKYDIVE_USERNAME and SKYDIVE_PASSWORD can be used as default value for the username/password command line parameters.

Start Flow captures
Skydive client allows you to start flow captures on topology Nodes/Interfaces
$ skydive client capture create -p <probe path>
The probe path parameter references the interfaces where the flow probe will be started, so where the capture will be done.
The format of a probe path follows the links between topology nodes from a host node to a target node :
The node name can be the name of :
  • a host
  • an interface
  • a namespace
The node types can be :
  • host
  • netns
  • ovsbridge
Currently target node types supported are :
  • ovsbridge
  • veth
  • device
  • internal
  • tun
  • bridge
To start a capture on the OVS bridge br1 on the host host1 the following probe path is used :
$ skydive client capture create -p "host1[Type=host]/br1[Type=ovsbridge]""
A wilcard for the host node can be used in order to start a capture on all hosts.
$ skydive client capture create -p "*/br1[Type=ovsbridge]"
A capture can be defined in advance and will start when a topology node will match.
To delete a capture :
$ skydive client capture delete <probe path>

Topology informations are accessible through HTTP or a WebSocket API
HTTP endpoint:
curl http://<address>:<port>/api/topology
WebSocket endpoint:
  • NodeUpdated
  • NodeAdded
  • NodeDeleted
  • EdgeUpdated
  • EdgeAdded
  • EdgeDeleted

Skydive provides a DevStack plugin that can be used in order to have Skydive Agents/Analyzer configured and started with the proper probes by DevStack.
For a single node setup adding the following lines to your local.conf file should be enough.
enable_plugin skydive

enable_service skydive-agent skydive-analyzer
The plugin accepts the following parameters:
# Address on which skydive analyzer process listens for connections.
# Must be in ip:port format

# Inform the agent about the address on which analyzers are listening
# Must be in ip:port format

# ip:port address on which skydive agent listens for connections.

# Configure the skydive agent with the etcd server address
# http://IP_ADDRESS:2379

# The path for the generated skydive configuration file

# List of agent probes to be used by the agent
# Ex: netns netlink ovsdb

# Remote port for ovsdb server.

# Set the default log level, default: INFO

Subscribe via e-mail for updates!