WhereScape Overview

Prizm connects to WhereScape RED as a pipeline source, the same way it connects to Airflow or dbt. It reads your WhereScape metadata repository and catalogs groups, projects, jobs, and tasks, collects run history, and traces lineage between the warehouse tables those jobs build. Prizm reads only the repository, never the data warehouse it describes, and it never writes.

​

Why Connect WhereScape to Prizm?

Pipeline Catalog Prizm discovers jobs and tasks, with their owners, types, priorities, and schedules, and organizes them by project and group. Run Monitoring Job and task run history gives you status, duration, error and warning counts, and rows affected, so failures show up in the same Alerts feed as your other pipeline connectors. Lineage Prizm reads source-to-target relationships from the repository for Load, Stage, Dimension, Fact, and Aggregate tables, and links them to assets already cataloged by other Prizm connectors. Quality Propagation DQ scores, alerts, and issues on the tables a job builds can propagate to the job.

​

Supported Repositories

The metadata repository must be on Microsoft SQL Server. Oracle, Teradata, and DB2 repositories aren’t supported. If you run separate Dev, Test, and Prod repositories, each is its own connection with its own catalog.

​

Pipeline Measures

Thresholds are learned from history for each job and task, and alerts need at least 5 runs of history.

​

Current Scope

• Cubes, Exports, and Host Scripts aren’t collected.
• Execution Status, success and failure rate, Tests, and SLA aren’t offered as measures.
• Root cause analysis, circuit breakers, GitHub integration, blast-radius analysis, and cross-environment correlation aren’t part of this connector.

​

Next Steps