> 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 **information about application operation saved automatically** — e.g. completed process steps, system messages, errors, or response times.

Logs are used to analyze problems (e.g. why a given request ended in an error), monitor the correctness of business process execution, 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 execution,
* **DEBUG** — details for developers; usually disabled in production so as not to generate excessive data.
* **WARN** — warning. The system is working, but something appeared that may indicate a potential problem.
* **ERROR** — error. The operation failed.

#### Logger in lowcode <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](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/logowanie-w-scriptcode.md) (Logs in unit tests of scripts/validators - [Unit tests of scripts](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/testy-jednostkowe-skryptow.md))

## Log sources

| Source                                                                                      | When to use it                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Log viewing tools (Kibana, Argo CD, Grafana)** (application logs and sensitive data logs) | The default place for analysis; the tool depends on the deployment. Kibana and Grafana allow searching logs from many services at once, while Argo CD shows logs from individual service pods. Sensitive data logs also contain the content of service requests and responses as well as script input and output.                                                                                                                                                          |
| **Log files on the application server**                                                     | Deployments without log viewing tools or access to the server via SSH. Reading files, e.g. with the command `grep`, described on the page [Diagnostic tools](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/narzedzia-diagnostyczne.md).                                                                                                                                                                             |
| **EximeeBPMS Cockpit**                                                                      | Process stopped or ended with an incident; checking process variable values.                                                                                                                                                                                                                                                                                                                                                                                               |
| **“Case History” tab in Eximee Dashboard**                                                  | Checking what events the case went through and who performed the task.                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Logs from the user's browser**                                                            | The error occurred in a form on the browser side, and the server logs do not show its cause. After the error occurs, the latest entries from the browser console are sent to the server and saved in sensitive logs. The feature depends on the license and must be enabled in the configuration: [Logging client logs in Eximee logs](https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/webforms/konfiguracja/logowanie-logow-klienckich.md). |
| **FormStore UI**                                                                            | Checking the final state of the request: data and attachments with which it was saved in FormStore (JSON and XML preview). Availability of the feature depends on the license and may not be available in all deployments.                                                                                                                                                                                                                                                 |

{% hint style="info" %}
Logs are saved in two streams: **non-sensitive**, where sensitive data is hidden, and **sensitive**, where they are visible. Access to sensitive logs is sometimes restricted. Index names in Kibana, file paths, and log retention time depend on the deployment.
{% endhint %}

{% hint style="warning" %}
Logs in test environments may be retained briefly, e.g. only for the current day. Entries related to the error should be collected on the day it occurred.
{% endhint %}

### Reading logs from the terminal

On the application server, logs are usually in the directories `/var/log/eximee` (non-sensitive logs) and `/var/log/eximee_sensitive` (sensitive data logs). Basic commands are described on the page [Diagnostic tools](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/testy/narzedzia-diagnostyczne.md). Examples of searching for entries of a single request:

```bash
# all request entries
grep "EXI000000012345" /var/log/eximee/eximee_platform.log

# only warnings and errors for this request
grep "EXI000000012345" /var/log/eximee/eximee_platform.log | grep -E " (WARN|ERROR) "

# error with five entries before it and ten after it, including the stack trace
grep -B 5 -A 10 "EXI000000012345.*ERROR" /var/log/eximee/eximee_platform.log

# all entries for one request (correlation identifier from the error entry)
grep "sci=5d38bf89-8912-4f23-baab-15c09b4f80b9" /var/log/eximee/eximee_platform.log

# view new entries live, e.g. while reproducing the error
tail -f /var/log/eximee/eximee_platform.log | grep "EXI000000012345"
```

## Log entry structure

Each entry consists of the same parts: date and time with time zone, logging level, service name, context tags in square brackets, and message. Example of an entry from opening a form (shortened):

```
2026-11-09 09:10:55.025+0100 INFO --- [webforms] [X-RequestId: ] [X-Forwarded-For: ] webforms : [st=EXI000000012345][sci=5d38bf89-8912-4f23-baab-15c09b4f80b9] Commiting user forms [formInstanceNumber=EXI000000012345, newVersion=2]
```

