Skip to content
This repository was archived by the owner on Nov 13, 2018. It is now read-only.

Traffic Stats 3

Jan van Doorn edited this page Sep 11, 2016 · 1 revision

(from Neuman's 2.0 page)

###Initial Ideas for Traffic Stats 2.0.
This list is considered a work in progress; feel free to add to it.

All IPv6

  • Use IPv6 for all communication; overall design goal of TC 2.0

Better HTTPS support

  • Remove the need for httpd proxy

Generic Input interface.

  • Provide a way for other programs to write data to InfluxDb via Traffic Stats

High Availability

  • Traffic Stats currently runs on a single machine. We need a HA solution possibly using RAFT or hot/cold.

Easier configuration

  • Make it easier to configure of all components possibly via better/tighter integration with Traffic Ops.

Integrate more stats

  • Store stats from Traffic Router, Traffic Monitor, Traffic Ops, etc.

Backups

  • Provide a mechanism in Traffic Stats to backup data. Possibly a job that runs on cron or some other means.

Long Term storage

  • Figure out the feasibility and changes necessary to store data for at least 3 years

Easier way to create ad-hoc graphs

  • May be a function of Grafana/Chronograf

Explore Influx TICK stack

  • See what other pieces we want to integrate

config servers in config file, then TO

try multiple traffic monitors

fancy connect string. (all servers in cluster).

remove seelog.xml

[Traffic Control 3](Traffic Control 3)

[Traffic Control 2.0](Traffic Control 2.0)

Projects

Design discussions

Presentations

[Notes and Processes](Notes and Processes)

Clone this wiki locally