tree: a5bb255195941f10e41de6fc5633f08ef8df3a08 [path history] [tgz]
  1. build/
  2. etc/
  3. src/
  4. .classpath
  5. .gitignore
  6. .pmd
  7. .project
  8. pom.xml
  9. README.md
traffic_monitor_java/README.md

Traffic Monitor

Why Tests are not in exactly matching packages

The “com.comcast.cdn.traffic_control.traffic_monitor” portion of the package name was omitted from unit tests to prevent improper referencing of package private fields and methods of the code under test.

Running Traffic Monitor locally

The “com.comcast.cdn.traffic_control.traffic_monitor.Start” class allows one to run Traffic Monitor locally provided that necessary configuration is in place. By default, the files are specified with paths relevant to certain IDEs, but these paths can be changed by specifying different properties via System.properties. These properties are:

  • traffic_monitor.path.config
  • traffic_monitor.path.db

The first property refers to the location of traffic_monitor_config.js. The second property refers to the directory that will be used for certain data files that are downloaded at runtime. If you need to specify a different path, use the -D option to the Java command, or modify the paths in the Start class directly.