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.