> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/narzedzia-diagnostyczne.md).
# Diagnostic tools (logs, audit views, FormStore, Cockpit)
## Diagnostic logs
[Diagnostic logs](/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/testowanie-i-debugowanie-aplikacji/audyt-aplikacji-biznesowej/logi-diagnostyczne.md).
## Audit views
### Linux terminal
On the server, logs are usually located in the directories **/var/log/eximee** and **/var/log/eximee\_sensitive**.
We most often refer to the file **eximee\_platform.log**, which initially provides the most information.
It is worth knowing a few basic commands:
* **cd** – change directory,
* **cat**, **less** and **more** – for viewing logs,
* and **grep** – for searching for specific entries. E.g.: grep "ERROR" /var/log/eximee/eximee\_platform.log, This command will search for all lines with errors in the log file.
### Kibana
**Kibana** is a tool that can be used to browse and analyze logs and test data that have been previously collected and stored in the system (e.g. in Elasticsearch).
It enables:
* viewing logs from system operation in an organized, readable form,
* filtering data according to various criteria (e.g. operation ID, date, status, or error type),
* quickly searching for specific events and analyzing their course step by step,
* identifying errors and checking when and under what conditions they occurred,
* creating simple visualizations (e.g. charts) that help spot recurring problems or patterns.
Figure 1. Sample Kibana interface.
## EximeeBPMS Cockipit
Learn more: [EximeeBPMS Cockpit](/documentation/documentation-en/eksploatacja-aplikacji/obsluga-procesow/eximeebpms-cockpit.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.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/narzedzia-diagnostyczne.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.
