Skip to main content
The CXDOT Collector offers configurable integrations to collect telemetry data from various tools, apps, and services and send that telemetry data to Palo Alto Networks Cortex XCOR.

Available integrations

For a list of available integrations for the CXDOT Collector, see CXDOT Collector integrations. You can also browse integrations in the Integrations Hub.

Configure integrations

To configure integrations for the CXDOT Collector, add and update entries in the integrations section of your configuration file. Before configuring an integration that collects logs or traces, enable telemetry egress for that telemetry type.
For information about integration-specific configuration settings, consult the documentation for each integration.
When you configure an integration, the CXDOT Collector manages the components required to collect and route telemetry data to Cortex XCOR. You can configure integration-specific settings as needed, but you don’t need to directly manage OpenTelemetry components like receivers, processors, or pipelines. For example, the following configuration snippet configures collection and timeout settings for the NGINX integration:
values.yaml

Use multiple instances of the same integration

To use multiple instances of the same integration, each instance of that integration must be nested under a unique YAML key. Create unique keys by assigning names to your integration instances. The following example configures three instances of the NGINX integration: an unnamed nginx instance, an instance named bravo nested under the key nginx/bravo, and an instance named charlie nested under the key nginx/charlie.
values.yaml