Last night, at DevOps Boulder, I presented the StatsD basics: key concepts, metric types & implementation strategies - and dug a little deeper. My mission was to talk about StatsD and how it made me a better developer by giving me a simple, repeatable tool that I could use to instrument my code.
Here are my slides.
During the Q&A session after the presentation, the group started a lively discussion around StatsD. We discovered:
Using StatsD to generate custom metrics is great - but there is a deeper value in developer engagement.
StatsD can help make us better team members by encouraging cooperation, collaboration and advancing DevOps CAMS (Culture, Automation, Measurement & Sharing) in an organization.
Logging still has a place, but StatsD provides a more immediate feedback mechanism.
It was great to hear specific examples of how StatsD had already helped organizations and their DevOps process.
If you haven't had the chance to check out StatsD, here's a post and some code samples to help get you started:
If you have any StatsD stories about how it has helped your organization, we'd love to hear them! Please leave a comment below.