> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/setup-docs/troubleshooting/cms-error-logs.md).

# CMS Error logs

The CMS has a central “error log” which collects messages from all components in the platform  which is a valuable resource when investigating issues.

## How to collect CMS error logs

1. Click the **Settings** section of the main CMS menu
2. Click the **Troubleshooting** tab
3. Use the drop down menu and set **Log Level** to **Debug**
4. Set a date and time in the **Elevate Log Until** field

{% hint style="warning" %}
Ensure that this is set far enough into the future that the system can collect the logs required.
{% endhint %}

#### Export CMS error log file

1. Click the **Advanced** section of the main CMS menu
2. Click Log and use the **Filters** button to set a **from** date and time  
3. Set additional filters to capture the required information
4. Click **Apply Filter**
5. Click the CSV button to export the log file

## Contacting support

Open a new ticket via **My Account** ensuring you provide the following:

* [ ] The **version** of the software that you are using (both CMS and Player)
* [ ] Description of the **issue** you are experiencing
* [ ] Detailed **steps** so that the issue can be recreated by our team
* [ ] Attach the downloaded **log file** to the ticket
* [ ] Provide a **screenshot** of the Player Status page


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/setup-docs/troubleshooting/cms-error-logs.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 `build a script that syncs our docs to a CMS` 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.