Skip to main content
This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone product separate from Palo Alto Networks Cortex XCOR.
The Cortex XCOR Logs destination plugin (name: http, alias: Cortex XCOR) lets you configure your telemetry pipeline to output log data to Cortex XCOR.

Supported telemetry types

The Cortex XCOR Logs destination plugin for Palo Alto Networks Telemetry Pipeline supports these telemetry types:

Configuration parameters

Use the parameters in this section to configure the Cortex XCOR Logs destination plugin. The Palo Alto Networks Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.

General

  • Replace TENANT with the name of your Cortex XCOR tenant.
  • Replace API_TOKEN with the API token generated from your service account. Cortex XCOR recommends storing your API token in a separate file or Kubernetes Secret and calling it using an environment variable, such as $API_TOKEN.

Advanced

Security and TLS

Advanced Networking

Basic Authentication

Example

The following YAML configuration defines a Fluent Bit input and a Cortex XCOR Logs output.