The 3 levels of AWS observability
Hey 👋🏽
This week I'm bringing back one of our most-read posts: the 3 levels of AWS observability. A lot of you joined after it went out in May, and the topic fits this week perfectly.
Because the real question isn't "do I have logs?" anymore. It's "who actually knows what they mean?" 👇🏽
Sponsored by Dynatrace. These are my own words.
📚 From the Archive
In 2022 I joined a startup with 100 million API requests a month. All on AWS, all logs in CloudWatch. I loved it. Then the first incident hit. My boss was looking over my shoulder, and I didn't even know which log stream to open. As a self-claimed AWS expert. Level 1: Log HellWe had logs, metrics and some traces. All unstructured plain text, spread over different log streams. When a customer reported a missing order, we searched strings and compared timestamps by hand. You cannot skip a levelOver the years I went through three levels of AWS observability. Each one builds on the one before. Most teams stop at Level 2, and that is the level that makes everything after it possible. Level 3 is where I stopped opening the console. What does it take to get there, and why does it fail without Level 2? |
📰 This Week in AWS🌐AWS Lambda Web Functions
🔀CloudWatch log routing and chained parsers
🔁Lambda loop detection for EventBridge custom buses
|
That's it for this week.
Where is your team right now: Level 1, 2 or 3? Hit reply and tell me, I read every answer.
See you next week,
Sandro & Tobi