This issue is sponsored by:
It is actually surprisingly difficult to create product testing criteria from scratch. Anyone who has evaluated products in the past can tell stories about new criteria popping up last minute, simply because no one thought about it before they found a problem in one product.
That’s a dumb way to evaluate products. Do better with Scalyr’s guide to evaluating a log management platform.
Did you miss last week’s issue?
You can read it here: Issue #074
Latest Articles on monitoring.love
The (in)famous Corey Quinn of Last Week in AWS recently graced the website of Monitoring Weekly and wrote this gem on a new/old concept: Observerless.
Articles From The Community
This isn’t strictly monitoring-related, but given everyone’s job on this newsletter, I know you’ll be interested in it. For those not familiar with it, the annual State of DevOps Report is a tremendous work headed up by Dr. Nicole Forsgren every year using legit, rigorous research and statistical analysis methods. The results of this one are pretty neat to read.
For you PRTG folks wondering what to do with all those Arduinos laying around, well, you’re in luck.
I’m still digesting this article because it’s just that good, but the gist: calculating a latency SLO is harder than it first seems, and you’re probably doing it wrong (I know I am).
I always get a kick out of the Rails library for improving logging: lograge. That about sums up my feelings with respect to Rails logging.
This is great: a Prometheus exporter for smartmon.
Well, seems I lost the game of “is that actually an AWS service or is Corey screwing with me again?” This article covers AWS GuardDuty, an incident detection service that leverages VPC flow logs, CloudTrail, and DNS.
Do you perhaps need a shot of Jaeger(meister) to help soothe the pain otherwise known as “understanding my microservice architecture”? This article on tracing might help solve the monitoring problem, but sorry, you’re on your own with the rest of it.
DevOpsDays KC on Twitter: “Excited to see @mike_julian share what an old jalopy taught him about monitoring: https://t.co/eZLjxJAQ63 - use code SEEMIKEJULIAN to get a 25$ discount that you can spend on oil filters or timing belts.”
Yes, I’ll definitely be touching on the horror of timing belts in interference engines with deferred maintenance. Also, monitoring.
Going to KubeCon in Seattle? You should totally go to this event that runs in conjunction.
See you next week!
– Mike (@mike_julian) Monitoring Weekly Editor