For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex Cloud RuntimeCortex Cloud

Forward logs and data from Cortex Cloud to external services

Forward Cortex Cloud logs and data to external services for monitoring, analysis, and retention.

You can forward logs, cases, and issues from Cortex Cloud 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 Cloud. 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 Cloud and egress configured in the Cortex Gateway before forwarding to these services.

  • AWS Security Hub: Only issues can be forwarded to AWS Security Hub. The external application must be configured in Cortex Cloud before forwarding. You don't need to configure egress in the Cortex Gateway.

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

Data/log type
Email
Slack
Syslog
Splunk, Amazon SQS, Amazon S3, Webhook
AWS Security Hub

Issues

✓

✓

✓

✓

✓

Cases

✓

✓

—

✓

—

Management Audit Logs

✓

—

✓

—

—

Last updated

Was this helpful?