Operations

Operational behavior depends on the engine edition and enabled integrations. Community edition builds support Prometheus metrics as an optional emitter. Enterprise builds add additional integrations such as Influx metrics and event storage.

Engine APIs expose live inventory and signaling endpoints under /api. GET /api/clients and GET /api/tunnels return point-in-time state. /api/sse and /api/websocket stream an initial snapshot followed by lifecycle events.

Prometheus metrics

When Prometheus metrics are enabled, the engine exposes a metrics endpoint. The default path is /metrics, and the path is normalized if it is configured without a leading slash.

Prometheus metrics require a listen address to be configured. When the emitter is disabled, no metrics server is started.

Influx metrics and events

Enterprise builds can emit metrics to Influx and can persist event batches. Stream summaries are emitted as events of type stream.summary in enterprise builds, while community builds do not emit these summaries.

CLI event stream

The CLI can subscribe to the engine event stream using rstream events and can optionally forward each event as JSON to a webhook destination.

See Signaling for transport behavior and examples.