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

# Debug log files

Where the debug output goes and how long it is kept. Switching it on is described in [Produce a debug log for a bug report](/antiredstoneclock-remastered/how-to-guides/produce-a-debug-log-for-a-bug-report.md).

|               |                                                       |
| ------------- | ----------------------------------------------------- |
| Directory     | `plugins/AntiRedstoneClock-Remastered/debug-logs/`    |
| Current file  | `latest.log`                                          |
| Rotated files | `<yyyy-MM-dd>-<n>.log.gz`                             |
| Rotates       | on every server start, and once the file passes 10 MB |
| Retention     | `debug.keepFiles` rotated files, default `5`          |
| Written by    | the server's own Log4j2                               |
| Source        | `DebugLogging`                                        |

Debug messages go to this file only and never to the server log, because they are far too noisy for it. Warnings and errors go to both, so the file holds the whole picture when it is attached to a bug report.

On a server that does not run on Log4j2 the file cannot be written. The server log says so at the moment debug logging is switched on.


---

# 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.onelitefeather.net/antiredstoneclock-remastered/reference/debug-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 `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.