Add timing info with something like statsd

[yuvipanda]

Allows us to form a more clear idea of how this behaves under various loads. python-statsd makes it pretty easy to include, and easy to not use when you do not need it.

[minrk]

sounds great!

[yuvipanda]

I wonder if we should actually build this into CHP itself... These are useful when systems are running anyway.

[minrk]

I'm not familiar enough with it to say, but that may make sense. Just track things like:

• http req/sec
• http response time (?)
• ws bytes/sec
• ws connect/sec
• active ws connections

for CHP. We could consider the same for JupyterHub:

• logins/sec
• auth API accesses
• Running users
• Spawn timers

[yuvipanda]

+1. It would be immensely useful. I'll file bugs on both CHP and JupyterHub.

On Wed, Mar 2, 2016 at 12:10 PM, Min RK notifications@github.com wrote:

I'm not familiar enough with it to say, but that may make sense. Just
track things like:

• http req/sec
• http response time (?)
• ws bytes/sec
• ws connect/sec
• active ws connections

for CHP. We could consider the same for JupyterHub:

• logins/sec
• auth API accesses
• Running users
• Spawn timers

—
Reply to this email directly or view it on GitHub
#1 (comment).

Yuvi Panda T
http://yuvi.in/blog

[minrk]

Perfect, thanks. This is the first I'm hearing of statsd, and I already have a ton of ideas of things to track.