> 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-xdr-5.x/onboard-cortex-xdr/post-deployment-steps/set-up-your-environment/data-and-log-forwarding/forward-logs-and-data-from-cortex-xdr-to-external-services.md).

# Forward logs and data from Cortex XDR to external services

Send Cortex XDR logs, cases, and issues to external services.

You can forward logs, cases, and issues from Cortex XDR to an external service. By forwarding logs and data, you can manage alerts and investigations in external systems and meet data retention requirements. Available services include the following:

* **Slack channel and/or syslog receiver:** Configure the external application with Cortex XDR. After the application is configured, configure notification forwarding, specifying the data/log type you want to forward.
* **Email distribution list:** Configure notification forwarding, specifying the data/log type you want to forward.
* **Splunk, Amazon SQS, Amazon S3, and Webhook:** Only cases and issues can be forwarded to these services. The external application must be configured in Cortex XDR and egress configured in the Cortex Gateway before forwarding to these services.

The following table shows the log types supported for each notification type:

| Data/log type                                                                                                                                                               | Email | Slack | Syslog | Splunk, Amazon SQS, Amazon S3, Webhook |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | ----- | ------ | -------------------------------------- |
| Issues                                                                                                                                                                      | ✓     | ✓     | ✓      | ✓                                      |
| Cases                                                                                                                                                                       | ✓     | ✓     | —      | ✓                                      |
| <p>Agent Audit Logs</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Notice</strong></p><p>Requires an XDR Agent.</p></div> | ✓     | —     | ✓      | —                                      |
| Management Audit Logs                                                                                                                                                       | ✓     | —     | ✓      | —                                      |


---

# 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/cortex-xdr-5.x/onboard-cortex-xdr/post-deployment-steps/set-up-your-environment/data-and-log-forwarding/forward-logs-and-data-from-cortex-xdr-to-external-services.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.