Skip to main content
A Metric is a single, repeatable measurement PRIZM runs against a piece of your data estate — a table, a column, a warehouse, or two datasets checked against each other. Metrics are what turn a static catalog into a living one: instead of finding out a table stopped updating when a downstream dashboard breaks, PRIZM’s metrics catch it the moment it happens.Every asset carries a set of metrics, visible on its Metric tab (see Asset Details), and every metric belongs to one of six contexts — a lens that determines who the metric is for and what question it answers.

​
The six metric contexts

Operational

Is this asset arriving on time, at the right volume, with the right structure?

Performance

Is the warehouse or system underneath it keeping up?

Structural

What does this column actually look like, value by value?

Business

Does the data satisfy the rules your business cares about?

Reconciliation

Does this data agree with the same data somewhere else?

Semantic

Rolled up from the underlying asset-level scores, how healthy is this business concept overall?
Operational metrics (Volume, Freshness, Schema) and Performance metrics (Usage, Queries, Credits) are auto-generated the moment an asset or warehouse is connected — no setup required. Structural metrics (Distribution, Frequency, Pattern, Statistics) are also automatic: PRIZM profiles every column and generates them for free. Business and Reconciliation metrics are the two contexts you configure yourself, because they encode judgment PRIZM can’t infer on its own — a discount that can’t exceed 100%, or a row count that must match between a source system and the warehouse.
See Metric Overview for the full breakdown of categories and individual metrics within each context.

​
Two questions every metric answers

Under the hood, every metric is configured to answer one or both of these questions:
  • Should this raise an alert if something looks wrong? This is a metric’s Monitor setting. Operational and Performance metrics are always Monitor: Yes — they exist specifically to catch problems in real time and feed Alerts.
  • Should this count toward the asset’s overall trust score? This is a metric’s Score setting. Structural metrics always contribute to score. Business metrics contribute only for the Custom, Conditional, and Standalone types — Behavioral metrics track trends over time and are excluded from scoring, since a trend deviation isn’t the same as a quality defect.
This split matters in practice: a warehouse running slow shouldn’t drag down a table’s data quality score, but it absolutely should trigger an alert. Keeping observability (is something broken right now) separate from scoring (is this asset trustworthy overall) keeps both signals meaningful.

​
The Metrics page

Metric page with summary cards for the metric contexts

The Metric page with a card for each context

Beyond the per-asset Metric tab, PRIZM also rolls all six contexts up into a live, org-wide view on the Metrics page — the fastest way to see the health, performance, and business consumption fitness of your entire data and pipeline ecosystem. Each metric overview and timeline page provides comprehensive information about the metric, including all breaches that have occurred over a given period.. The chart defaults to a 30-day window. Use the date control in the chart header to adjust the range.
Metrics refresh automatically as new data is ingested. To force an immediate update without waiting for the next refresh cycle, click the refresh icon in the top-right corner of the Recent Alerts panel.

​
Import, bulk edit, and cloning

The Metrics page’s More menu offers Select Columns, Download, Bulk Edit, Import, Group by, and Reset Preference.
  • Import opens the Import Metric dialog, the same one used by the Command Center Utility page. It loads metric definitions and related information (details, configurations, and relationships) from a CSV or Excel file, and has a Validated Query toggle. It is not a threshold-only upload. Thresholds are stored in the file’s Threshold Constraint column as structured JSON; see File columns by import type for the full column list.
  • Bulk Edit applies one change to many metrics. You choose a column to edit, and the available columns are Status, Active, Allow Score, and Export. It does not edit threshold values.
Any metric can also be cloned with the copy icon in its row-level actions, which sit alongside edit, schedule, run now, and delete. Cloning is useful for standing up a variant of an existing metric without rebuilding it from scratch.

​
From metric to action

When a metric breaches its threshold, PRIZM raises an Alert with a severity level so you know how urgently to respond. If the underlying problem needs a tracked fix rather than a one-off glance, turn that alert into an Issue and manage it through to resolution.

Explore every metric

The full reference of contexts, categories, and individual metrics — including which ones are auto-generated and which you configure yourself.

See metrics on an asset

How metrics, alerts, and scores surface together on an individual asset’s detail page.
Together, the six contexts and the Metrics page give you two complementary views of the same signal: one org-wide dashboard for a quick pulse check, and one detailed model underneath it for understanding exactly why that pulse looks the way it does.