| Fragment                       | Meaning                                                                                             |
| ------------------------------ | --------------------------------------------------------------------------------------------------- |
| `2026-11-09 09:10:55.025+0100` | Date and time with milliseconds and time zone.                                                      |
| `INFO`                         | Logging level.                                                                                      |
| `webforms`                     | The service that saved the entry (here: the forms service). Service names depend on the deployment. |
| `[st=EXI000000012345]`         | The request session token, i.e. the request number.                                                 |
| `[sci=...]`                    | Correlation identifier: all entries of one request have the same value.                             |
| `Commiting user forms [...]`   | Message.                                                                                            |

Context tags appear only when they have a value, so the form entry has different tags than the process task entry:

| Tag   | Meaning                                                                                                                                                                |
| ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `st`  | Request session token. After the request is assigned a number, this is the request number (`formInstanceNumber`), earlier the session identifier or `no-user-context`. |
| `pb`  | Business key of the process, usually the request number.                                                                                                               |
| `pi`  | Process instance identifier, the same as in EximeeBPMS Cockpit.                                                                                                        |
| `pd`  | Process definition key.                                                                                                                                                |
| `sn`  | Name of the service or task, e.g. a script task.                                                                                                                       |
| `pt`  | Type of process task, e.g. `eximeeScriptCodeTask`.                                                                                                                     |
| `sci` | Request correlation identifier.                                                                                                                                        |
| `sk`  | Session key.                                                                                                                                                           |
| `cn`  | Component name.                                                                                                                                                        |

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fgit-blob-e862930bec1b6534575e7225acc70cb99661b67d%2Fkibana-pola-wpisu-logu.png?alt=media" alt=""><figcaption><p><em><strong>Illustration 1.</strong> Log entry fields selected in Kibana (Selected fields).</em></p></figcaption></figure>

In Kibana, the same values are available as separate fields that can be filtered on, e.g. session token, process instance identifier, logging level, and message content. Field names depend on the deployment, for example: `eximee.sessionToken`, `eximee.processInstanceId`, `eximee.processDefinitionKey`, `eximee.log.level` and `eximee.log.data`.

### Data hidden in logs

