> 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-v7/dataflows/data-logging-and-profiling/record-level-log.md).

# Record Level Log

A *Record Level Log* captures the status (Success, Error, Warning, or Skip) for each of the records transferred, and includes snapshots of the source record and the destination record. It also provides additional details, such as error messages.

You can have any number of *Record-Level Logs* on the dataflow. Each *Record Level Log* will collect the status of the records in the object that it is connected to.

{% embed url="<https://youtu.be/b7XMKdCRn84>" %}

## **Using Record Level Log**

In this case, we have a simple dataflow performing a data quality check process. It contains a *Customers* dataset stored in an[ *Excel Workbook Source*](https://documentation.astera.com/v/astera-data-stack-v7/dataflows/sources/excel-workbook-source). Then, a *Data Quality Rule* is applied to validate data for error and warning checks, and finally, data is written to a *Database Table Destination*.

![](/files/6AsEXcZu5gYfwZ32nJ3x)

If you *Preview Output* for the *Customers* dataset, you will see that some of the records for the *Region* and *Fax* fields are empty.

![](/files/eCwaW8GBJBB7r5HuuiKx)

A *Data Quality Rule* is applied to identify null records in the *Region* field as errors, and empty records in the *Fax* field as warnings. Upon previewing its output you will see that the records that failed to match the rule have returned an error, denoted by a red warning sign.

![](/files/9rWLNIQStXTjiaLTwaoj)

If you hover on these warning signs, it will show you the error message.

Now, when we run this dataflow we want to know of records that passed the validation check, records that failed the validation check, records containing errors, and records that ended in only warnings.

## **Configuring a Record-Level Log Object**

1. To get a *Record Level Log* object from the Toolbox, go to *Toolbox > Data Profiling > Record Level Log*. If you are unable to see the Toolbox, go to *View > Toolbox* or press Ctrl + Alt + X.

![](/files/0SnFgJXywiPphhNS5unX)

2. Drag and drop the *Record Level Log* object onto the dataflow designer.

![](/files/mAmPbzZMosHfywtFaxMt)

You can see that the dragged *Record Level Log* object is empty right now. This is because we have not mapped any fields to it yet.

3. Auto-map the fields from the source object to the *Log* object.

![](/files/JSlduqUkXFQKW9go4ugJ)

4. To configure the *Log* object, right-click on its header and select *Properties* from the context menu.

![](/files/awlJKiR8xJWIquc45Vat)

A configuration window will open. The first window you will see is the *Layout Builder* window. This is where we can create or delete fields, and change their name and data type.

![](/files/RnR7AGcVxjgW8HHndYgL)

5. Click *Next*, and you will be directed to a *Properties* window where you can configure settings for creating the log file.

![](/files/ep1a8lFQFRmTN0VEwtmj)

6. Specify the *Profile File* path where Astera will save this log file. Log files are saved with the .prof extension.

![](/files/RF0euqftU14zh6amBkZx)

7. Specify the *Log Level Type* from the dropdown list.

![](/files/SjK8dU8a0qNafdyEnyrV)

* *All* – all records (including Success records) are logged.
* *Errors* – only error records are logged
* *Warnings* – only warning records are logged
* *Errors and Warnings* – both error and warning records are logged
* *Off* – no logging

In this case, we will select *Errors and Warnings* as our log type.

![](/files/8bMXvBTEgyLgKyZIcTQV)

* *Stop Logging After … Records with Errors* – allows you to limit excessive logging by setting a cap on the maximum number of errors to be logged. The logging stops after the cap has been reached. The default value is 1000 errors.

8. Click *OK*.

## **Executing The Task**

1. After configuring settings for the *Log* object, click on the *Start Dataflow* icon ![](/files/g27XlG7EqEnOL4wYZ6eg)from the toolbar located at the top of the window. A *Job Progress* window will open at this instant and will show you the trace of the job.

![](/files/VXqqOlEI3SPjDz9hBpgc)

2. Click on the log file link provided in the *Job Progress* window.

![](/files/f5ywJkvnZNooUpfwCEUe)

3. *Record Level Log* will open in Astera showing you the status of logged records.

![](/files/bqnjwmarvb4xIVCyCDcc)

Astera stores the error logs in XML format and if you expand each record, it will give you the *Field Name* to which the error/warning message was attached, the *Processing Step* of the data check that resulted in the errors, as well as the error *Message*.

![](/files/jAvqan57qVexbaK3VTlg)

If you click on *View Record*, Astera will show you the field values of the record failing the data quality rule.

![](/files/fVZZEPYWlNxhho7ZF7Xw)


---

# 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-v7/dataflows/data-logging-and-profiling/record-level-log.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.