December 30, 2011
I’ll remember 2011 as the year of fine-tuning at Scout. From your experience with the end product to our experience delivering it, we invested a lot of our time sanding Scout.
scout_apiRuby gem, you can slice and dice your metrics as you see fit.
With nearly 60 monitoring plugins in our directory, Scout’s breadth of coverage grew substantially in 2011. Some of the highlights:
But it’s not just new plugins that I was excited about: Scout plugins grew incredibly more robust. Our plugin repository on Github had more than 200 commits from 20 authors in 2011. Thanks for all of your pull requests and bug reports: there are few things I love more than solidifying Scout’s core.
We think it’s important for you to know how our brains function at Scout. Some of the highlights (or lowlights, depending on your interpretation):
We plan on Scout being around for a long time. 2011 saw the start of our grand succession plan: both Andre and I brought home baby girls this year. While my two-month old daughter is lacking focus at this point, I’m confident she’ll be ready to take over my share of Scout by 2035.
I’ve never been more excited about Scout. We eliminated a lot of cruft from Scout in 2011 that’s freeing us up to make monitoring even easier in 2012. Thanks for your continued feedback, bug reports, and plugin commits: you’re making Scout better every year.