Operating Streaming Hub

Read the Streaming Hub health endpoints: liveness, readiness, build identity, runtime snapshot, and the build-info metric.

This page covers the unauthenticated endpoints that report the state of a running Streaming Hub. To learn who installs and updates the hub, see the Streaming Hub overview.

Health endpoints

---

Endpoint	Behavior
/healthz	Returns 200 unconditionally once the process serves requests, independent of Postgres, Kafka, or application-ingest consumer health.
/readyz	Folds the full probe set. Healthy or Degraded → 200; Down → 503. A Degraded replica still serves requests.
/version	Returns the build identity.
/runtime	Returns a cheap Go-runtime snapshot for incident triage.
/metrics	Serves only the static streaming_hub_build_info gauge.

Dead-letter observations

---

GET /admin/dlq lists the dead-letter observations that Streaming Hub reads from the .dlq topics that producers write. In BYOC, a credential that Access Manager grants the Streaming Hub admin_dlq resource with the get action can read them. Use them to investigate why a producer dead-lettered a record. The hub never re-delivers or replays them.

Next steps

---

How Streaming Hub works

The path an event takes: ingest, match, dispatch, retry, and auto-disable.

Managing subscriptions

Create and manage subscriptions through the API.