> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/system-maintenance-and-security/system-information/application-logfile.md).

# Application logfile

## Summary

**Application logfile** shows messages generated during operation. These messages can include events, warnings, and errors.

The **Application logfile** is available as a tab on the [System information](/docs/system-maintenance-and-security/system-information/system-information.md) page.

![Application logfile tab](/files/vQnrsCcUyA96BzuZ90KP)

## Notification alert level selection

The **Notification alert level** control sets the minimum severity shown in the **Messages** grid. Only messages at or above the selected level appear.

* **TRACE**: Provides very detailed information, often including step-by-step code execution. Typically used for in-depth debugging.
* **DEBUG**: Fine-grained informational events useful for debugging an application.
* **INFO**: Important events that show the application's progress at a coarse-grained level.
* **WARN**: Potentially harmful situations that might warrant attention but are not necessarily critical errors.
* **ERROR**: Error events that may still allow the application to continue running.

## Messages grid

The **Messages** grid displays application messages that match the selected alert level. Each row shows:

* **Level**: The severity of the message.
* **Timestamp**: The date and time when the message was generated.
* **Class name**: The application class or component that produced the message.
* **Message**: The text describing the event that occurred.
* **Detailed information**: Click the details icon to view additional information in a pop-up.


---

# 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.fact-finder.com/docs/system-maintenance-and-security/system-information/application-logfile.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.