Rick Bradley 218f098800 [QENG-4075] Unify graphite and statsd for the pool manager ... Prior to this, the `pool_manager.rb` library could take handles for both graphite and statsd endpoints (which were considered mutually exclusive), and then would use one. There was a bevy of conditional logic around sending metrics to the graphite/statsd handles (and actually at least one bug of omission). Here we refactor more, building on earlier work: - Our graphite class comes into line with the API of our Statsd and DummyStatsd classes - In `pool_manager.rb` we now accept a single "metrics" handle, and we drop all the conditional logic around statsd vs. graphite - We move the inconsistent error handling out of the calling classes and into our metrics classes, actually logging to `$stderr` when we can't publish metrics - We unify the setup code to use `config` to determine whether statsd, graphite, or a dummy metrics handle should be used, and make that happen. - Cleaned up some tests. We could probably stand to do a bit more work in this area.		2016-07-12 14:24:58 -05:00
..
vmpooler	[QENG-4075] Unify graphite and statsd for the pool manager	2016-07-12 14:24:58 -05:00
vmpooler.rb	[QENG-4075] Unify graphite and statsd for the pool manager	2016-07-12 14:24:58 -05:00