> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pentaho-data-integration/data-integration/enterprise-solution/logging.md).

# Logging

{% hint style="info" %}
There are several ways to enable logging in Pentaho Data Integration, depending on how you want to run and monitor your jobs and transformations. Here are some of the methods:

* You can use the **command line tool** Pan or Kitchen to execute the transformation or job with the option `-logfile:"your-log-file.txt"`. You can also specify the log level, the log size limit, and the log record timeout. You can then use any scheduling tool on your system, such as cron on Linux or Task Scheduler on Windows, to run the command at a specific time or interval.
* You can use the **Transformation Properties** or **Job Properties** dialog box in Spoon to create a log table that keeps a history of information associated with your field information. You can specify the database connection, the log table name, the logging interval, and the log record timeout. You can also view the log entries in the Execution Results panel or in the Schedule perspective.
  {% endhint %}

{% content-ref url="/pages/tbbUHeV129ywqLoOaIVm" %}
[Logging](https://academy.pentaho.com/pentaho-data-integration/data-integration/concepts-and-terminology/logging.md)
{% endcontent-ref %}


---

# 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://academy.pentaho.com/pentaho-data-integration/data-integration/enterprise-solution/logging.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.
