Public APIs, exports, and the version registry anchor every downstream observation.
Runtime-authoritative observability
See the system.
Read the signal.
A technical view of StreamSuites operation: measured component health, observation freshness, response characteristics, architecture, and only the watchdog history that actually exists.
Authoritative topology
One nucleus. Every observable path.
Public-safe control and state relationships grounded in the shipped product boundaries. This is not a media-path diagram: Browser Studio, StudioApp, and OBS retain their own media ownership.
Core & identity
Identity and session support beneath the canonical Runtime authority.
Public & web
Public-safe web surfaces that consume Runtime/Auth state and artifacts.
Studio & clients
Separate product and media owners connected through bounded Runtime/Auth edges.
Current component health
Measured, deferred, and external—kept distinct.
Every card is driven by Runtime/Auth’s sanitized projection. A missing direct observation remains Unknown; it never inherits a green state from another source.
Waiting for measured, freshness, and ownership fields.
Signal health
Fresh data is part of health.
An HTTP response is not enough when the observation behind it is old. Runtime timestamps and staleness rules remain authoritative here.
Runtime signal health
Observation freshness
No response received yet.
No cycle timestamp received yet.
Retention status is unavailable.
Independent heartbeat state is unavailable.
Measured response characteristic
Core API response time
No measured Runtime response sample is available.
- Minimum
- —
- Median
- —
- Maximum
- —
- Samples
- 0
Retained observations
Historical health, without backfill.
Every coloured cell is a real retained watchdog bucket. Empty periods are not silently painted green, and unmeasured components do not receive a synthetic row.
- Watchdog-observed availability
- —
- Observation coverage
- —
- Observed downtime
- —
- Observed buckets
- —
The page will show only buckets present in the authoritative projection.
Focus or hover a timeline chip for its exact source range and observation counts.
Observability methodology
Health explains operation. Status explains impact.
/health presents Runtime/Auth-authoritative public observations, freshness, response characteristics, and retained samples. /status remains the place for availability, incidents, maintenance, and user-facing service impact.
- Authority
- StreamSuites Runtime/Auth
- Projection
/api/public/status/diagnostics- Refresh
- Conservative 60-second browser cadence
- Freshness
- Runtime-defined; stale never becomes operational
- External providers
- Separated from StreamSuites-owned components
- Missing metrics
- Unknown, not measured, or no history yet