> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/inforiver-enterprise-on-prem/how-to-guides/enabling-app-service-logs.md). # Enabling App Service Logs Following are the steps to Enable App Service Logging and Log stream. ### App Service Logs 1. Select Inforiver web app. 2. On the left side menu, click **App Service logs** under **Monitoring** section.

3. In **Application logging** bar on the right**,** select **File System**. 4. In **Quota (MB)**, specify the disk quota for the application logs. 5. In **Retention Period (Days)**, set the number of days the logs should be retained. A minimum of 30 days is a good practice to keep the logs. 6. When finished, select **Save**. To stream logs, you can select **Log stream** menu on the left. --- # 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.inforiver.com/inforiver-enterprise-on-prem/how-to-guides/enabling-app-service-logs.md?ask=&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.