The Problem With Distributed Tracing

Every function should have one, one single responsibility. One reason to do this is for cold start. The less pay load you have, the faster that code's gong to start up cold. If all my coad is bundled into one lamda or one container, and then a low balance that container, who knows what went wrong? But if i have one function, say post contact form, nwall, we know, you know, if there's an error on post contact form where it is, the mystery is over. There's no tracing to do. You just go to that coat and figure out what happened. And bob's your uncle. Lamda has cloud watch events set