Observability Guides
EspañolEnglish
← Back to guidesGuide

Enrich telemetry with the OpenTelemetry lookup processor without cardinality spikes or backpressure

A practical guide to adding context in the Collector with timeouts, cache, internal metrics, and a cardinality canary.

Learn how to use lookups in the OpenTelemetry Collector without turning the pipeline into a source of latency, queues, or explosive attributes.

Created: July 31, 2026

Published: July 31, 2026

Estimated time38 min
LevelAdvanced
Before you startOpenTelemetry Collector running on Kubernetes or Linux
PlatformsLinux
WhatsAppXLinkedIn

Linux

Local Collector validation with a versioned lookup file and internal metrics endpoint.

otelcolcurloptional promtool
Validate configuration
otelcol validate --config /etc/otelcol/config.yaml
Check internal metrics
curl -s localhost:8888/metrics | grep -E 'lookup|queue|send_failed|dropped'
Also available inEnriquecer telemetría con lookup processor en OpenTelemetry sin disparar cardinalidad ni backpressure

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.