Live events
Follow live metadata while keeping capture and connection state separate.
Live connection and history
Live uses a server-sent event connection for event metadata within the selected organization/source. It can reconnect after interruption; a reconnect does not prove that every event in the gap was replayed.
When a pause or disconnect leaves a gap, use Refresh recent events to reconcile up to the latest 50 persisted events in the selected organization. Open Events and page through history for older events. Reconnection and refresh do not guarantee every event in a longer gap.
Two pause controls
J/K navigate events on the source detail page; P toggles source pause there. Do not confuse that shortcut with pausing only the Live view.
- Pause Live closes the view’s connection. Incoming capture continues independently.
- Pause source changes the source: new requests can receive an explicit dropped acknowledgement and are not captured. Resume source affects future requests, not previously dropped bodies.
Metadata and details
Filter the current buffer by source name. The signature indicators show the valid percentage and invalid count. Received describes capture. When available, original delivery state and its recorded HTTP response are shown separately; an uncertain outcome remains explicit. Live counters cover the current event buffer, not the complete organization.
Request detail contains permitted headers, content availability and original delivery state. Titles preserve semantic types or fall back to the declared Content-Type. Copy the visible event ID to correlate x-acklane-id. Signature shows the recorded result/reason; Replays shows separate deliveries. Live entries are receipt snapshots, not a stream of delivery updates.
Raw body is absent from SSE and list caches. Changing organization, event or closing the body view clears the private content.