> 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/9.3-data-integration/pdi-job-entries-reference-overview/transformation-job-entry-cp/options-transformation-job/logging-tab.md).

# Logging tab

By default, if you do not set logging, PDI will take generated log entries and create a log record inside 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 runs 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 want logs for your load dimension runs to display in the job logs. If there are errors in the transformations, they will be displayed in the job logs. However, you want all your log information kept in one place, you must then set up logging.

![Logging tab, Transformation (job entry)](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-7e9a52d8e0696ed47d5a6ebd4037f639532394ec%2FssPDITransformationEntry_LoggingTab.png?alt=media)

The following table describes the options for setting up a log file:

| Option                      | Description                                                                                                                                                                                                                                              |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Specify logfile**         | Specifies a separate logging file for running this transformation.                                                                                                                                                                                       |
| **Name**                    | Specifies the directory and base name of the log file (`C:\logs` for example).                                                                                                                                                                           |
| **Extension**               | Specifies the file name extension (`.log` or `.txt` for example).                                                                                                                                                                                        |
| **Log level**               | Specifies the logging level for running the transformation. See [Logging and performance monitoring](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/logging-and-performance-monitoring.md) for more details. |
| **Append logfile**          | Appends the logfile as opposed to creating a new one.                                                                                                                                                                                                    |
| **Create parent folder**    | Creates a parent folder for the log file if it does not exist.                                                                                                                                                                                           |
| **Include date in logfile** | Adds the system date to the log file, with the format YYYYMMDD such as `(_20051231)`.                                                                                                                                                                    |
| **Include time in logfile** | Adds the system time to the log file, with the format HHMMSS such as `(_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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.