Track request/response times in librato

[indirect]

Right now librato tracks internal response time (the time it takes to generate the response), but it doesn't track the amount of time that an HTTP request takes to go through the routing mesh blah blah blah. We should also track and graph the time it takes to make a request against the api at bundler-api.herokuapp.com and the time it takes to make a request against the api reverse proxied through rubygems.org.

[lmarburger]

Are you proposing an external process that periodically runs and generates this data? This sounds like a good start to some production specs.

[indirect]

Seems probably okay too add as another procfile entry or cronjob. The diff of times is more important than the times being similar to an Internet user far away physically I think.

On Feb 9, 2013, at 5:15 PM, Larry Marburger notifications@github.com wrote:

Are you proposing an external process that periodically runs and generates this data? This sounds like a good start to some production specs.

�
Reply to this email directly or view it on GitHub..

[indirect]

Hey, this is done! Thanks @lmarburger