Lambda Function Error Notifications

CloudWatch Alarms on Lambda error metrics route through the agent. It groups related errors, pulls the latest stack trace from CloudWatch Logs, and pings on-call with the suspected cause.

Webhook + WhatsApp DMlambdacloudwatcherrors

Conversation example

CloudWatch Alarm: lambda-billing-worker-errors ALARM (threshold: 5 errors in 5 min)
http_request → CloudWatch Logs filterLogEvents

Lambda errors spiking on billing-worker. Pulling the last 10 log events from CloudWatch Logs...

whatsapp_web_send

Lambda Error Burst — billing-worker Function: arn:aws:lambda:us-east-1:...:billing-worker Errors: 12 in 5 min (alarm threshold: 5) Invocations: 48 → 25% error rate Top error (9 of 12): TypeError: Cannot read property 'plan_id' of undefined at prorateUsage (/var/task/src/billing.js:84) at Runtime.handler (/var/task/src/index.js:22) Correlation: started 6 min after the v2.11.0 deploy of lunogen/api. Looks like a missing field on trial subscriptions. Pinged @rivka-d (last committed to billing.js yesterday). Want me to trigger a rollback?

More AWS use cases

Deploy this in minutes

Create a LunoGen agent, connect AWS, and start running this workflow from WhatsApp today.

Back to AWS