> 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/zarzadzanie-aplikacja-biznesowa/testowanie-i-debugowanie-aplikacji/audyt-aplikacji-biznesowej/logi-diagnostyczne.md).

# Diagnostic logs

Diagnostic logs are **automatically recorded information about the application's operation** – e.g. the executed process steps, system messages, errors, or response time.

Logs are used to analyze problems (e.g. why a given request ended with an error), monitor the correctness of business processes, and support IT teams in quickly finding the causes of errors and incidents. They help ensure the stability and security of the application.

#### Logging levels <a href="#logidiagnostyczne-poziomyloggowania" id="logidiagnostyczne-poziomyloggowania"></a>

* **INFO** – standard information about the course of operation,
* **DEBUG** – details for developers; usually disabled in production so as not to generate excess data.
* **WARN** – warning. The system is working, but something has appeared that may indicate a potential problem.
* **ERROR** – error. The operation failed.

#### Logger in low code <a href="#logidiagnostyczne-loggerwlowcode" id="logidiagnostyczne-loggerwlowcode"></a>

* Logger in the local data source of the data model
* Loggers in ScriptCode (scripts, validators, script tasks) - [Logging in ScriptCode](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/logowanie-w-scriptcode.md) (Logs in unit tests of scripts/validators - [Script unit tests](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/testy-jednostkowe-skryptow.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 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.eximee.com/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/testowanie-i-debugowanie-aplikacji/audyt-aplikacji-biznesowej/logi-diagnostyczne.md?ask=<question>&goal=<endgoal>
```

`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.