Serverless means no servers to watch — not nothing to watch. Lambda monitors will tell you when functions fail, slow down, get throttled or stop running.
Lambda functions fail in ways nobody sees: an image resizer times out on large files, a webhook handler throws for one customer's data, a scheduled report silently stops because its trigger was removed. The logs are there — if someone reads them.
AWS Lambda Monitoring will watch the functions you choose and alert you about errors, timeouts, throttling and missed runs, with the function name and the numbers that matter.
The plan for the first release. Every check will be stored in a full log, like all Upzilla monitors.
Failed invocations, and the rate of failure.
Functions that run long or hit their limit.
Invocations AWS refused to run.
Scheduled functions that stop running.
The Cron Jobs Monitor can already alert you when a scheduled function stops checking in.
Set up like every other Upzilla monitor, in a few minutes.
Read-only access to the regions you use.
Or all functions with a given tag.
Name, error rate and when it started.
Catch failing handlers before users report them.
Image, video and file processing that must not stall.
Reports and clean-ups that run on a timer.
Webhook handlers between your systems.
The same alert channels as every Upzilla monitor, as many as you like.
We are building it now; many new checks arrive before the new year. Create a free account to hear first.
The Cron Jobs Monitor can already watch a scheduled function: the function pings Upzilla when it runs, and you are alerted when it stops.
Read-only access to Lambda and its metrics.
Yes — and API Monitoring can already check those endpoints from the outside today.
Start with 10 free monitors today — we will tell you the moment this one is ready.