> For the complete documentation index, see [llms.txt](https://docs.monokot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monokot.io/basics/administrator-gui/event-log.md).

# Event Log

The event log records errors, warnings and informational messages that occur during server operation, and is a diagnostic and troubleshooting tool. The event log is stored in the root folder of the server in the logs subfolder. Event log can be viewed via the Monokot Server Administrator or Web API.

To open a event log in the Monokot Server Administrator, on the *Server Explorer* pane double-click on *General* and go to *Event Log* tab.

![](/files/xyOFWgs0d7R4y5oYDnoQ)

You can sort the event log by message type, date and time, message source by clicking on the corresponding column in the table. To save the event log to a file click the *Save...* button and specify the path and file name. To view the current version of the event log, click on the *Refresh* or *Sync* button. Use *Errors*, *Warnings* or *Messages* checkboxes to filter messages by type.


---

# 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.monokot.io/basics/administrator-gui/event-log.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.