Fragments surrounded by tags `_SENSITIVE_DATA_START_` and `_SENSITIVE_DATA_STOP_` or replaced by `_SENSITIVE_DATA_` or `#hashed#` mark data treated by the platform as sensitive. Its full content is available in sensitive logs. For entries added using the `Logger` object, all passed arguments are treated as sensitive by default. If an argument does not contain sensitive data, it can be marked with the `nonsensitive()`method so that it is visible without masking also in non-sensitive logs. More information on the page [Logging in ScriptCode](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/logowanie-w-scriptcode.md#logowanie-sensytywne-i-niesensytywne).

## Searching for entries related to the problem

| Search purpose               | What to search by                                         | Where to get the value                                                                                                                                                                                                                                                                                                                |
| ---------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| All entries of one request   | Request number (`formInstanceNumber`, session token `st`) | Parameter `stkn` in the form URL, session variable `formInstanceNumber`; more: [Form, process, and data model identifiers](https://docs.eximee.com/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/testowanie-i-debugowanie-aplikacji/audyt-aplikacji-biznesowej/identyfikatory-formularza-procesu-i-modelu-danych.md) |
| Process entries              | Process instance identifier (`pi`) or business key (`pb`) | EximeeBPMS Cockpit, Eximee Dashboard                                                                                                                                                                                                                                                                                                  |
| Script or validator calls    | Artifact name                                             | Eximee Designer                                                                                                                                                                                                                                                                                                                       |
| External service calls       | Service name or part of the address                       | Application RestApi configuration                                                                                                                                                                                                                                                                                                     |
| Entries of one request       | Correlation identifier (`sci`)                            | Any entry of that request                                                                                                                                                                                                                                                                                                             |
| Occurrences of a known error | Error message fragment                                    | Error screen, report                                                                                                                                                                                                                                                                                                                  |

Search is always narrowed to the time range in which the problem occurred.

{% hint style="info" %}
At the beginning of the session, before a request number is assigned, the field `st` in log entries contains the session identifier. The assignment of the number is recorded in the entry `SessionToken switched: <identyfikator sesji> -> SessionToken: <numer wniosku>`. Therefore, errors occurring while opening the form should also be searched for by session identifier.
{% endhint %}

## Step-by-step analysis of a form or process error

{% stepper %}
{% step %}

### Collecting identifiers

Record the request number, environment, date and time of the error with time zone, and the text of the message shown on the screen, and in the case of a case error in a process, also the process instance identifier.
{% endstep %}

{% step %}

### Finding request entries

In Kibana, set the time range covering the error and search by the request number; with a large number of entries, the level filter helps `WARN` and `ERROR`. In Argo CD, search for the request number in the logs of the service pod to which the error relates, e.g. the form or process task logs.
{% endstep %}

{% step %}

### Checking the last operations before the error

After sorting entries by time, analyze the last few entries before the first `WARN` or `ERROR`: which scripts, validators, and services were called and with what result.
{% endstep %}

{% step %}

### Identifying the component that reported the error

The service name and tags indicate where the error occurred: in the form (`st`), in a script or validator (artifact name in the message), in a process task (`pi`, `pd`, `sn`) or in an external service (HTTP response status).
{% endstep %}

{% step %}

### Going to the relevant source

* Script or validator error: [How to debug a script](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/jak-debugowac-skrypt-krok-po-kroku.md).
* Process error: [Process debugging](https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/obsluga-procesow/eximeebpms-cockpit/debugowanie-procesow.md), tab **Incidents** and **Variables**.
* External service or platform error: gather information from the [Problem escalation](#eskalacja-problemu) section and pass the problem on.
  {% endstep %}
  {% endstepper %}

## Most common messages and their meaning

| Message in the log                                                                                       | What it means                                                                                                                                                                                | Where to look next                                                                                                                                                                                                                                                                                       |
| -------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Script service call [name=<skrypt>, input=...]` and `Script service called [name=<skrypt>, output=...]` | Script call on the form: input and result. If there is no second entry, the script did not complete successfully.                                                                            | Entries `ERROR` with the same `sci`; [How to debug a script](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/jak-debugowac-skrypt-krok-po-kroku.md)                                                                                               |
| `WARN` with the business exception message                                                               | The script deliberately interrupted execution with a business exception, and the user saw a business error page. This is intended application behavior, not a platform failure.              | Condition in the script that throws an exception; [Business errors](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/strony-bledow.md#bledy-biznesowe)                                                                   |
| `Caused by: ...` with a stack trace                                                                      | Unhandled exception. The first line `Caused by` usually indicates the direct cause, e.g. `java.lang.ArithmeticException: / by zero`.                                                         | [How to debug a script](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/jak-debugowac-skrypt-krok-po-kroku.md), execution error section                                                                                                           |
| `Script failed, bpmn error [errorCode=<code>, cause=<task>: Error from service]`                         | The process script task ended with a BPMN error because the service returned an error. The process follows the error-handling path or stops with an incident.                                | Adjacent entry `ERROR` with the same `pi` and the service response status; EximeeBPMS Cockpit                                                                                                                                                                                                            |
| `NetworkExceptionPayload(status=Status(code=<code>...`                                                   | The external service responded with an HTTP error. `401` and `403` indicate missing permissions or authorization, `404` a wrong address or missing data, `5xx` an error on the service side. | Application RestApi configuration; service owner                                                                                                                                                                                                                                                         |
| `ServiceSecurityException ... IEW_SECURITY_VALIDATOR_CHARACTER_WHITE_LIST`                               | The value contains a character outside the allowed list, e.g. `#` or `&`, and was rejected by security validation.                                                                           | Property **Character whitelist** (`extraWhitelistCharacters`) of the field or parameter: [Common properties of components](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/wspolne-wlasciwosci-komponentow.md) |
| `ERROR` without a request number, recorded when the service starts, e.g. about a cache connection        | Technical message from the service, unrelated to the analyzed request.                                                                                                                       | Can be skipped if it does not coincide in time with the error; a recurring message should be reported to the maintenance team                                                                                                                                                                            |

### Example: service error in a process script task

The process checking client data stopped at a task sending a request to an external service. In the process logs, there are two entries with the same millisecond (shortened):

```
2026-11-09 08:44:21.289+0100 WARN --- [process-task-runtime] ... : [pi=01a17cd7-0e4d-7158-bcd3-4482945befa0][pd=sprawdzenieKlientaSubprocess][sn=wyslijZapytanieScriptTask][pt=eximeeScriptCodeTask][sci=d6637ffa-...] Script failed, bpmn error [errorCode=ERR_SENDREQUEST, cause=wyslijZapytanieScriptTask: Error from service]
2026-11-09 08:44:21.289+0100 ERROR --- [process-task-runtime] ... : [pi=01a17cd7-0e4d-7158-bcd3-4482945befa0][pd=sprawdzenieKlientaSubprocess][sn=wyslijZapytanieScriptTask][pt=eximeeScriptCodeTask][sci=d6637ffa-...] wyslijZapytanieScriptTask error: _SENSITIVE_DATA_START_NetworkExceptionPayload(status=Status(code=403, message=null), body={"errors":[{"code":"9","message":"Request has been UNAUTHORIZED"}]})_SENSITIVE_DATA_STOP_
```

What they indicate:

1. `pt=eximeeScriptCodeTask` and `sn=wyslijZapytanieScriptTask` — the error occurred in a process script task, not on the form.
2. `pd` and `pi` — indicate the process and instance affected by the error. After `pi` the instance can be found in EximeeBPMS Cockpit.
3. `Error from service` and `code=403` with the message `UNAUTHORIZED` — the service rejected the request due to missing permissions. The cause lies in the service access configuration, not in the script logic.
4. `errorCode=ERR_SENDREQUEST` — the process received a BPMN error with this code; the path that handles it is shown by the process model.
5. The same error repeats for many instances — this is an environmental problem (service access), which should be passed to the service owner or the maintenance team.

### Example: value rejected by the character whitelist

The user entered the value into the form `ABC#123`. In the form service logs there is an entry (shortened):

```
ERROR ... Exception during HTTP request [request=_SENSITIVE_DATA_, exception=internalException, exceptionCode=1794210327913, clientIp=_SENSITIVE_DATA_]
...ServiceSecurityException: Security violations found in service params [result=SecurityValidationResult(violations=[ServiceSecurityViolation(super=SecurityViolation(exceptionMessage=Invalid chars in string: ABC#123, level=WARN, validationMessageKey=IEW_SECURITY_VALIDATOR_CHARACTER_WHITE_LIST), ...)])]
```

What it indicates:

1. `Invalid chars in string: ABC#123` — rejected value; character `#`.
2. `IEW_SECURITY_VALIDATOR_CHARACTER_WHITE_LIST` — the cause is validation of allowed characters, not a script error.
3. The character required by the business is added to the **Character whitelist** property of the field that accepts this value, after verifying that the services receiving the value are prepared for it.

## Problem escalation

The problem is escalated when the cause lies outside the lowcode application: an external service returns an error, the environment is unavailable, the error points to the platform, or the same error occurs in many unrelated requests.

Before escalation, collect:

* the request number and, if applicable, the process instance identifier,
* the environment,
* the date and time of the error with time zone,
* the application name and artifact version affected by the error,
* the message text visible on the screen,
* a log fragment with entries `WARN` and `ERROR` and a few entries before them, without sensitive data,
* a description of the steps leading to the error, and information on whether the error repeats.

{% hint style="warning" %}
The report must not contain personal data, passwords, or tokens. Sensitive data is removed from the fragment taken from sensitive logs.
{% endhint %}


---

# 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/zarzadzanie-aplikacja-biznesowa/testowanie-i-debugowanie-aplikacji/audyt-aplikacji-biznesowej/logi-diagnostyczne.md?ask=<question>&goal=<user_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.
