Agent Validation Monitor

string · required

The agent whose spans the monitor reads. Agent monitors name an agent instead of a table; the warehouse source is derived from it. The value takes one of two forms, told apart by its shape:

• Warehouse platform agents (e.g. Snowflake Cortex, Databricks) — a <database>:<schema>.<name> reference, where <name> is the agent's display name when it has one (otherwise its underlying identifier). No trace_table.
• OpenTelemetry agents — the agent's bare service_name. By default the OpenTelemetry trace store is resolved automatically; set trace_table only when the spans live in a specific warehouse table.

agent: my-otel-agent

string · optional

<database>:<schema>.<table> naming the warehouse trace table that holds an OpenTelemetry agent's spans. Required when the spans live in your warehouse, or when the warehouse holds more than one OpenTelemetry trace table. Omit it for platform agents and for agents resolved from the default OpenTelemetry trace store.

trace_table: "ingest:opentelemetry.traces"

object · required

The predicate tree spans must satisfy (or are flagged for violating). A set of conditions combined by a boolean operator (AND / OR); each condition is a predicate over span fields. Leaf predicates are unary (type: UNARY, e.g. is-null), binary (type: BINARY, e.g. comparison), or raw SQL (type: SQL), and groups can nest.

alert_condition:
  operator: AND
  conditions:
    - type: UNARY
      predicate:
        name: "null"
      value:
        - field: prompts

object · required

The lookback window the condition is evaluated over. time_field must be the ingest_ts field; lookback_in_hrs must be at least 1.

time_filter:
  time_field:
    field: ingest_ts
  lookback_in_hrs: 10

string · optional

The span column used to identify and deduplicate exceptions across runs (for example, span_id). Lets the monitor track the same offending row over time rather than re-alerting on it.

exception_primary_key_column: span_id

boolean · optional

Evaluate the validation at the trace grain rather than per span. When set, only the agent span filter is allowed — span-level refinements (workflow/task/span_name) are rejected. Include it in the template to re-apply at the same grain.

is_agent_trace_aggregation: true

object · optional

A predicate tree (FilterGroup) that further restricts which spans are validated, beyond the agent and the alert condition.

array of objects · optional

Refines the monitor to specific spans (workflow, task, span_name, each an object with a value). The agent is already set by agent. With is_agent_trace_aggregation: true, only the agent dimension is allowed here.

agent_span_filters:
  - workflow:
      value: checkout

object · required

type (fixed or manual), interval_minutes, start_time, timezone. Dynamic schedules are not supported for validation monitors.

schedule:
  type: fixed
  interval_minutes: 60
  start_time: "2025-01-01T00:00:00+00:00"

The shared rule-monitor envelope:

• name string · optional — unique identifier (auto-generated if omitted); renaming creates a new monitor.
• description string · optional — max 512 characters.
• warehouse string · optional — UUID or name; overrides the montecarlo.yml default.
• connection_name string · optional — query engine to use within the warehouse.
• timeout integer · optional — query timeout in seconds.
• notes string · optional — shown in the UI, not in notifications.
• audiences / failure_audiences array of strings · optional — notification channels.
• priority enum · optional — P1–P5.
• event_rollup_count integer · optional — minimum 2; roll up repeated breaches into one incident.
• tags array of objects · optional — name (required) + value (optional).
• data_quality_dimension enum · optional — ACCURACY · COMPLETENESS · CONSISTENCY · TIMELINESS · UNIQUENESS · VALIDITY.
• domains array of strings · optional (required on accounts created after January 2025).