Traffic Stats Administration¶
Traffic Stats consists of three separate components: Traffic Stats, InfluxDB, and Grafana. See below for information on installing and configuring each component as well as configuring the integration between the three and Traffic Ops.
Installing Traffic Stats¶
In order to store Traffic Stats data you will need to install InfluxDB. While not required, it is recommended to use some sort of high availability option like Influx enterprise, InfluxDB Relay, or another high availability option.
Grafana is used to display Traffic Stats/InfluxDB data in Traffic Ops. Grafana is typically run on the same server as Traffic Stats but this is not a requirement. Grafana can be installed on any server that can access InfluxDB and can be accessed by Traffic Ops. Documentation on installing Grafana can be found on the Grafana website.
Configuring Traffic Stats¶
Traffic Stats’s configuration file can be found in
/opt/traffic_stats/conf/traffic_stats.cfg. The following values need to be configured:
The user used to connect to Traffic Ops
The password to use when connecting to Traffic Ops
The URL of the Traffic Ops server used by Traffic Stats
The user to use when connecting to InfluxDB (if configured on InfluxDB, else leave default)
That password to use when connecting to InfluxDB (if configured, else leave blank)
The interval at which Traffic Monitor is polled and stats are stored in InfluxDB
The status of Traffic Monitor to poll (poll ONLINE or OFFLINE Traffic Monitors)
The absolute path of the seelog configuration file
The interval, in seconds, at which Traffic Stats checks to see if daily stats need to be computed and stored.
The default retention policy for cache stats
The default retention policy for Delivery Service statistics
The retention policy to be used for the daily statistics
An array of InfluxDB hosts for Traffic Stats to write stats to.
As mentioned above, it is recommended that InfluxDB be running in some sort of high availability configuration. There are several ways to achieve high availability so it is best to consult the high availability options on the InfuxDB website.
Once InfluxDB is installed and configured, databases and retention policies need to be created. Traffic Stats writes to three different databases: cache_stats, deliveryservice_stats, and daily_stats. More information about the databases and what data is stored in each can be found in the Traffic Stats Overview.
To easily create databases, retention policies, and continuous queries, run create_ts_databases from the
/opt/traffic_stats/influxdb_tools directory on your Traffic Stats server. See the InfluxDB Tools section for more information.
In Traffic Portal themenu item can be configured to display Grafana graphs using InfluxDB data (when not configured, this menu item will not appear). In order for this to work correctly, you will need two things:
A Parameter with the graph URL (more information below)
The graphs created in Grafana. See below for how to create some simple graphs in Grafana. These instructions assume that InfluxDB has been configured and that data has been written to it. If this is not true, you will not see any graphs.
To create a graph in Grafana, you can follow these basic steps:
Login to Grafana as an administrative user
Enter the necessary information to configure your data source
Click onat the bottom
Where it says No Title (click here) click and choose edit
Choose your data source at the bottom
You can have Grafana help you create a query, or you can create your own.
SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" GROUP BY time(60s), cdn;
Once you have the graph the way you want it, click the Save Dashboard button at the top
You should now have a new saved graph
In order for Traffic Portal users to see Grafana graphs, Grafana will need to allow anonymous access. Information on how to configure anonymous access can be found on the configuration page of the Grafana Website.
traffic_stats/grafana/ need to be in the
/usr/share/grafana/public/dashboards/ directory on the Grafana server. If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting the files in place. If your Grafana server is different from your Traffic Stats server, you will need to manually copy the files to the correct directory.
More information on custom scripted graphs can be found in the scripted dashboards section of the Grafana documentation.
Configuring Traffic Portal for Traffic Stats¶
Configuring Traffic Portal to use Grafana Dashboards¶
To configure Traffic Portal to use Grafana Dashboards, you need to enter the following Parameters and assign them to the special GLOBAL Profile. This assumes you followed instructions in the Installation, Configuring Traffic Stats, Configuring InfluxDB, and Configuring Grafana sections.
is the FQDN of the Grafana server (again, usually the same as the Traffic Stats server),
is the name of the Dashboard providing CDN-level statistics,
is the name of the Dashboard providing Delivery Service-level statistics, and
is the name of the Dashboard providing a daily summary of general statistics that would be of interest to administrators using Traffic Portal
Under the Traffic Stats source directory there is a directory called
influxdb_tools. These tools are meant to be used as one-off scripts to help a user quickly get new databases and continuous queries setup in InfluxDB. They are specific for Traffic Stats and are not meant to be generic to InfluxDB. Below is an brief description of each script along with how to use it.
Go 1.7 or later
Options and Arguments¶
(Optional) Print usage information and exit (with a failure exit code for some reason)
- --replication N¶
(Optional) The number of nodes in the cluster (default: 3)
- --url URL¶
The InfluxDB server’s root URL - including port number, if required (default:
- --user username¶
The name of the user to use when connecting to InfluxDB
This program is used to sync one InfluxDB environment to another. Only data from continuous queries is synced as it is down-sampled data and much smaller in size than syncing raw data. Possible use cases are syncing from production to development or syncing a new cluster once brought online.
Go 1.7 or later
Options and Arguments¶
- --database database_name¶
(Optional) Specify the name of a specific database to sync (default: all databases)
- --days N¶
The number of days in the past to sync.
(Optional) Print usage information and exit
- --source-url URL¶
(Optional) The URL of the InfluxDB instance _from_ which data will be copied (default:
- --source-user username¶
The name of the user as whom the utility will connect to the source InfluxDB instance
- --target-url URL¶
(Optional) The URL of the InfluxDB instance _to_ which data will be copied (default:
- --target-user username¶
The name of the user as whom the utility will connect to the target InfluxDB instance