> ## 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 additional metrics

> Ingest Carbon, StatsD, SignalFx, Wavefront, and other metric formats with the Chronosphere Collector, and enable client-side aggregations.

Scraping metric endpoints is the preferred method of ingesting metrics to the
Chronosphere Collector, but you can also ingest the following metric formats:

* [Carbon](/ingest/metrics-traces/collector/addl-metrics/carbon)
* [DogStatsD](/ingest/metrics-traces/collector/addl-metrics/dogstatsd)
* [Prometheus and OpenMetrics](/ingest/metrics-traces/collector/addl-metrics/prom-openmetrics)
* [Pushgateway](/ingest/metrics-traces/collector/addl-metrics/prom-pushgateway)
* [SignalFx](/ingest/metrics-traces/collector/addl-metrics/signalfx)
* [StatsD](/ingest/metrics-traces/collector/addl-metrics/statsd)
* [Tagged StatsD](/ingest/metrics-traces/collector/addl-metrics/tagged-statsd)
* [Wavefront](/ingest/metrics-traces/collector/addl-metrics/wavefront)

## Enable aggregations

You can enable client-side aggregations for
[Carbon](/ingest/metrics-traces/collector/addl-metrics/carbon),
[StatsD](/ingest/metrics-traces/collector/addl-metrics/statsd), and
[Datadog DogStatsD](/ingest/metrics-traces/collector/addl-metrics/dogstatsd) metrics.
These aggregations reduce network egress and processed writes to Palo Alto Networks Cortex XCOR.

When the Collector ingests a data sample, it aggregates the data based on the metric type
and sends a single data point to Cortex XCOR that represents the sample for
the defined period. The Collector aggregates on the following metric types:

* Counters, which are rolled up through addition.
* Gauges, which are selected by the last value written.
* Timers, which use sketches of the underlying sample to build quantiles.

Aggregations are disabled by default. To enable aggregations, define the
`push.PROTOCOL.aggregation` YAML collection in your Collector manifest, where
*`PROTOCOL`* can be `carbon`, `dogstatsd`, or `statsd`. For example, the following
YAML collection enables aggregations for StatsD with defined values for each of the
supported metric types:

```yaml theme={null}
push:
  statsd:
    aggregation:
      counters:
        interval: "10s"
      gauges:
        interval: "10s"
      timers:
        interval: "10s"
      inactiveExpireAfter: "2m"
```

* `interval`: Defines the length of time before writing to Cortex XCOR.
  A longer `interval` duration provides more effective caching, but also increases
  the length of delays before writing.
* `inactiveExpireAt`: Determines the length of time before Cortex XCOR evicts unused
  keys from the local cache. Default: `2m`.


## Related topics

- [Kubernetes Collector installation to retrieve metrics](/ingest/metrics-traces/collector/install/kubernetes.md)
- [Chronosphere Collector](/ingest/metrics-traces/collector.md)
- [Ingest AWS CloudWatch metrics](/ingest/xcor/integrations/server/aws-cloudwatch.md)
- [Ingest DogStatsD metrics with the OpenTelemetry Collector](/ingest/metrics-traces/otel/ingest-dogstatsd.md)
- [Prometheus and OpenMetrics ingestion](/ingest/metrics-traces/collector/addl-metrics/prom-openmetrics.md)


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