Maple checks your sites, APIs, ports and cron jobs around the clock. When one fails, you get the alert with the reason, and a failed HTTP check opens as a trace of the request inside your app.
In motion
Every bar is one check. By default, two failures in a row open an incident and alert your team. It closes on its own once the check passes again.
Root cause
Most uptime tools stop at "503". Maple's HTTP checks carry a trace ID into your app, so if the app is instrumented, a failed check opens as the full request. Here, the database pool took five seconds to hand out a connection.
Set it up
Ask an AI assistant connected to Maple's MCP server, or keep monitors next to your code in Terraform, Pulumi or the REST API. Here is the same check three ways.
> Add an uptime check for https://api.example.com/health,
every minute, linked to the checkout service.
create_uptime_monitor({
kind: "http",
name: "checkout-api",
url: "https://api.example.com/health",
interval_seconds: 60,
service: "checkout",
}) resource "maple_uptime_monitor" "checkout_api" {
name = "checkout-api"
interval_seconds = 60
service_name = "checkout"
config = jsonencode({
type = "http"
url = "https://api.example.com/health"
})
} curl https://api.maple.dev/v2/uptime_monitors \
-H "Authorization: Bearer $MAPLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "checkout-api", "kind": "http",
"config": {"type": "http", "url": "https://api.example.com/health"},
"interval_seconds": 60, "service_name": "checkout"}' What it does
On the plan
In production: Superwall sends Maple more than 80 billion traces, logs and metrics a month, about 18 TB, with nothing sampled out. Read the Superwall story
One endpoint, one key. Traces, logs, metrics and sessions, linked from the first request.