This year I again had the privilege of delivering a keynote during the Velocity Conference in Santa Clara, CA. Last year I shared my experiences, lessons learned, and cloud services I depended on during the lifetime of BrowserMob - from inception to acquisition (video here).
This year I spent my time on stage discussing the various types of tools DevOps people depend on to maximize performance, availability, and functionality. Stuff like HTTP synthetic monitoring, functional testing, application performance management (APM), browser-based synthetic monitoring, and more recently Real User Measurements. You can find the video here.
Despite window.onerror having been around for years, very few people utilize it to gain insight in to the experience of their real users. For example, of the 60 sponsors at Velocity, only one (Dropbox) was actively capturing JS errors and sending the logs back to a central server.
What’s interesting is that the equivalent thing for mobile apps has recently received quite a bit of attention, mostly due to several competing hot startups:
There are few services out there that do JS error logging:
Most don’t look super professional, with the exception of Fire Tower. And now that it’s part of Crashlytics, it’ll be interesting to see how the combination evolves and grows out the analytics around error reporting. I’m also curious to see if log management services like Splunk, Loggly, Sumo Logic, and Papertrail get in to the game of analyzing error messages and error rates.