FlowMock

Traffic

Watch live proxy requests across every QA session by default. Filter by teammate with row avatars, or focus on one session for mocking and deep debugging.

On this page

Traffic is the live request feed for an environment. Every proxied call shows up here - method, path, status, timing, and whether a mock or transform applied.

You do not need to pick a session before logs appear. Traffic is observability-first: watch first, claim identity when you need mocks.

All sessions by default

Open Traffic and you see requests from every active QA session on that environment.

  • Each row shows a session avatar so you can tell whose request it is
  • Hover the avatar for the session name (and You when it is your claimed session)
  • Use the Sessions filter in the toolbar to narrow to one or more teammates
  • Shareable URL params keep filters (including sessions=…) when you copy the link

Clearing the Sessions filter (or choosing All sessions) returns to the full feed. Avatars stay visible while you are in this multi-session view - even if you filter down to a single teammate in the toolbar.

Focused mode (one session)

When you need a calm, single-person stream:

  1. In the session strip, claim You, choose Return to my session, or View as a teammate
  2. Traffic locks to that session only
  3. Row avatars and the Sessions multi-select hide (everything is already from one person)

Switch back with All sessions in the session picker. Your claimed identity (and its mocks) stay in effect while you watch everyone.

Filters and live tail

Beside Sessions you can filter by:

  • Search (path or status)
  • Only errors / mocked / transformed
  • Status buckets (2xx, 3xx, 4xx, 5xx)

Toggle Live to pause the stream, Clear to hide older rows for the current Traffic scope (focused session, filtered sessions, or all), and switch Table vs Timeline as needed. Clear only hides rows in this browser tab — refresh restores the full history.

Mocking from a log

Open a row to inspect headers and bodies, then create a mock from the response.

If you have already claimed a session, the draft turns on for you immediately. Without a claimed session, FlowMock still creates a draft — select a session later to turn it on.

Prefer not to hand-edit JSON? Use AI edit on the response: describe the change in plain English ("make all items expired", "return an empty list") and FlowMock rewrites the captured payload. Recent instructions stick around so you can rerun them on the next body.