Monitor Dome Metrics

Dome Metrics provides visibility into a protected Agent, including 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.

​

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.

​

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: 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: 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: 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. To query raw telemetry from the command line, see the Telemetry CLI.

​

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: 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