Alerting › Delivery log

Delivery log

What was actually sent to a destination, and what the far end said.

Every send Uptimer attempts is recorded: the body it posted, whether it was accepted, and when. It is the answer to “the alert never arrived” without asking the destination.

Open it from a destination’s More → View delivery in Workspace → Settings → Destinations, or from the Delivery page’s own destination select.

What a row says

ColumnWhat it holds
Payloadthe body as it was sent, one line of it in the cell. View opens the whole thing. Under it, the alert kind this was.
StatusDelivered or Undelivered, and on a failure the reason the far end gave, quoted.
Whenthe moment of the attempt, in UTC.

View opens the full payload over the page rather than inside the row, so reading one attempt does not move the others.

Two filters, both in the URL so a view can be shared or bookmarked:

An empty result says so plainly. A workspace with no destinations says that instead — nothing has been sent because there is nowhere to send it.

It is a read

Nothing on the page sends, resends or changes a destination. There is no retry button: Uptimer sends once, in the background, and the record is what happened.

What it keeps, and for how long

Reading the log needs the Edit workspace permission, like the destinations it belongs to: the bodies it holds are the messages your monitoring sent.

Over the API

GET /v2/notifications/deliveries returns the same rows with the same two filters — see the REST reference.