> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ingest metric and trace data

> Learn about the collection methods used to ingest metrics and traces into Palo Alto Networks Cortex XCOR.

Palo Alto Networks Cortex XCOR supports two
[Collectors](#chronosphere-collector-or-opentelemetry-collector) to ingest metric
and trace data, the Chronosphere Collector and the OpenTelemetry Collector.
Cortex XCOR also supports direct metric imports from
[Google Cloud](/ingest/xcor/integrations/server/gcp).

## Chronosphere Collector or OpenTelemetry Collector

Your Collector selection depends on the telemetry data you plan to ingest.

Cortex XCOR recommends using the vendor-supported, optimized, and highly performant
[Chronosphere Collector](/ingest/metrics-traces/collector) for Prometheus discovery and scrape
workloads. This use case typically works best with metrics data.

Use the [OpenTelemetry Collector](/ingest/metrics-traces/otel) if your organization uses
OpenTelemetry SDKs for app instrumentation. An added benefit of using the
OpenTelemetry Collector is you can configure dynamic, remotely configurable
[head sampling](/control/shaping/sample-traces/head-sampling), which is a powerful control
mechanism for managing your tracing costs. Cortex XCOR supports the
[OpenTelemetry JaegerRemoteSampler](https://opentelemetry.io/docs/specs/otel/trace/sdk/#jaegerremotesampler)
head sampling standard for remotely controlling the sampling configuration of
OpenTelemetry SDKs.

| Chronosphere Collector | OpenTelemetry Collector |
| :- | :- |
| Proprietary | Open source |
| Fully supported by Cortex XCOR Support | Exporter configuration support |
| No remote trace sampling support | Remote trace sampling support |

<Note>
  Cortex XCOR doesn't provide customer support for OpenTelemetry components.
</Note>

## Integrations

Cortex XCOR supports these metrics integrations:

<Columns cols={2} rowGroup="2">
  <Card horizontal icon="aws" title="AWS Cloudwatch metrics" href="/ingest/xcor/integrations/server/aws-cloudwatch">
    <p>Configure AWS to stream metrics to Cortex XCOR through CloudWatch Metrics Streams.</p>
  </Card>

  <Card horizontal icon="microsoft" title="Azure metrics" href="/ingest/xcor/integrations/server/azure">
    <p>Connect Cortex XCOR with Azure Monitor to ingest metrics.</p>
  </Card>

  <Card horizontal icon="google" title="Google Cloud metrics" href="/ingest/xcor/integrations/server/gcp">
    <p>Connect Cortex XCOR with Google Cloud to ingest metrics from Google Cloud projects.</p>
  </Card>

  <Card horizontal icon="telescope" title="OpenTelemetry" href="/ingest/metrics-traces/otel">
    <p>Use the OpenTelemetry protocol (OTLP) HTTP endpoint to route metrics from OpenTelemetry.</p>
  </Card>
</Columns>


## Related topics

- [Ingest metrics and traces using the OpenTelemetry Collector](/ingest/metrics-traces/otel.md)
- [Ingest, query, and control your trace data](/overview/types/traces.md)
- [Trace Metrics](/control/shaping/sample-traces/trace-metrics.md)
- [Tracing ingest limits](/administer/limits-licensing/limits/trace-limits.md)
- [Dummy logs, metrics, and traces source plugin](/ingest/pipeline/plugins/source-plugins/dummy.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.