> For the complete documentation index, see [llms.txt](https://docs.telm.ai/telmai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.telm.ai/telmai/integrations/data-quality-external-reporting.md).

# Data Quality External Reporting

This page explains the Centralized DQ Monitor Scan Reporting feature, which generates a comprehensive, standardized report for every Data Quality (DQ) Monitor scan and appends the results to a designated external table. This mechanism centralizes DQ metrics from various sources and monitors, providing a unified, historical view of data quality performance.

***

## Report Structure (External Destination Table Schema)

The external table is the central repository for all DQ scan results. It provides a standardized format that allows users to query and analyze DQ performance across all projects, data assets, and monitors.

| Column Name                 | Data Type          | Description                                                                                                          |
| --------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------- |
| project\_id                 | `Long`             | Identifier for the project where the data asset resides.                                                             |
| data\_asset\_id             | `String`           | Identifier for the specific data asset (e.g., table/stream) being monitored.                                         |
| monitor\_Id                 | Long               | Unique identifier for the Monitor that performed the check. This is the primary key for tracking the rule execution. |
| scan\_timestamp             | `Timestamp`        | The exact time the DQ job completed execution.                                                                       |
| total\_records\_failed      | `Integer`          | Count of records that failed the specific Monitor's check.                                                           |
| total\_records\_scanned     | `Integer`          | Total count of records processed by the job for this check.                                                          |
| record\_id\_attribute\_name | `String`           | The name of the primary key/ID attribute used to uniquely identify records in the data asset.                        |
| record\_id\_sample          | `Array of Strings` | A sample of up to 100 failed record IDs. This sample aids in immediate investigation and debugging.                  |

***

### **User Actionability**

* To check DQ status: Users should query the External Destination Table, filtering by `data_asset_id` and `scan_timestamp`.
* To debug failures: Users can use the `record_id_sample` along with the `record_id_attribute_name` to look up the failing records directly in the source data asset for diagnosis.

***

## Supported Destinations

DQ scan results can be written to the following external storage destinations:

* **Amazon S3**
* **Azure File Storage**
* **Google Cloud Storage (GCS)**

## Configuring Reporting

Reporting is configured via API. Please refer to the [DQ Reporting APIs](/telmai/api-reference/dq-reporting-apis.md) page for the full reference.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.telm.ai/telmai/integrations/data-quality-external-reporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.