Skip to main content
Palo Alto Networks Cortex XCOR supports OpenTelemetry ingestion for logs, metrics, and traces. This ingestion process varies depending on your environment, configuration settings, and telemetry type, but always follows the same general path:
  1. Your app is instrumented with the OpenTelemetry SDK to emit telemetry data.
  2. The OpenTelemetry Collector aggregates and processes this telemetry data.
  3. Cortex XCOR ingests this telemetry data through the OpenTelemetry protocol (OTLP) ingestion endpoints.

​
OpenTelemetry support for metrics

You can use the OpenTelemetry Collector to send metrics to Cortex XCOR. Cortex XCOR ingests these metrics through OpenTelemetry protocol gRPC and HTTP ingestion endpoints. To ingest DogStatsD metrics, add the StatsD receiver to the OpenTelemetry Collector. When Cortex XCOR ingests metrics from OpenTelemetry, it converts those metrics to a Prometheus-compatible format. The Live Telemetry Analyzer displays special request metadata relevant to OpenTelemetry metrics.

​
OpenTelemetry support for traces

You can use the OpenTelemetry Collector to send traces to Cortex XCOR. Cortex XCOR ingests these traces through OpenTelemetry protocol gRPC and HTTP ingestion endpoints. You can also use the OpenTelemetry Collector to configure head sampling for traces.

​
OpenTelemetry support for logs

You can use the OpenTelemetry Collector to send logs to Cortex XCOR. Cortex XCOR ingests these logs through an OpenTelemetry protocol HTTP ingestion endpoint.

​
Monitor your OpenTelemetry Collector health and ingestion volume

When you configure the OpenTelemetry Collector to ingest metrics or traces, you can send operational metrics about the OpenTelemetry Collector to Cortex XCOR. Cortex XCOR provides the OpenTelemetry Ingestion & Health dashboard, which displays information about the health of your OpenTelemetry Collector instances and the amount of data they’re ingesting and processing.