Skip to main content
Ultra records a trace record for every MCP operation. Traces capture the full lifecycle of a request — what was called, what arguments were sent, what came back, and how long it took.

​
Trace Record Structure

Each trace record contains:

​
Multi-Tenant Fields

When connected to Ultra Hub, traces also include:

​
Operation Types

​
Querying Traces

Traces are stored locally and can be queried through the dashboard.

​
Dashboard

The dashboard at http://localhost:8080 provides:
  • A list of all traces, sorted by timestamp
  • Filtering by operation type, upstream server, status, and time range
  • Full request/response payload inspection for each trace
  • Duration and status breakdown
  • A Copy link button on each trace to share a deep link to it, and an Export control to download the filtered trace list as CSV or JSON (see Exporting table data and Sharing links)

​
Aggregate Statistics

Aggregate statistics are computed over your traces:
  • Total requests — Count of all operations
  • Success/error counts — How many succeeded vs failed
  • Average duration — Mean operation time
  • Requests by type — Breakdown by operation type
  • Requests by server — Breakdown by upstream server

​
OpenTelemetry Compatibility

Trace IDs and span IDs follow the W3C Trace Context specification, making Ultra traces compatible with any OpenTelemetry-compatible backend. See OTLP Export for configuration.