> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/administration/system/system-logs-and-tools.md).
# System Logs & Tools
The logs and tools page is used for the technical management of AppControl. The information on this page reflects the operation of AppControl and not the operation of the apps managed by AppControl.
{% hint style="danger" %}
Do not use any of the action in the 'System Tools' tab unless instructed to do so by Blue Storm support. Incorrect usage of these tools can cause data loss.
{% endhint %}
{% hint style="info" %}
By default old log messages are not deleted. Over time the size of the log table can grow to become very large. To delete old log messages do the following:
* Enable the Logging.CleanupDataLogging scheduled event.
* Set the constant Logging.LogHistoryDays to the number of days that you want to retain old log messages.
{% endhint %}
Logs
This tab gives an overview of all logs generated by AppControl. Use these log messages to troubleshoot any unexpected behaviour of the system.
Background Jobs
AppControl uses background jobs to perform tasks such as app scans and policy checks. This tab shows the current and historical status of all background jobs executed by AppControl. Use this information if you encounter problems with policies, scorecards, or other information in AppControl that is not updating as expected.
System Task Queue
AppControl uses task queues to execute jobs in parallel. Use this tab to view which tasks AppControl is currently executing.
System Tools
The tools on this page can be used to manually perform tasks that are usually performed autmatically by AppControl. Only use these tools when instructed to do so by Blue Storm support.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bluestorm.io/administration/system/system-logs-and-tools.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.