Collect host and application telemetry with OpenTelemetry Collector

Likely causeThe configuration was written for a component that is not included in the selected core or contrib distribution, or the component name changed between releases.

ResolutionUse a distribution containing only reviewed components or build a pinned custom distribution. Do not download arbitrary third-party binaries to satisfy the configuration.

Likely causeThe agent is down, the receiver binds another interface, TLS trust fails, a firewall blocks the endpoint or memory protection is refusing load.

ResolutionRepair health, bind and trust configuration; scale or shed noncritical telemetry when memory pressure is intentional. Never disable TLS verification on a network receiver.

Likely causeMemory limiter is absent, placed after buffering processors, sized above the container limit, or persistent/export queues ingest faster than the backend can drain.

ResolutionLower limiter thresholds below the runtime limit, bound queues and batches, restore export throughput and load-test a representative burst.

Likely causeThe backend outage exceeds queue capacity, storage shares the root filesystem, retry never gives up or downstream capacity is lower than sustained input.

ResolutionRestore the backend, enforce a finite queue and retry horizon based on RPO, isolate storage with a quota, and document which telemetry is dropped first.

Likely causePersistent queues provide at-least-once delivery and replay items whose acknowledgement was not durably observed.

ResolutionMake the backend and queries tolerant of bounded duplicates, preserve stable trace/span IDs, and do not promise exactly-once delivery.

Likely causeThe signal lacks a service pipeline, receiver/exporter is omitted from that pipeline, or a filter/transform expression drops it.

ResolutionAdd the missing pipeline or correct processor logic, validate, then canary all three signals before production reload.

Likely causeClient certificate, CA, token or workload identity is expired, mapped to the wrong tenant, or absent from the exporter.

ResolutionRestore the approved short-lived identity, rotate compromised material and test an unauthorized identity is denied. Do not use a shared administrator token.

Likely causeThe transform targets the wrong signal path, a new attribute key or encoding bypasses it, or a debug exporter emits before the processor.

ResolutionStop the affected pipeline, revoke leaked credentials if applicable, correct source instrumentation and pre-export transform/filter logic, then retest synthetic fixtures.

Likely causeOTTL syntax, context or field type does not match the pinned component version, or error_mode is propagating unexpected failures.

ResolutionCorrect the OTTL statement and choose an explicit reviewed error_mode; never silently ignore redaction failures in production.

Likely causeAgents and gateways both overwrite resource attributes, hostname discovery varies, or ephemeral IDs are used as canonical host identity.

ResolutionAssign stable host/service/environment identity once, preserve SDK attributes intentionally, and delete only explicitly forbidden keys.

Likely causeTimeout or batch size is too high for a low-volume tenant, queue congestion adds delay, or exporter connections are saturated.

ResolutionTune batch timeout/size from measured volume, shard gateways by stable tenant key where required, and add backend/export capacity.

Likely causeComplex regex/OTTL runs for every record, debug verbosity serializes full payloads, or filelog parses large multiline records.

ResolutionMove filtering earlier, simplify bounded expressions, cap record size and disable detailed debug export outside synthetic tests.

Likely causeFile storage is not persistent, file fingerprints change, include/exclude patterns overlap or the rotation strategy is incompatible.

ResolutionPersist receiver state, correct include/exclude patterns and validate the application's actual rotation semantics before rollout.

Likely causeProcess liveness only proves the Collector is running, not that queues drain or exporters succeed.

ResolutionKeep liveness simple but add readiness/operational alerts based on exporter and queue health plus signal canaries.

Likely causeLoad balancing, sticky connections, gRPC connection longevity or tenant distribution concentrates traffic.

ResolutionUse supported client/load-balancing behavior, additional connections or stable sharding while preserving trace/metric processing requirements.

Likely causeRelated telemetry is split across gateways without consistent routing, or stateful processors restart without an accepted loss model.

ResolutionRoute related data consistently, use supported load-balancing connectors, or remove the stateful processor until correctness is proved.

Likely causeResource attributes were promoted into self-telemetry, endpoint URLs contain credentials, or debug logs include headers.

ResolutionRemove credentials from URLs, restrict internal telemetry endpoints and sanitize labels/logs before returning service.

Likely causeCollector did not reload files, chain order/SAN is wrong, CA bundle was replaced non-atomically or clock skew invalidates the new certificate.

ResolutionRestore the prior valid certificate atomically, validate the new bundle offline and use a staged restart/reload procedure.

Likely causeSDKs omit `service.name`, the resource processor inserts a generic value, or gateway normalization overwrites a correct value.

ResolutionRequire explicit service identity at instrumentation, add a bounded fallback only where absent, and never overwrite a trusted value accidentally.

Likely causeThe queue is local durability, not a backup; the host and queue filesystem share the same failure domain.

ResolutionCorrect the architecture statement: persistent queues bridge bounded outages but do not replace backend durability. Use a durable backend and accept/document local loss on host failure.