Report Issue


Major Features

The Time Series Data Repository (TSDR) project in OpenDaylight (ODL) is an extendible collector framework used to collect and store network metrics from SDN protocols, traditional network protocols as well as SDN controller and environment data. This data is stored in a common format using one of several datastores and is accessible by a REST interface, Grafana interface (beta) and by the ODL provided API.

SDN, Environment and Traditional Network Data Collected

  • OpenFlow
  • NetFlow
  • sFlow
  • REST
  • SNMP
  • SysLog
  • Controller Metrics

TSDR Overview

The Time Series Data Repository (TSDR) project in OpenDaylight (ODL) creates a framework for collecting, storing, querying, and maintaining time series data in the OpenDaylight infrastructure. TSDR provides the framework for plugging in various data collectors to collect OpenFlow, sFlow, NetFlow, SysLog and Controller metrics time series data in a common data model and generic TSDR data persistence API. The user can choose which data stores to be plugged into the TSDR Persistence framework. Three data stores are currently supported: HSQLDB (loaded by default), HBase and Cassandra.

With the capabilities of data collection, storage, query, aggregation and purging provided by TSDR, network administrators could leverage various data driven applications built on top of TSDR for security risk detection, performance analysis, operational configuration optimization, traffic engineering and network analytics with automated intelligence.

TSDR Model/Architecture

TSDR has the following major components:

  • Data Collection Service
    • OpenFlow Data Collector
    • RestConf Data Collector
    • NetFlow Data Collector
    • SNMP Data Collector
    • sFlow Data Collector
    • SysLog Data Collector
    • Controller Metrics Data Collector
  • Data Storage Service
    • HSQLDB Datastore (loaded by default)
    • HBase Datastore
    • Cassandra Datastore
  • Data Query Service
  • ElasticSearch Service
  • Grafana integration for time series data visualization
  • Data Aggregation Service
  • Data Purging Service

The Data Collection Service handles the collection of time series data into TSDR and hands it over to the Data Storage Service. The Data Storage Service stores the data into TSDR through the TSDR Persistence Layer. The TSDR Persistence Layer provides generic Service APIs allowing various data stores to be plugged in. The Data Aggregation Service aggregates time series fine-grained raw data into course-grained roll-up data to control the size of the data. The Data Purging Service periodically purges both fine-grained raw data and course-grained aggregated data according to user-defined schedules.

TSDR provides component-based services on a common data model. These services include the data collection service, data storage service and data query service. The TSDR data storage service supports HSQLDB (the default datastore), HBase and Cassandra datastores. Between these services and components, time series data is communicated using a common TSDR data model. This data model is designed around the abstraction of time series data commonalities. With these services, TSDR is able to collect the data from the data sources and store them into one of the TSDR data stores; HSQLDB, HBase and Cassandra datastores. Data can be retrieved with the Data Query service using the default OpenDaylight RestConf interface or its ODL API interface. TSDR also has integrated support for ElasticSearch capabilities. TSDR data can also be viewed directly with Grafana (beta) for time series visualization or various chart formats.

Core TSDR Framework


TSDR Collectors






TSDR Data Stores






Security Considerations

  • TSDR northbound query supports authentication and authorization using AAA features.
  • Since ODL OpenFlow Plugin supports TLS, the OpenFlow Stats data transported from OpenFlow enabled appliances to ODL will be encrypted when TLS is enabled.
  • Syslog, NetFlow, and RestConf collectors do not support encryption at this time.

Quality Assurance


  • Is it possible to migrate from the previous release? If so, how?
    • Yes, since there’s no contract breaking changes of features from the previous releases.


  • Is this release compatible with the previous release? Yes
  • Any API changes? No
  • Any configuration changes? No

Bugs Fixed

  • List of bugs fixed since the previous release
    • TSDR-26 TSC-113 Convert to Jersey 2
    • TSDR-28 odl-openflow-statistics-collector doesn’t collects openflow stats from multiple mininet
    • TSDR-31 Fix broken tsdr feature failing the new extended SingleFeatureTest incl.
    • TSDR-37 Upgrade Guava because of Jersey 2.x dependency
    • TSDR-42 Remove SNMP dependency for Fluorine
    • TSDR-47 Convert NBI to use new web registration API
    • TSDR-49 Provide support for new grafana and re-add dataquery feature
    • TSDR-52 Investigate FlowCapableNodeConnectorStatistics building
    • TSDR-61 TSC-96 IetfInetUtil conversion from byte[] and InetAddress returns Ipv4Address
    • TSDR-78 Catch and log NumberFormatException
    • TSDR-80 TSDRQueryandNBITest failing 500 error
    • TSDR-82 Validate REST NBI query parameters
    • TSDR-85 Add detailed user-facing error messages for query params

Known Issues

  • Collector data stores run one at a time. To switch store, uninstall current and install new.
  • Grafana interface is still under construction.


  • List of features/APIs which are EOLed, deprecated, and/or removed in this release
    • experimental SNMP data collector was temporarily removed until further support is found.
    • experimental sFlow data collector was temporarily removed until further support is found.


  • List of standards implemented and to what extent
    • N/A

Release Mechanics