IOSOR Learn
Heartbeat and smoke gates before paging humans
Page humans only after a fresh webhook heartbeat and delivered smoke prove the pipe — vanity latency dashboards alone must not wake ops.
Alerts that wake humans must prove the pipe first: a fresh webhook heartbeat and a delivered smoke on the live path. Vanity latency charts must not page ops. Stale HB ≡ blocked for alerting — no fake green.
This page is alert hygiene after pipe proof — not the traffic_ok launch gate (traffic_ok gate before pilot volume); not a latency deep dive (SMS latency root cause). Also: Day-1 runway: what must be green, webhooks that survive launch, and Shared status language for product and finance.
IOSOR is white-label prepaid. USD 20 funds smoke evidence; soft review near USD 1,000/month does not waive stale HB.
Alerts are not vanity dashboards
A dashboard can look healthy while the webhook consumer is silent. Paging on p95 spikes or “chips green last week” trains humans to ignore incidents. Contracts need HB age, smoke intent ID with delivered/honest-terminal outcome, and a shared reason code.
| Signal | May page? | Why |
|---|---|---|
| Fresh HB + delivered smoke | Yes | Pipe proven |
| Latency chart spike alone | No | Vanity |
| Stale HB or missing smoke | No — blocked | Fake green |
Vanity metrics stay in investigation views — not the pager. Missing HB age or smoke intent → suppress.
Fresh heartbeat before any page
Heartbeat must be fresh: recent signed webhook events, consumer without silent drop, IDs matching ledger rows. Yesterday’s 200 is not a page license. Stale HB ≡ blocked for alerts.
Do not page when HB is outside freshness or export lacks HB timestamp (webhooks that survive launch). Soft volume near USD 1,000/month does not waive stale HB. Override: named owner, reason, new fresh HB.
Smoke proves the pipe humans wake for
Smoke is engineering evidence: one held intent on the live corridor, one terminal outcome (delivered or honest fail), exportable intent ID. Humans wake for broken pipes — not unproven charts.
Sequence: fresh HB → delivered smoke → arm pages. Without smoke, suppress. USD 20 funds the smoke wallet. Distinct from traffic_ok gate before pilot volume: unlocks pilot money; this unlocks human pages after pipe proof.
What not to page on
Do not page solely on vanity latency dashboards, orphan green chips without HB age, sandbox smoke on another corridor, soft-volume chatter near USD 1,000/month, or latency theories without pipe proof (SMS latency root cause — diagnosis, not paging). No “almost page” yellow. Day-1 red → pages off (Day-1 runway: what must be green).
Buyer checklist for HB and smoke before alerts
- Do human pages require fresh HB inside a written freshness window?
- Is delivered (or honest-terminal) smoke required before any page?
Start with IOSOR
Stale the webhook heartbeat on purpose and prove human pages stay silent. Refresh the heartbeat, send one delivered smoke on the live path, export both timestamps, then arm paging. This is a wake gate, not a Live-badge ceremony and not a wallet floor.
IOSOR takeaway
Humans wake only after a fresh heartbeat and a delivered smoke.
Do: export heartbeat time and smoke intent before the first page. Don’t: page from a vanity latency chart or a stale heartbeat.
Was this guide helpful?
Related guides
- Reconciling Telemetry Event Logs with Ledger Debits at Billing
Learn how to audit and reconcile message execution telemetry with ledger debits in IOSOR, ensuring accurate billing and resolving discrepancies.
- Establishing Telemetry Metric Baselines During Pilot Week
Learn how to establish stable telemetry baselines, verify webhook latency, and monitor prepaid thresholds during your white-label CPaaS pilot week with IOSOR.
- Delivery Receipt Latency Analysis During Monthly Volume Reviews
Evaluate and mitigate delivery receipt (DLR) propagation delays during monthly volume reviews to protect downstream SLAs and optimize webhook performance.