Musing on the stats endpoint

[rgbkrk]

This is a dupe of jupyter/tmpnb#95, but likely belongs in both since they're using the same "spec".

I'm kind of wishing we had a beautiful front-end stats page (which could just be at stats.example.org), or we could make two endpoints on a given tmpnb server /stats for a beautiful mockup of the data and /api/stats for the raw JSON.

In addition, some things I've wanted during a deploy:

• List version of the containers that are running
• Some aggregated activity data (e.g. number of docker logs of individual containers)

[minrk]

If you want logs, I would probably put that on a separate endpoint. Adding container info makes sense, though. You don't want requesting stats to be too expensive, though.

[rgbkrk]

You don't want requesting stats to be too expensive, though.

Ah, yeah. Maybe a separate API call then for health checks?

We could flip it around and either have tmpnb report up to tmpnb-redirector, or some other shared key value store (e.g. etcd).

[captainsafia]

Can this be closed thanks to jupyter/tmpnb#162?

[rgbkrk]

Most definitely!

[rgbkrk]

Ah, wait. No. This hasn't been implemented in the redirector.

[captainsafia]

OK. Let me change the issue title to clarify that.

I shall submit a PR soon.