Re:Browser Monitoring for GitHub.com
by seanp2k2 on Tuesday May 19, 2015 @10:57PM
(#9574419)
It seems like they could collect those metrics on the back-end (kitchen / food processor(s)) too, or use tip % as a proxy metric for QoS. Not sure how they'd track e.g. CTR, but straight conversions could be easy enough if you instrument the servers such that they're tracking clients per table. Of course, if you're trying to solve for optimal Drink Refresh Rate, you might need something more granular along the lines of sugar.
[ Parent
| on HN ]