{"push_id":2180058582,"size":1,"distinct_size":1,"ref":"refs/heads/ajs-migrate-2","head":"2299332fb827eaf9c25e59b9f55a853ba3c567b4","before":"c6090c59c8c49e49966f0ff9e34cdefc1a6a9e75","commits":[{"sha":"2299332fb827eaf9c25e59b9f55a853ba3c567b4","author":{"name":"Akshay Shah","email":"5878b1ba896f8f0f120152e37da0e9f1fb91a6b8@uber.com"},"message":"Add support for Prometheus's protobuf exposition\n\nThis commit makes the controller an HTTP handler, which uses portions of\nthe official Prometheus client to expose all the registry's metrics for\nscraping or debugging. The Prometheus client's HTTP handler is pretty\nnice - it automatically does some content-type negotiation, so it dumps\nplain text by default but also supports negotiating up to the binary\nprotobuf encoding.\n\nThis requires one final extension to the internal `metric` interface:\nall metrics must now be able to serialize themselves to Prometheus's\n`MetricFamily` protobuf type. This is an internal detail, so we can\ndefinitely change if the Prometheus exposition format changes (which it\nlikely will - there's a group of folks working on a common exposition\nformat for a whole variety of metrics systems).\n\nThis is tested via an end-to-end integration test. The fixture for the\nintegration test was generated by the official Prometheus client\nlibrary; in a post-1.0 commit, I'll add the code that generated it and\nverify that it also matches the fixture exactly.","distinct":true,"url":"https://api.github.com/repos/yarpc/metrics/commits/2299332fb827eaf9c25e59b9f55a853ba3c567b4"}]}
{"actor":{"display_login":"akshayjshah"}}