Hey folks, welcome to another installment of Monitoring Weekly! Did you write something about monitoring recently? Maybe got an idea rolling around in your head? Send it on over and let the community learn from you. :D
We’ve got a pretty short issue this week, thanks to America being on holiday for half the week.
Sadly, I only just learned of this conference, the Open Source Monitoring Conference, after it wrapped up last week. Thankfully, the folks at Netways (who are also the organizers, it seems) wrote up a great wrap-up.
Speaking as a former network engineer, there is one easy way to make your network engineers love you: give them a proper traceroute when you tell them about suspected problems. (bonus points for packet captures!) One thing I didn’t even think about, and yet seems so obvious now, is running all that traceroute data through Grafana. The example given in this article is straightforward but it could easily be expanded to be even more useful.
Designing a monitoring system for a low-to-medium traffic monolithic app is pretty easy. Designing monitoring for a high-traffic, distributed architecture is a bit of a challenge. This talk goes through how to design and build a real-time streaming architecture for monitoring, similar to what you’d expect under the hood at a monitoring company such as Librato, Datadog, or others.
The folks at InfoQ, who interviewed me about my book, Practical Monitoring, last week, just posted this interview with Charity Majors about observability, how applications have changed, and what we should do about it in order to keep pace with understanding the health of the apps.
See you next week!
– Mike (@mike_julian) Monitoring Weekly editor