Skip to main content
Guardway captures three complementary views of traffic that hits your gateway:
  • Logs — a flat, filterable table of every HTTP request.
  • Traces — an OpenTelemetry-based timeline showing how each request flowed through guardrails, auth, routing, and the provider.
  • MCP logs — every tool call made through an MCP server attached to the gateway, including request, response, and latency.
All three live under Monitoring in the dashboard.

Logs

Open Monitoring → Logs (/dashboard/monitoring/logs).
Logs table

Filters

FilterNotes
Time rangePresets (1h, 24h, 7d, 30d) or a custom calendar.
GatewayMulti-select. Leave empty for all gateways.
ProviderMulti-select.
SearchMatches request path, model, or API key name.

Columns

Timestamp, method, path, status, duration, provider, model, API key name, tokens (prompt + completion), cost, client IP, and trace ID. Sort on any of them.
Click a row’s trace ID to jump straight to the matching trace.

Traces

Open Monitoring → Traces (/dashboard/monitoring/traces).
Trace detail
A trace is a timeline of the steps a request went through inside the gateway. Each step has an icon:
IconStep
ShieldGuardrail evaluation (PII, hate speech, prompt injection, keyword, IP).
KeyAuthentication and quota check.
RouterRouting rule match + provider selection.
CloudUpstream model call.
CacheCache hit or miss.
Click a step to see its latency, tokens consumed, cost contribution, and any error. The entire trace is time-aligned, so a slow guardrail stands out immediately.

MCP logs

Open Monitoring → MCP logs (/dashboard/monitoring/logs/mcp).
MCP logs
Every call to a tool exposed by an MCP server registered with the gateway is logged here. Columns:
ColumnNotes
TimestampWhen the call was made.
MCP serverThe server that handled the call.
ToolThe tool name.
CallerThe API key or session that invoked the tool.
Statusok, error, or denied (blocked by MCP access rules on the key).
DurationRound-trip time.
Request / ResponseJSON payload, viewable inline.
Filters mirror the Logs view: time range, gateway, and a free-text search that matches tool name, MCP server, or API key name.
If a call shows denied, check the API key’s MCP access settings (see API keys) — the key’s allow/deny list is the usual cause.

Audit logs (local-only)

Audit logs describe administrative actions on a specific gateway (config changes, key rotations, failed auth). They stay on the gateway and are not routed through the cloud monitoring pipeline. View or export them from the gateway’s detail page while the dashboard is connected to it.

Exports

From any of the three views, click Export to download the current filter as CSV or JSON. Exports are assembled locally by the gateway; the cloud dashboard only forwards the query.

You made it to the end of the onboarding

Turn on guardrails

PII, prompt injection, hate speech, keyword filters.

Set up your org

Invite teammates, create teams, issue API keys.