> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# WhereScape — What We Collect

> Preview: the assets, run history, and lineage Prizm extracts from a WhereScape RED metadata repository.

> [!WARNING]
>
> **Preview.** This page describes the planned connector and may change before release.

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

## Catalog and Run History

| WhereScape object | What Prizm stores |
| :- | :- |
| Group | Group, used to organize projects |
| Project | Project, including its active flag and documentation |
| Job | Job asset with name, description, owner, type, priority, status, and schedule fields |
| Task | Task asset with sequence, object type, and action |
| Job run | Run history with status, start, end, duration, and error and warning counts |
| Task run | Run history with status, start, end, message, and rows inserted, updated, and deleted |

## 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](/sources/wherescape/overview.md#pipeline-measures).
* **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

> **[Setup](/sources/wherescape/setup.md)**
>
> Prepare the repository and connect WhereScape.

> **[FAQ](/sources/wherescape/faq.md)**
>
> Common questions about the WhereScape connector.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.