Logs tied to the exact run that produced them. Errors surfaced before you go looking. Costs visible per function. Long-running work that tells you when it's done.
When you run a function, the CloudWatch logs for that exact execution are retrieved and attached to its result. Output, errors, and logs together, per run, with retrieval status tracked so you know when they've landed.
For broader investigation: select any function, set a time-range window, search with text filters, auto-refresh while you watch a live issue, inspect entries in detail, and export what you need.
A dedicated error monitoring workflow surfaces errors detected in your functions' CloudWatch logs — you don't discover problems by accident or by customer email. Each surfaced error links directly to the CloudWatch console when you want to go deeper.
Deploys, builds, runs, background operations — the global notification system (bell and toasts, everywhere in the app) reports the outcome of long-running work wherever you are in the workspace. Kick off a deploy, keep building, and let the result come to you.
Per-function cost grids and charts show your spend at a glance and let you compare functions side by side. The function quietly burning money stops hiding in a monthly bill — you see it, by name, while there's still time to do something about it.
CloudWatch log retention is configured right alongside the rest of a function's settings — with a change summary before saving, like every configuration change in LambdaDeploy.
More on the Function Editor →