The API answers, the work does not happen
The API enqueues and returns 200. If the consuming function fails, the ping stays green and nobody notices.
Functions, queues, Step Functions, tables and events on AWS, Azure and GCP, with no code or agents. And the full path of a message, because a 200 from the API does not tell you the work got done.
1 min
shortest interval for APIs and health endpoints
5 min
for functions, queues and tables
5 hops
per end-to-end flow, every 15 min
3 free
HTTP or heartbeat monitors on any plan
The API enqueues and returns 200. If the consuming function fails, the ping stays green and nobody notices.
Messages pile up with no visible error until a customer asks why nothing arrived.
A scheduled task that does not run raises no error: nothing happens, and nobody finds out until much later.
Lambda, SQS, Step Functions, DynamoDB, EventBridge and API Gateway, and their Azure and GCP equivalents, over the read-only connection: errors, aging messages, throttling and failed deliveries, with adjustable thresholds. From 5 minutes.
health+json, Spring Actuator, ASP.NET and Kubernetes, or your own JSONPath: if a component goes down, you see it even when the endpoint answers 200. From 1 minute.
A flow sends a test transaction into the start of the chain and checks it reaches every hop, up to 5 (e.g. SQS → Lambda → DynamoDB). If it breaks, it tells you which hop and how long each one took. Every 15 minutes.
A heartbeat waits for your scheduled tasks to check in, from 1 minute to 35 days. When an HTTP probe fails, it is confirmed from Frankfurt when it responds, before you are alerted by email, Slack, Teams, webhook, PagerDuty or Jira Service Management.
With thresholds you can adjust. Equivalent checks on Azure and GCP, based on what each cloud publishes (on Azure Functions, 5xx responses).
| Provider | Errors | Aging messages | Throttling | Failed deliveries |
|---|---|---|---|---|
| AWS Lambda | Yes | Yes | Yes | No |
| Amazon SQS | No | Yes | No | Yes |
| AWS Step Functions | Yes | No | No | No |
| Amazon DynamoDB | No | No | Yes | No |
| Amazon EventBridge | No | No | No | Yes |
| Amazon API Gateway | Yes | No | No | No |
On Lambda, age is that of the stream it processes; on SQS, failed deliveries are messages in its dead-letter queue. On Azure: Functions, Service Bus, Cosmos DB, API Management, Event Grid and Logic Apps. On GCP: Cloud Run, Cloud Functions, Pub/Sub, Eventarc, Workflows, Firestore and API Gateway.
Free
Pro · Business
No. Functions, queues and tables are read through your account connection, and endpoints through their URL. A heartbeat only needs your task to call a URL when it finishes.