Total Screens
—
all time
Passed
—
—
Blocked
—
—% block rate
Masked (PII)
—
—% PII rate
Avg Latency
—
ms
P95 Latency
—
ms
TimeGateActionCategoryLatencyPIITrace ID
Waiting for traces…
Analytics
Aggregated metrics across all screening events
Action Breakdown
Latency Timeline (last 30)
Threat Categories
Gate Distribution
Summary Stats
Total screens—
Block rate—
PII detection rate—
Avg server latency—
P95 latency—
Security Events
All blocked screening calls - threats intercepted by GuardEx
Loading security summary…
Threat Category Breakdown
TimeCategoryConfidenceTrace ID
No security events yet.
PII Events
All screening calls where PII was detected and masked
Loading PII summary…
TimeGateEntitiesTrace ID
No PII events yet.
Settings
Dashboard and OTel configuration
OTel Configuration
ExporterIn-process (custom)
SDK versionopentelemetry
Service nameguardex
Tracerguardex
Span processorSimpleSpanProcessor
Dashboard
Refresh interval2 seconds
Max traces shown200
Port7865
API/api/traces · /api/stats
Connect to a real backend (production)
Replace the _InProcessExporter in
guardex.dashboard (run via guardex-dashboard or python -m guardex.dashboard) with OTLPSpanExporter pointing to your Jaeger, Grafana Tempo, Datadog, or Azure Monitor endpoint. GuardEx spans carry all guardex.* attributes automatically - no code changes needed in your app.
Jaeger (local)http://localhost:4317
Datadoghttps://trace.agent.datadoghq.com
Azure MonitorAzureMonitorTraceExporter