Page MenuHomePhabricator

Move Navigation Timing reporter to separate repo (scap-deployed)
Closed, DeclinedPublic

Description

Move code to a dedicated repository, turn it into a proper Python module, add tests, configure CI.

Then remove puppet file resources and instead deploy through scap from Git.


Original task description:

navtiming.py started life as a quick hack, and gradually grew to its current proportions. It's not a disaster yet, but it is definitely on the path to becoming spaghetti.

Some ideas:

  • Use eventlogging.EventConsumer instead of lower-level APIs (ZeroMQ).
  • Upstream @handles decorator.
  • Provide some abstraction to assist with metric segmentation (i.e., reporting a metric with multiple key names / prefixes.)
  • Move code to a dedicated repository, turn it into a proper Python module, add tests, configure CI.

Event Timeline

ori triaged this task as High priority.

Use of ZeroMQ and EventLogging is tracked here:

Basic tests were recently added for NavTiming as well.

Re-purposing this task for the move to a separate repo and presumably deploying through scap instead of puppet.

Krinkle renamed this task from Navigation Timing metric reporter (navtiming.py) should be refactored to Move Navigation Timing reporter to separate repo (scap-deployed).Dec 7 2016, 7:31 PM
Krinkle lowered the priority of this task from High to Low.
Krinkle updated the task description. (Show Details)

Closing this task. It's fine in puppet for now. The above three improvements are on the way to implementation.