> 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-agentix/onboard-cortex-agentix/post-deployment-steps/log-forwarding/forward-logs-and-data-from-cortex-agentix-to-external-services.md).

# Forward Cortex AgentiX logs and data to external services

Forward Cortex AgentiX logs, cases, and issues to Slack, syslog, email, Splunk, Amazon SQS, Amazon S3, and webhooks.

Use Cortex AgentiX log forwarding and data forwarding to send logs, cases, and issues to external services. Forwarded data supports alert management, investigations, and data retention in external systems.

You can forward notifications to these external services:

* **Slack channel and/or syslog receiver:** Configure the external application in Cortex AgentiX. Then configure notification forwarding and select the data or log type.
* **Email distribution list:** Configure notification forwarding and select the data or log type.
* **Splunk, Amazon SQS, Amazon S3, and Webhook:** Forward cases and issues only. Configure the external application in Cortex AgentiX and egress in Cortex Gateway first.

### Supported data types by notification destination

| Data/log type              | Email | Slack | Syslog | Splunk, Amazon SQS, Amazon S3, Webhook |
| -------------------------- | ----- | ----- | ------ | -------------------------------------- |
| Issues                     | ✅     | ✅     | ✅      | ✅                                      |
| Cases                      | ✅     | ✅     | —      | ✅                                      |
| Management Audit Logs      | ✅     | —     | ✅      | —                                      |
| Health Issues (Deprecated) | ✅     | ✅     | ✅      | —                                      |


---

# 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-agentix/onboard-cortex-agentix/post-deployment-steps/log-forwarding/forward-logs-and-data-from-cortex-agentix-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.