Stream telemetry events as Server-Sent Events
Opens a live SSE stream of telemetry events. Each frame has the form id: {seq}\ndata: {envelope-json}\n\n. Sequence numbers are process-monotonic and persist across configuration changes; a Last-Event-ID from any previous connection is valid for resuming the stream. Drops are signaled by gaps in the id field: if the received id is more than 1 ahead of the last-seen id, events were evicted from the buffer. Clients should track the last-seen id to detect gaps. Fresh connections with no Last-Event-ID start from the current sequence and only see new events; pass ?replay=all to start from the oldest retained event instead. The wire shape is the generic TelemetryEvent. For browser events emitted by the Kernel image (or by callers using a documented type), the event's data conforms to the matching Browser*EventData schema, selected by type.
Query parameters
Pass all to start from the oldest retained event. Ring buffer caps at 1024; older events are evicted and surface as a first id greater than 1.
Headers
Resume after this sequence number. Omit or send 0 to start from the current position. Sequence numbers are process-monotonic, so any previous value resumes correctly from that point. Takes precedence over replay when both are present, so SSE auto-reconnect resumes cleanly instead of re-replaying history.
Response
Live SSE stream of telemetry events.