TL;DR: In the collector config for Chronosphere, set timeout 30s, retry_on_failure enabled true, and compression to zstd. For gateway deployments use sending_queue num_consumers 50 and watch the queue-size metric; spikes mean you need more consumers. If you see rejected metrics, use the Chronosphere-Metrics-Validation-Response header (SHORT, SUMMARY, or DETAILED verbosity) to get the rejection reasons instead of guessing.

```text
Configure the OTel collector exporter for Chronosphere: 30s timeout, retries on
```

## Fix
1. In the collector config for Chronosphere, set timeout 30s, retry_on_failure enabled true, and compression to zstd.
   Expected: this specific failure stops.
2. For gateway deployments use sending_queue num_consumers 50 and watch the queue-size metric; spikes mean you need more consumers.
   Expected: this specific failure stops.
3. If you see rejected metrics, use the Chronosphere-Metrics-Validation-Response header (SHORT, SUMMARY, or DETAILED verbosity) to get the rejection reasons instead of guessing.
   Expected: the request routes instead of erroring.
4. Context: Official Chronosphere docs (Configure your OpenTelemetry Collector): documents the exporter settings to use when pointing a collector at the Observability Platform.
   Expected: this specific failure stops.
5. Set the exporter timeout to 30s so larger requests do not time out while the upstream system does its internal batching.
   Expected: this specific failure stops.
6. Set retry_on_failure enabled to true so retryable errors are retried instead of losing data.
   Expected: this specific failure stops.
7. Set sending_queue num_consumers (the docs recommend 50 for gateway deployments of OTel Collectors) and raise it if the exporter queue size varies over time.
   Expected: this specific failure stops.

## Details
Compression can be snappy, gzip, or zstd, or none. Agents that leave defaults in place get timeouts and dropped telemetry under load.

## When to use
You hit exactly this: Configure the OTel collector exporter for Chronosphere: 30s timeout, retries on.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
the tool named in the title.