> 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/cortex-xsoar-8-on-prem/8.6/troubleshoot-and-reference/troubleshoot/integration-logs.md).

# Integration logs

The **Integration Logs** table helps monitor, troubleshoot, and analyze performance. It provides visibility into interactions between Cortex XSOAR and external systems, facilitating effective integration management and ensuring the operational integrity of security operations.

Logs are generated for integrations developed with Python or non-python code, for example, JavaScript or PS. Logs include integrations that have verbose or debug-level logging enabled. In addition, integration logs include scripts that are run either manually or via a playbook.

To view integration logs, navigate to **Settings & Info** → **Settings** → **Integrations** → **Integration Logs**.

The integration log table displays log details sorted by date.

{% hint style="info" %}

### Note

All Integration logs are located in the integration logs table in your Cortex XSOAR tenant. If you have an engine, verbose logs (including integration logs) are also stored in the log file on your engine machine.
{% endhint %}

You can view the following data:

| Field           | Description                                                                                                                                                                                       |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Timestamp       | The date and time that the integration created the log.                                                                                                                                           |
| Engine name     | The engine server name that the integration was running on.                                                                                                                                       |
| Log level       | The log level (Debug, Error, or Info).                                                                                                                                                            |
| Command         | The command that the integration ran.                                                                                                                                                             |
| Source brand    | For integration commands, the integration name is listed. For scripts, the source brand is listed as **Automation**.                                                                              |
| Source instance | The integration instance name that was set in the integration instance settings.                                                                                                                  |
| Bundle ID       | A unique identifier for logs generated from a specific integration execution. For example, a bundle ID is assigned for all logs generated from a specific integration command or fetch incidents. |
| Message         | A text message indicating the status or error.                                                                                                                                                    |

You can do the following:

* Update the log table

  To update the log table, click the **Refresh** button.
* Filter by field

  You can filter by log table column, such as log level, brand, or instance name, and you can save filters for later use. You can also adjust the width of the columns and add or remove columns.
* Export logs

  To export the integration log as a **`.tsv`** file, click the **Export to file** button.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.6/troubleshoot-and-reference/troubleshoot/integration-logs.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.