GitHub PushEvent at 2014-02-11 15:50:41
Repository: sidekiq-statsd
Actor: vinayvinay
Payload: {"shas":[["866e2b5941d3ce276834a9221acd6bfd008609ed","56173d9c4ea5b30d6b19800e69d9f1e5ac7ba11f@digital.cabinet-office.gov.uk","Added metrics based on Sidekiq Stats API","Vinay Patel",false],["0b94f81b402fc6eb1e07871dd631e5b8dd086c04","56173d9c4ea5b30d6b19800e69d9f1e5ac7ba11f@digital.cabinet-office.gov.uk","Temporarily getting tests to pass","Vinay Patel",false],["7b274a530f056ae7a86596e20faa6042748ea4e1","56173d9c4ea5b30d6b19800e69d9f1e5ac7ba11f@digital.cabinet-office.gov.uk","Tracking gauges in batch mode\n\nChanges:\n\n1. Added gauges to track total enqueued, processed,\n   and failed jobs, and 2 queue-level metrics - depth\n   and latency. These metrics reflect numbers that\n   Sidekiq::Stats api gives us.\n\n2. Removed the Client as it's main responsibility\n   was to return a statsd client which is done\n   from the middleware. we don't need wrapper\n   methods for increment, gauge, time as the\n   Client had, because those were only adding\n   correct prefix, which is replaced by a method.\n\n3. Because we have a bunch of metrics to track,\n   it would be better to use the statsd batch mode\n   which came with the 1.1.0 release of statsd-ruby.\n\n4. Added a new option statsd, to enforce the usage\n   of an existing statsd client.","Vinay Patel",false],["36a2b1f866bb43e2a3b0a05e23bba8f98997de5b","ae35ab0740aacd97464a00403599420b75e90d1f@gmail.com","Merge pull request #3 from alphagov/more-metrics\n\nMore metrics","Pablo Cantero",true],["36cd063453c017fcc6e57842bce633be0cf3a5cc","707d14912bb250caf67dfe0ea4035681fbfc4f56@pablocantero.com","Bumps version to 0.1.2","Pablo Cantero",true],["8edac07edd4623eabcadae3ab6cc2fe681a07d98","ae35ab0740aacd97464a00403599420b75e90d1f@gmail.com","Update README.md","Pablo Cantero",true]],"size":6,"ref":"refs/heads/master","head":"8edac07edd4623eabcadae3ab6cc2fe681a07d98"}