Trace

The Trace module ("Trace Viewer") in PruTAN is a diagnostic tool that lets you search, inspect, and visualize Studio, Sandbox, and Interceptor request transactions along with their complete request → response flow. It provides comprehensive insights into each step of the request lifecycle, enabling developers, testers, and system administrators to troubleshoot issues effectively and optimize their workflows.

Search & Filtering

  • Search bar: find transactions by trace ID, method/operation, URL, status, and more — all through a single search input.
  • Time range filter: narrow results by a start and end date/time. The viewer defaults to the last 24 hours on first load.
  • Scoped to the active team / workspace: results are limited to the currently selected workspace; switching workspaces re-runs the search automatically.
  • Sources covered: Studio, Sandbox, and Interceptor requests.

Transactions List

The left panel lists every matching request with a live count badge (e.g. "50 requests"). Each row shows at a glance:

  • Source icon indicating where the request originated (Studio / Sandbox / Interceptor).
  • Status — green for success, red for failure.
  • Method / operation — colour-coded and dependent on the protocol: HTTP methods (GET, POST, PUT, DELETE) for REST, message types for ISO, and the channel operation (e.g. KAFKA, SQS) for Realtime.
  • Timestamp in your local time.
  • Duration of the request in milliseconds.
  • Request name (taken from the parent or the request itself).
  • URL with a small arrow showing traffic direction — external (red, downward) or internal (green, upward).

The list supports infinite scroll — more results load automatically as you scroll. Clicking any row opens its full details in the right panel.

Request Flow Visualization

When you select a transaction, the right panel renders a Request Flow at the top — an ordered chain of nodes representing every hop the request traveled through. Each node carries its own icon and label corresponding to the module that handled it (Studio, Sandbox, Interceptor, etc.).

  • A straight arrow between two nodes means they are connected (green for internal traffic, red for external).
  • A squiggly line between nodes indicates a disconnected or unknown hop.

Inspecting a specific hop

Each node in the flow is clickable. Clicking a node loads the request/response details for that specific module's hop — for example, clicking the Studio node shows what the request looked like inside Studio, clicking the Sandbox node shows the Sandbox-side view, and clicking the Interceptor node shows the interceptor view.

The Request and Response tab sets below also update to match the clicked module:

  • Studio hops show Pre Requests (request side) and Validation (response side).
  • Sandbox / Interceptor hops show Rules and After Rules tabs on both sides.

Only click nodes that are properly connected (linked with a straight arrow). Nodes connected by a squiggly line represent broken or unknown hops and may not load details correctly when clicked.

Request & Response Details

Below the flow, the details are presented in a two-column Request | Response layout, each with its own tabbed content:

  • Request tabs — Body, Headers, Pre Requests (for Studio requests), and Rules (for Sandbox / Interceptor requests).
  • Response tabs — Body, Headers, Validation (for Studio requests), and Rules / After Rules (for Sandbox / Interceptor requests).
  • The response header bar shows the status code and text (e.g. 200 OK, 404 Not Found for REST; the corresponding result for ISO/Realtime) — green for success, red for failure.

Body Formatting

  • The viewer auto-detects the content type from the response headers and pretty-prints JSON, XML, and ISO bodies for readability.
  • If formatting fails for any reason, the raw text is shown as-is.

Benefits

  • Accelerate debugging — quickly pinpoint the source of errors or unexpected behaviour.
  • Improve transparency — gain a clear view of data flow across complex systems.
  • Enhance security — monitor for anomalies in request handling.
  • Optimize performance — identify bottlenecks and inefficiencies in the request pipeline.

Whether you're working with REST APIs, ISO protocols, or custom integrations, the Trace module ensures that no aspect of your request execution remains hidden.