IOSOR
LearnSign InConnection applicationRestore Access
  1. IOSOR
  2. /Knowledge hub
  3. /Observability & ops signals

Observability & ops signals

Heartbeats, smoke checks, and shared status language for product and finance.

25 guides in this topic

  • Correlation IDs across debit and DLR

    Join the prepaid debit row to the delivery event with one stable correlation ID — finance and product share the same intent without archaeology.

  • Ops signal board when volume is live

    What to watch hourly at volume without drowning in raw upstream noise — HB age, smoke, missing/unknown, debit↔status join, and wallet stops on one white-label board.

  • Missing signal is not Delivered

    No DLR, no webhook, timeout, or silence must stay unknown or failed — never Delivered in UI or the prepaid ledger. Distinct from content-filter sent≠inbox and DLR retry policy.

  • 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.

  • Shared status language for product and finance

    Agree one product↔finance vocabulary for outcomes — accepted, held, settled, released, blocked, gated, delivered, failed, unknown/missing — before anyone builds dashboards. Not an SMS status encyclopedia.

Page 3 of 3

  1. Previous
  2. 1
  3. 2
  4. 3
  5. Next

Adjacent topics

  • Launch readiness

Not this hub: Incidents & status · Webhooks & events

Ready for a controlled prepaid path?

Tell us destinations, monthly volume, and compliance constraints. We will map onboarding clearly.

Apply for access
AboutKnowledge hubSite mapnFADP Privacy PolicyGDPR ComplianceTerms of ServiceSLA AgreementB2B Master AgreementApply for access

English is the sole legally binding language of IOSOR legal documents. Summaries in other languages are for convenience only.

© 2026 IOSOR · All rights reserved.🇨🇭 Switzerland