Detect ingestion backpressure between OpenTelemetry, Data Prepper, and OpenSearch before telemetry drops

A practical guide to separate healthy queues, slow pipelines, and OpenSearch rejections before changing limits blindly.

Validate Collector, Data Prepper, and OpenSearch with parity, queue, and rejection metrics so traces, logs, or metrics do not disappear before you can explain the incident.

Created: July 10, 2026

Published: July 10, 2026

Estimated time45 min

LevelAdvanced

Before you startOpenTelemetry Collector exposing internal metrics on :8888 or equivalent.

PlatformsLinux / Docker

WhatsApp X LinkedIn

Linux

Validate from a Linux workstation or bastion with curl, promtool, and access to internal endpoints.

curlpromtooloptional jqnetwork access to Collector, Data Prepper, and OpenSearch

Check Collector metrics

curl -s http://otel-collector:8888/metrics | egrep 'exporter_queue|send_failed|dropped'

Check Data Prepper metrics

curl -s http://data-prepper:4900/metrics | egrep 'recordsIn|recordsOut|buffer|latency'

Check OpenSearch write pressure

curl -s http://opensearch:9200/_cat/thread_pool/write?v

Also available inDetectar backpressure de ingesta entre OpenTelemetry, Data Prepper y OpenSearch antes de perder telemetría

Content locked

This guide requires both steps before full content is available.

○Click “Like” on this guide.
○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.