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. 😀
Monitoring News, Articles, and Blog posts
5 traits of teams that make on-call less terrible for developers
It’s actually not terribly difficult to drastically improve the on-call experience and these five suggestions are really great ones. My favorite is #5: have empathy.
If you’re in the SF Bay Area, be sure to come to the SF Metrics Meetup next week on March 7th! We’ve got Baron Schwartz (Vivid Cortex, @xaprb) and Mike Freedman (TimescaleDB, @michaelfreedman) speaking.
Full disclosure: I’m an organizer of this event.
Do you pay extra for on-call duties? Why? Why not? This thread on Twitter has a lot of really great thoughts on the topic. Personally, I think on-call should be compensated for. Doctors and nurses, for example, know that on-call is part of their job going into it and they’re still paid extra for their on-call shifts. Our industry is rather flippant about the whole thing, and I think that needs to change.
From the fantastic folks at Pivotal, Micrometer aims to be a vendor-agnostic metrics library for JVM-based applications.
Curious about Prometheus? Here’s another well-written start-up guide.
Built by the folks at Logz.io, Sawmill is an open-sourced tool they’ve been using internally as a replacement for Logstash’s JSON transformation functionality. If you’re running Logstash at scale, this might help.
See you next week!
— Mike (@mike_julian) Monitoring Weekly Editor