OTEL-001
memory_limiter is required to prevent the Collector from being OOM-killed.
OTEL-002
Declaring memory_limiter is not enough — each pipeline must reference it.
OTEL-003
The batch processor is required for efficient, cost-effective export.
OTEL-004
Exporter credentials must come from environment variables, not literal strings.
OTEL-005
Receiver credentials must come from environment variables, not literal strings.
OTEL-006
A Collector config with no pipelines does nothing.
OTEL-007
A pipeline with no receivers or no exporters transmits nothing.
OTEL-010
Binding to 0.0.0.0 exposes receivers on every interface.
OTEL-011
Kubernetes probes and load balancers need a health endpoint.
OTEL-012
Defining an extension does not enable it — it also has to appear in service.extensions.
OTEL-013
Putting batch last means every other processor sees un-batched data and batches reflect the final shape.
OTEL-014
The memory limiter must be first so it can reject work before anything allocates.
OTEL-015
The debug exporter is a development tool — it should not ship to production.
OTEL-016
Debug-level logs in production are expensive and noisy.
OTEL-017
Network exporters need retry and/or queueing to tolerate brief outages.
OTEL-018
OTLP traffic to a remote backend should be encrypted.
OTEL-020
A receiver not referenced in any pipeline silently does nothing.
OTEL-021
An exporter not referenced in any pipeline sends nothing.
OTEL-022
A processor not referenced in any pipeline does nothing.