> ## 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.

# Install the Chronosphere Collector

> Compare Chronosphere Collector installation methods for collecting metrics with Kubernetes or a standalone binary and for receiving traces.

The Chronosphere Collector can either collect metrics data or receive trace data.
When collecting metrics data, the Collector *pulls* data it scrapes from Prometheus
endpoints. When receiving trace data, an app *pushes* data to a service, with the
Collector behind that service receiving the data.

Regardless of the installation method you use, Palo Alto Networks Cortex XCOR recommends deploying
separate, independent Collectors for metrics and for traces. This distinction means
that a Collector either collects metrics data or receives trace data.

## Collect metrics data

You can install the Collector to retrieve metrics data, either with Kubernetes or as
a standalone binary. When deployed within Kubernetes, the Collector scrapes
Prometheus endpoints exposed on pods, based on pod-level annotations.

### With Kubernetes

You can install the Collector with Kubernetes to collect metrics as:

* [A Kubernetes DaemonSet](/ingest/metrics-traces/collector/install/kubernetes) (recommended)
* [A Deployment](/ingest/metrics-traces/collector/install/kubernetes#install-the-collector-using-a-deployment)
* [A sidecar](/ingest/metrics-traces/collector/install/kubernetes#install-the-collector-as-a-sidecar)

Cortex XCOR recommends installing the Collector as a Kubernetes DaemonSet on each
node in a cluster to:

* Minimize cross-node network traffic within a cluster.
* Eliminate a single point of failure in case one node is offline.
* Provide the ability to switch to a standalone deployment if the Collector is
  using too many resources.

### Without Kubernetes

If you don't use Kubernetes, or want to gather metrics from services not managed by
Kubernetes, you can install the Collector
[as a standalone binary](/ingest/metrics-traces/collector/install/standalone).

<Note>
  Docker images are `multiplatform` builds for both `linux/amd64` and `linux/arm64`.
  Cortex XCOR also offers
  [Linux binaries](/ingest/metrics-traces/collector/install/standalone#download-the-collector-binary-and-make-it-executable)
  for both of these platforms.
</Note>

## Receive trace data

To receive trace data, Cortex XCOR recommends
[installing the Collector](/ingest/metrics-traces/collector/install/tracing) as a Kubernetes
Deployment, typically with a service in front to receive trace data. Your tracing app
pushes trace data to the service, which the Collector receives the data from.


## Related topics

- [Kubernetes Collector installation to retrieve metrics](/ingest/metrics-traces/collector/install/kubernetes.md)
- [Kubernetes Collector installation to receive traces](/ingest/metrics-traces/collector/install/tracing.md)
- [Receive and aggregate metrics from StatsD](/ingest/metrics-traces/collector/addl-metrics/statsd.md)
- [DogStatsD ingestion](/ingest/metrics-traces/collector/addl-metrics/dogstatsd.md)
- [Chronosphere Collector](/ingest/metrics-traces/collector.md)


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