> For the complete documentation index, see [llms.txt](https://knowledge.flyability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.flyability.com/software/inspector/inspector-5/common-workflows/how-to-retrieve-the-inspector-5-logs.md).
# How to retrieve the Inspector 5 Logs
### Quick log retrieval:
**(1)** The most recent log can be quickly accessed by entering the following file path into a Windows file explorer window: %localappdata%\Flyability\Inspector
View from Windows file explorer.
Once opened, save and share this file. Notepad can be used to open this file if not already selected.
### Access Inspector log folder
All logs are stored: C:\Users\User name\AppData\Local\Flyability\Inspector
{% hint style="info" %}
If the **AppData** folder is not visible, select **Show Hidden Folders** from the **(2) View** dropdown menu from any Windows Explorer window.
{% endhint %}
Inspector Log folder as seen from Windows file explorer
**(3)** Only the `log_insp_2026-02-27_13-57-28-706.txt` files are needed. The most recent logs are the best ones to share after recreating the issue..
NOTE: The logs are now sorted in the *opposite* direction alphabetically, newest are at the end (if sorted alphabetically).
---
# 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://knowledge.flyability.com/software/inspector/inspector-5/common-workflows/how-to-retrieve-the-inspector-5-logs.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.