> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v6/dataflows/data-logging-and-profiling/using-data-quality-mode.md).

# Using Data Quality Mode

In addition to standard logging functionality, Astera provides a special data quality mode which is useful for advanced profiling or debugging. When a dataflow is used in data quality mode, most objects on the dataflow show the *Messages* node with output ports. An example of an object with the *Messages* node is shown below:

![](/files/rD0n1CKc3LOv1G08ledO)

Connecting the *Messages* node’s outputs to another object’s input ports on the dataflow makes it possible to get both summary and record-level statistics for the object’s record set, which is useful for analysis or debugging.

The *Messages* node captures the following statistical data:

* TotalCount
* ErrorCount
* WarningCount
* InfoCount
* MessagesText

The metrics listed above aggregate data for the entire record set.

In addition, *FirstItem, LastItem,* and *Items* sub-nodes provide a way to collect quality control data on a record-by-record basis. The quality control data, such as *ElementName, MessageType,* or *Action*, can be written into a dedicated destination object for record-keeping purposes.

To turn on data quality mode, click the ![](/files/lI4tEIE3sY1c9lBqrxMR)icon a second time turns data quality mode off.

## **Usage**

An example of a dataflow using data quality mode is shown below. Notice that all dataflow objects have Messages node enabled.

![](/files/DA91ditvmMfjZJ4fOtBi)


---

# 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://documentation.astera.com/astera-data-stack-v6/dataflows/data-logging-and-profiling/using-data-quality-mode.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.