Monitoring & Health
Where each health signal comes from and what it tells you. This page is a map to the surfaces that already document each signal in depth — it does not restate their payloads.
Signals at a glance
| Signal | Tells you | Surface |
|---|---|---|
| Program-states events | Stream lifecycle — whether ingest started, is running, or ended | Program-states webhook |
format-started / format-ended | A specific rendition became available or went away | Program-states webhook (format events) |
| Webhook delivery history | Whether your endpoint is actually receiving events | Dashboard / Events API |
| Analytics Monitor | Live view of current activity | Analytics dashboard |
| Analytics Trends | Usage and behavior over time | Analytics dashboard |
Stream lifecycle
Program-states events are the primary signal that a stream is alive. They arrive on your registered program-states webhook as the stream moves through its lifecycle, so you do not poll for state. For a worked implementation that keeps stream and viewer state in memory from these events, see Webhook-based stream state management.
Rendition availability
Format events tell you when an individual output format becomes playable and
when it stops. They arrive as format-started / format-ended token events on
the same program-states webhook — nothing extra to implement.
A legacy path also exists, where Native Frame calls endpoints you host
(PUT for Format Begin, DELETE for Format End). Prefer the webhook. See
Format Availability.
Delivery health
Events are delivered asynchronously, fanned out, and retried with exponential backoff, and Native Frame keeps a full delivery history. That history is the surface to check when you suspect you are missing events — it distinguishes "never sent" from "sent, and your endpoint rejected it."
Your endpoint only needs to accept the delivery; the response body is not acted
on. Register and manage endpoints in the dashboard or through the Events API
(GET / PUT / DELETE /events/v2/webhook/{name}). See
Webhooks Overview.
If events stop arriving, check delivery history before changing your code — a retried-and-failing delivery points at your endpoint, while no delivery at all points at registration.
Usage and trends
The Analytics dashboards cover the operational view rather than per-event signals: Monitor for what is happening now, Trends for behavior over time. See Analytics.