Why Observability?
Defense without observability is flying blind. You need to know what is happening with your protected agents, not just that Guardrails are running, but what they are catching, how often, and what patterns are emerging. Dome includes built-in telemetry that captures the full picture of agent behavior in production. This data serves three purposes:- Operational visibility: Are your Guardrails working? What is getting blocked? What is the latency impact?
- Security monitoring: Are you seeing attack patterns? Anomalous behavior? Escalating threats?
- Continuous improvement: What is happening in production that evaluation did not anticipate?
Telemetry
Dome automatically captures telemetry from every protected interaction. When instrumented by the developer, this includes:Execution Traces
Full traces of LLM and tool execution:Instrumentation
To capture full traces, instrument your agent with Dome’s SDK:Metrics
Dome aggregates telemetry into operational metrics:Protection Metrics
Latency Metrics
Guard-Level Metrics
Metrics are available via API, dashboard, and can be exported to your observability stack (Datadog, Prometheus, etc.).
Logs
Dome generates structured logs for every significant event:Detection Logs
When a Guard detects a threat:Audit Logs
For compliance and security review:Dashboard
The Dome dashboard provides real-time visibility:- Overview: Block rates, latency, active agents
- Guard performance: Which Guards are triggering, at what rates
- Threat timeline: Detection events over time
- Drill-down: From metric to trace to individual interaction
Next Steps
Observe Traces
Monitor Guardrail performance
How Defense Works
The defense architecture