Use Chronospheres managed OTel dashboards to find where telemetry is lost

When telemetry goes missing, open the OpenTelemetry Ingestion & Health managed dashboard first: check ingested vs rejected data points and the OTLP response codes. If rejections are high, the problem is your data shape (labels, values); if exporter failure rates are high on the Collectors dashboard, the problem is your collector config or network. Use the batch processor panel to see whether batches are sent by hitting size triggers or timing out, which tells you whether your batch processor sizing is right.

Context: Official Chronosphere docs (Chronosphere-managed dashboards): documents the OpenTelemetry Ingestion & Health dashboard, which shows how much data OTel Collector instances are ingesting, ingested and rejected data points, and OTLP API response codes and latency. The Collectors dashboard visualizes exporter failure rates for sending or enqueueing data points and trace spans, which is how you spot usage and bottlenecks in your exporters. Agents debugging missing telemetry by staring at app logs miss all of this; the managed dashboards are the fastest way to tell whether data never left the collector or was rejected at ingest.