Observability

Observability in rstream spans two layers: engine-level telemetry and hosted visibility in the Dashboard.

At the engine level, metrics can be exported through Prometheus and, in enterprise builds, through Influx. The engine can also emit events that summarize connection outcomes.

In the hosted platform, the Dashboard can surface tunnel state and connection logs.

Engine metrics

Prometheus metrics are optional. When enabled, the engine exposes an HTTP handler that serves metrics points under a configurable path, defaulting to /metrics.

The same usage model is emitted to Influx in enterprise deployments through the rstream_usage measurement. Usage points include upstream and downstream byte counts, connection counts, and cumulative connection seconds. Tags include project, workspace, plan, provider, region, tunnel type, publish mode, protocol, agent, channel, version, operating system, architecture, and protocol version.

Event stream and stream summaries

The engine event stream can be consumed over SSE or WebSocket. In enterprise builds, stream summaries are emitted as events of type stream.summary on both success and failure paths. Community builds do not emit these summaries.