> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/java/no-log-files-generated.md).

# No Log Files Generated

Logging is configured, but doesn't yield any log files

In case you encounter issues with the creation of log files when using the Java agent, please adhere to the following steps:

1. Ensure all logging parameters are properly configured
2. Configure the following flag as a JVM parameter in the specified application:

{% code overflow="wrap" lineNumbers="true" %}

```
sl.redirectStreamsTo=/path/to/log/folder
```

{% endcode %}

3. Restart your application server.

This method is to be used for debugging purposes only & should be removed once the required information has been retrieved.\
Under no circumstance should it be used as a replacement for logging parameters.

### Related articles <a href="#related-articles" id="related-articles"></a>

* [3-Component Integration Build](/knowledgebase/setup-and-configuration/build-and-test-execution/integration-build/3-component-integration-build.md)
* [Configure Pull Request Flow for SeaLights](/knowledgebase/setup-and-configuration/integrations/pull-request-integration/configure-pull-request-flow-for-sealights.md)
* [Sealights Agent Updates](/knowledgebase/setup-and-configuration/troubleshooting-faq/others/sealights-agent-updates.md)
* [Java Keystore: Add Certificate](/knowledgebase/setup-and-configuration/troubleshooting-faq/java/ssl-certificate-errors/java-keystore-add-certificate.md)
* [Using SL Multiprofiler with DataDog on IIS (Windows)](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/.net-core-agent/multiprofiling-running-sealights-side-by-side-with-other-profilers/using-sl-multiprofiler-with-datadog-on-iis-windows.md)


---

# 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.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/java/no-log-files-generated.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.