WhereScape — What We Collect

Prizm reads the WhereScape metadata repository only. It never reads the warehouse the repository describes, and it never writes.

​

Catalog and Run History

​

Lineage

Prizm reads source-to-target relationships directly from the repository, without parsing SQL. Lineage nodes are the Load, Stage, Dimension, Fact, and Aggregate tables a job builds, plus the relationships between jobs, tasks, and those objects. Where the source or target is already cataloged by another Prizm connector, Prizm links to that asset by matching database, schema, and table, which gives cross-connector lineage.

​

Alerts and Measures

• Failure alerts. Job Alert Failure and Task Alert Failure fire from run state. A job counts as failed when its status is F, G, or E, or its error count is above zero. A task counts as failed when its audit status is E or F.
• Measures. Freshness, Job Duration, Execution Time, and Rows Affected. See the Overview.
• SLA. You can bind alerts to an SLA policy under Settings → SLA → Policies.

​

What Prizm Does Not Collect

Cubes, Exports, and Host Scripts aren’t collected. Prizm doesn’t profile rows in the warehouse.

​

Next Steps