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.


