Setup

​

Creating a query metric

1

Add the metric

1. Navigate to Metric in the top navigation.
2. Click the Add button (⊕).
3. Enter a Metric Name.
4. Select Subcategory: Query from the dropdown.
5. Enter a Purpose description.
6. Click Create.

2

Open the configuration view

Click the metric name to open its detail page. The configuration view exposes:

• Asset — the table or view the metric runs against
• Metadata tabs — Description, Purpose, Rationale
• Query Metric Configuration — SQL editor and rule options
• Threshold
• Semantic context and Owners

3

Set the asset and metadata

Asset: Select the table or view this metric will query. Use the AI-assisted asset selection button to let Prizm suggest an asset based on the metric name and purpose.The Downstream Impact counter shows how many other assets depend on this asset.

Fill in the metadata tabs as needed:

Tab	Content
Description	What this metric measures. Prizm AI can suggest a description based on the metric name.
Purpose	Business justification — why this metric exists.
Rationale	The reasoning behind the specific SQL query chosen.

4

Write the SQL query

The Configuration tab contains the SQL editor where you define the metric logic.Write a SQL SELECT statement that returns a single numeric value. The returned number is the metric value recorded on each run.

-- Example: count of records violating a business rule
SELECT COUNT(*)
FROM orders
WHERE order_total < 0
  AND order_status = 'completed'

​

Rule options

Option	Description
Valid	Treat a non-zero result as the signal to evaluate
Scoring	Include this metric in the asset quality score
Weightage%	Relative weight of this metric in the overall score (default 100)
Pass Criteria	The threshold condition the result must satisfy to pass (e.g., = 0, <= 100)
Export	Include metric results in data exports

Click Validate to execute the query against current data and preview the returned value. Click View prepared query to inspect the full SQL Prizm will execute.

5

Set the threshold

Choose how Prizm determines when to raise an alert on the query result:Automated Threshold — Prizm learns statistical baselines from historical run values and alerts when the result deviates by a configurable number of standard deviations:

Priority	Deviation range	Default
Low	0σ – 1σ	Off — within expected variation
Medium	1σ – 2σ	Off — monitor for drift
High	2σ – 3σ	On — investigation recommended
Critical	≥ 3σ	On — immediate action required

Custom Threshold — Set explicit upper and/or lower bounds on the query result to trigger alerts (e.g., alert if result > 0 for a zero-tolerance rule, or alert if ratio > 0.01 for a 1% tolerance rule).

6

Set semantic context and owners

Scroll down past the Threshold section to complete:

• Semantic context: Assign Domain, Application, Product, Tag, and Dimension to make the metric discoverable and contextually relevant.
• Owners: Set Business owner, Technical owner, and Steward.
• Audience: Restrict who can view this metric’s results.

Click Save Changes when done.

​

Adding parameters to your query

-- Fixed query
SELECT COUNT(*) FROM orders WHERE status = 'failed'

-- Parameterized — value supplied at run time
SELECT COUNT(*) FROM orders
WHERE status = 'failed'
  AND business_date >= {{start_date}}
  AND region = {{region}}

​

Step 1 — Write the SQL with {{param_name}} tokens

• Tokens are case-sensitive: {{Region}} and {{region}} are different parameters.
• The same token can appear multiple times — all occurrences resolve to the same value.
• SOURCE tokens ({{table}}, {{schema}}, {{database}}, {{attribute}}, {{connection}}, {{warehouse}}, {{account}}, {{region}}) resolve automatically from the connected asset — they do not appear in the popup.

​

Step 2 — Save and review detected parameters

​

Step 3 — Run the metric and supply values in the popup

• Parameters with a default show the default value pre-filled — you can accept it or override it.
• Parameters marked Required with no default must be filled before the Run button activates.
• ENUM parameters show a dropdown of allowed values.
• DATE parameters show a date picker.

​

Running via API

POST /api/v1/measures/{measure_id}/run
Content-Type: application/json

{
  "parameters": {
    "start_date": "2026-01-01",
    "region": "NA",
    "min_count": 500
  }
}

​

Running via CLI

dqlabs measures run --id <measure_id> \
  --param start_date=2026-01-01 \
  --param region=NA \
  --param min_count=500 \
  --output json

​

Parameter resolution priority

Caller-supplied value (popup / API / CLI)
  > Metric-level default
    > Validation error (if required and no value found)