> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/logs/logs-overview.md).

# Logs Overview

Understand Cortex XSOAR 6.14 logs and use log data for system monitoring and troubleshooting.

The Cortex XSOAR logs provide information about events that occur in the system. These logs are a valuable tool in troubleshooting issues that might arise in your Cortex XSOAR environment. The Cortex XSOAR logs are located in `/var/log/demisto/`.

{% hint style="info" %}

### Note

Additional Cortex XSOAR logs are available when you create a log bundle. For information about log bundles, see [Create a Log Bundle](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/logs/create-a-log-bundle.md).
{% endhint %}

| Log     | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| server  | <p>The server log is automatically created and maintained by the server. It consists of a list of all activities performed by the server. It is constantly updated. This is the main log to view if there are problems in the system.</p><p>To quickly locate error messages, search for <strong><code>error</code></strong> in the log. Often, the error messages shown in the log do not indicate a serious problem. Serious errors will appear in the UI as well as in the server log.</p> |
| elastic | Displays a list of all activities associated with Elasticsearch. The elastic log exists only when a Cortex XSOAR environment uses Elasticsearch. Use the information in this log to troubleshoot Elasticsearch issues.                                                                                                                                                                                                                                                                        |
| d1      | The d1 log appears when a Cortex XSOAR Engine is running. The d1 log contains information necessary to debug Engine related issue. The log displays Engine related errors, as well as noting if the Engine is connected.                                                                                                                                                                                                                                                                      |


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/logs/logs-overview.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.