Request Rally guide
Read the traffic. Colour identifies the client in both directions; shapes identify response types. The key shows each theme's symbols. A bolt below a response means a cache hit.
HTTP. Requests bounce off the solid paddle. Status codes appear on the return journey; larger responses produce larger shapes. Both paddles flash the client's colour on contact.
WebSockets. IN frames travel from the client to the segmented server paddle and stop there. OUT frames travel from that paddle to the client. Each shape represents one logged frame, moving only in its logged direction; a reply appears only when an OUT frame is logged.
Connection lines. Waving lines appear after OPEN or the first observed transfer and disappear on CLOSE. Connections sharing endpoints share a line until the last closes. Reconnecting clears uncertain state; new opens and transfers rebuild it.
Inspect. Pause beside the gear, then click or tap a shape for details. Select C1, C2, etc. for client addresses. Pause freezes motion and mutes sound; counters and connections stay live. Play resumes without replaying traffic received while paused.
Hiding or leaving this page disconnects monitoring. Returning reconnects the feeds without replaying missed traffic.
Settings. Use the gear for filters, animation pace, labels, themes, sound and volume. Themes change the artwork, lines, key and instruments; your theme is remembered. Sound starts enabled and may need a first tap. Client notes play on the left; RCWeb server notes play on the right. Dark and Light spread short bursts into chime sequences; heavy traffic is sampled. Auto labels reduce clutter.
Clients and destinations. Both lists adapt to screen height, with up to 48 entries and distinct client colours. Destinations show request paths without query strings. Select a path to read it in full. Inactive destinations expire, freeing space for open connections in the overflow group. “Hidden Secure info” means the entire URL was redacted.
Counts. Missing or invalid HTTP status codes are treated as 500. HTTP requests and WS frames count once, even when filtered; OPEN and CLOSE add no transfers. WS open follows filters; FPS beside WS live is the animation frame rate. Travel time is animation, not latency. HTTP logs arrive after completion. Skipped visuals are counted; missed traffic during disconnection is not replayed. Other viewers' monitoring requests and connections appear under their paths; this page's own feeds are hidden. The server excludes outgoing WebSocket-log deliveries to prevent a feedback loop.