> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vijil.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Monitor Dome Metrics
> Monitor Dome Guardrail performance and Agent traffic.
Dome Metrics provides visibility into a protected [Agent](/owner-guide/register-agents/registering-agents), including [Guardrail](/concepts/defense/guardrail) activity, blocked traffic, errors, latency, and execution details. Use these metrics to investigate threats, tune protection, and understand Dome's effect on production traffic.
## Open Dome Metrics
Monitor Dome from the Agent whose production traffic you want to review:
1. Open **Agents** in the Console sidebar.
2. Select the Agent you want to monitor.
3. In the Actions row, click **Monitor**.
4. Review the Agent's **Dome Metrics**.
[Dome](/owner-guide/protect-in-production/configuring-guardrails) must be configured for the Agent and sending telemetry before the dashboard can display production data.
## Choose a Time Range
Use the time-range selector to review activity from the last **15m**, **30m**, **1h**, **2h**, **6h**, **1d**, **7d**, or **30d**. Summary metrics, charts, threat information, and events update for the selected range.
Chart timestamps display in UTC.
## Check Protection Status
The status banner provides a quick assessment of the selected time range and shows when the status was last updated. A **Clear** status means that Dome detected no threats during that interval. It does not guarantee that the Agent is free from every threat.
## Review Summary Metrics
The summary cards show the Agent's protection activity for the selected time range:
| Metric | What It Shows |
| - | - |
| **Traffic** | Agent traffic recorded by Dome |
| **Inbound Blocked** | External requests stopped before reaching the Agent |
| **Outbound Blocked** | Agent responses stopped before reaching users because of policy violations |
| **Errors** | Guard failures recorded while processing traffic |
| **Latency P99** | The 99th-percentile latency overhead added by Dome |
**Latency P99** means that 99% of observed Guard operations completed within the displayed time. Track it over time to understand Dome's effect on the slowest requests.
## Read Traffic Charts
The dashboard separates traffic by direction:
| Chart | Traffic Direction |
| - | - |
| **Inbound** | External requests moving toward the Agent |
| **Outbound** | Agent responses moving toward users |
Each chart compares blocked activity with total traffic. Red bars represent blocked requests or responses, while dark bars represent total traffic.
An increase in blocked traffic can indicate:
* Active threats or policy violations
* Guards that are too sensitive for normal traffic
* Changes in user behavior or Agent output
Compare the charts with **Threat Breakdown**, **Guard Performance**, and individual events before changing the Guard configuration.
## Investigate Threats and Guard Activity
Use the dashboard's investigation panels to understand what contributed to the summary metrics:
| Panel | How To Use It |
| - | - |
| **Threat Breakdown** | Review the threat categories detected during the selected time range |
| **Guard Performance** | Identify which Guards are active and where protection may require tuning |
| **Events** | Inspect individual detection events for the selected filter |
Select an event to inspect its details. Use event-level information to determine whether a block represents an expected policy decision, an active threat, or a possible false positive.
## Open Logs and Traces
The **Logs & Traces** panel provides links to the detailed observability tools associated with the Agent:
* **Guard Execution Logs** provides operational output from Guard executions.
* **Trace Explorer** provides request-level traces across Guardrails, Guards, and Detectors.
Follow a link to open the corresponding tool, or use its copy control to copy the URL. These logs and traces are not embedded in the Dome Metrics dashboard.
Use **Trace Explorer** to investigate:
* Why a request or response was blocked
* Which Guards and Detectors ran
* Whether each component flagged content or encountered an error
* Which Guards contributed the most execution time
For instrumentation and trace details, see [Developer Observability](/developer-guide/protect/observability). To query raw telemetry from the command line, see the [Telemetry CLI](/developer-guide/cli/telemetry).
## Interpret Metrics
Healthy behavior depends on the Agent's purpose and traffic. Establish a normal baseline instead of relying on a universal block-rate threshold.
Healthy patterns generally include:
* Traffic that follows expected usage patterns
* Blocked activity that remains consistent with the Agent's risk profile
* Stable P99 latency
* Few Guard errors
Investigate sustained changes:
| Pattern | Possible Cause | Action |
| - | - | - |
| Increasing inbound blocks | Attack activity, new user behavior, or sensitive input Guards | Review **Events**, **Threat Breakdown**, and traces |
| Increasing outbound blocks | Changes in Agent output or sensitive output Guards | Inspect blocked events and review the output Guard configuration |
| Error increase | Guard failures, deployment issues, or telemetry problems | Open **Guard Execution Logs** and verify the Dome deployment |
| P99 latency increase | Slow Guards, resource pressure, or unusually complex content | Review **Guard Performance** and compare Guard execution settings |
| Missing or unexpected traffic | No traffic in the selected interval or missing telemetry | Broaden the time range and verify deployment, Agent traffic, and telemetry |
Telemetry can support security investigations, compliance reviews, and performance analysis. Review trends regularly and compare changes with Guard configuration updates and Agent releases.
## Empty States
Messages such as **No threats detected**, **No guard data available**, or **No events for the selected filter** can be expected when the selected interval contains no relevant activity.
If the dashboard remains empty when you expect data:
1. Select a broader time range.
2. Confirm that Dome is deployed for this Agent.
3. Confirm that the Agent received traffic during the selected interval.
4. Verify that Dome telemetry is reaching Vijil.
## Next Steps
Integrate Dome with the Agent
Adjust the Agent's protection
Configure logs, traces, and metrics
Query raw telemetry
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.