> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-job-entries-reference-overview/job-job-entry/options-job-job-entry/logging-tab.md).

# Logging tab

By default, if you do not set logging, PDI will take the generated log entries and create a log record inside of the job. For example, suppose a job has three transformations to run and you have not set logging. The transformations will not log information to other files, locations, or special configurations. In this instance, the job executes and logs information into its master job log.

In most instances, it is acceptable for logging information to be available in the job log. For example, if you have load dimensions, you would want logs for your load dimension runs to display in the job logs. If there are errors in the transformations, they will display in the job logs. However, you want all your log information kept in one place, you must set up logging.

![Logging tab, Job (job entry)](/files/beRlPQQmowEFOtikDbqg)

This tab includes the following fields:

| Option                      | Description                                                                                                                                                                                                                               |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Specify logfile**         | Specifies a separate log file for running this job.                                                                                                                                                                                       |
| **Name**                    | The directory and base name of the log file, for example, `C:\logs`.                                                                                                                                                                      |
| **Extension**               | The file name extension, for example, `.log` or `.txt`.                                                                                                                                                                                   |
| **Log level**               | Specifies the logging level for running the job. See [Logging levels](/pdia-data-integration/10.2-data-integration/data-integration-perspective-in-the-pdi-client/logging-and-performance-monitoring/logging-levels.md) for more details. |
| **Append logfile?**         | Appends the log file instead of creating a new one.                                                                                                                                                                                       |
| **Create parent folder**    | Creates the parent folder for the log file if it does not already exist.                                                                                                                                                                  |
| **Include date in logfile** | Adds the system date to the file name with the format YYYYMMDD, for example`_20051231`.                                                                                                                                                   |
| **Include time in logfile** | Adds the system time to the file name with the format HHMMSS, for example `_235959`.                                                                                                                                                      |


---

# 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:

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-job-entries-reference-overview/job-job-entry/options-job-job-entry/logging-tab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.