Here's a gif I made showcasing Server Timing with Node.js + Chrome DevTools: <a href="https://umaar.com/dev-tips/136-server-timing/" rel="nofollow">https://umaar.com/dev-tips/136-server-timing/</a>
I was excited when I first heard about Server Timing, until I realised it was limited to a single duration value. Being able to model an actual timeline would make it significantly more useful.
This gem seems like a good way to get a full app view while remaining in the browser. The only thing I might add would be to have an example turning on these metrics on a per request basis (via a parameter) so that you could check performance for users other than admin users.<p>Aside: I've used scout on a production application and it is similar in quality to new relic but far simpler to understand.
Hi Derek! You've helped me with my employer's Scout configuration in Slack :)<p>Is there an automated way of getting the average of a performance metric (eg Time spent in AR) over N requests?
Seems to be using the `Server-Timing` header — are there docs somewhere on what this expects & what features it supports? Are other browsers likely to follow it?
There's also RailsPanel which I found quite useful when I was still using Chrome: <a href="https://chrome.google.com/webstore/detail/railspanel/gjpfobpafnhjhbajcjgccbbdofdckggg" rel="nofollow">https://chrome.google.com/webstore/detail/railspanel/gjpfobp...</a>
Neat! Seems similar to this project which I've been keeping an eye on: <a href="https://github.com/geoffreylitt/ladybug" rel="nofollow">https://github.com/geoffreylitt/ladybug</a>
Similar library for go: <a href="https://github.com/mitchellh/go-server-timing" rel="nofollow">https://github.com/mitchellh/go-server-timing</a>