The AI Cloud Engineers

The AI Cloud Engineers

Observability for Serverless Without the Bill Shock

How to actually see what your serverless app is doing without CloudWatch quietly becoming your biggest line item.

Lefteris Karageorgiou's avatar
Lefteris Karageorgiou
Aug 19, 2026
∙ Paid

Hey, it’s Lefteris 👋 I’m the voice behind the weekly newsletter “The Cloud Engineers.”

Here’s a story every serverless team eventually lives through. You ship a Lambda-based system, it works beautifully, and you feel great. Then the monthly bill arrives and there’s a line item that makes you squint: CloudWatch. Sometimes it’s bigger than the Lambda compute it’s supposed to be observing.

Observability is non-negotiable. You cannot run a distributed serverless system blind. But in serverless, the very thing that gives you visibility is metered, and the defaults are quietly expensive. The goal isn’t to log less and fly blind. It’s to be deliberate: capture what you need, drop what you don’t, and design your observability the same way you design everything else, with cost as a first-class constraint.

Let’s break down the three pillars — logs, metrics, and traces — where each one silently runs up the bill, and how to get production-grade visibility without the shock.

Thanks for reading The Cl…

User's avatar

Continue reading this post for free, courtesy of Lefteris Karageorgiou.

Or purchase a paid subscription.
© 2026 Lefteris Karageorgiou · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for writing, podcasting, and media founders.