> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/operations/clients/log-files.md).

# Manage Log-Files

Learn how to manage App log files of individual users through the admin interface.

To get detailed support information from the PASCOM App in the log file, **Debug Mode** must be enabled in the **Advanced Settings**. This option sets the logging of information about the App to *"Verbose "*, which makes the log file more extensive.

**Important:** That the log file is written daily, it must be saved via the button **Save support info**.

![PASCOM App Debug Mode](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-a026e10b866513beb0780683ccf89f2a8545ceb6%2Fadvanced_settings.en.png?alt=media)

## Read log files with command line parameter

If the PASCOM App is started with the command line parameter **--logcat**, all data in the log database will be output and stored in the user directory in **log.db**.

```
./pascom_Client --logcat // log.db from userDir is taken
```

However, it is also possible to open log data from another user directory by specifying a path to the **--logcat** command. An example of this would be opening log data from mobile Apps.

```
./pascom_Client --logcat "C:/path/to/log.db"
```


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/operations/clients/log-files.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 `build a script that syncs our docs to a CMS` 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.