OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant | AgentRules.org

Rules Stacks Clients Auditor Pruner Self-Heal RFCs Benchmark CLI CI/CD Authors Submit

This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →

devopscritical PriorityID: otel-collector-persistent-queue-disk-buffer-invariant

OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant

Enforces file-storage-backed persistent queueing within OpenTelemetry Collector exporters alongside upstream memory_limiter guards. Guarantees zero telemetry loss and prevents out-of-memory (OOM) fatal crashes during extended downstream network partitions by spilling bounded batches to persistent volumes.

Prohibited Anti-Pattern: Volatile In-Memory Exporter Queuing Without Disk Spooling or Memory Throttling

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant - Enforces file-storage-backed persistent queueing within OpenTelemetry Collector exporters alongside upstream memory_limiter guards. Guarantees zero telemetry loss and prevents out-of-memory (OOM) fatal crashes during extended downstream network partitions by spilling bounded batches to persistent volumes.
globs: **/otel-collector*.{yaml,yml}, **/collector*.{yaml,yml}, **/otel*.{yaml,yml}, k8s/**/otel*.{yaml,yml}, deployments/**/otel*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-collector-persistent-queue-disk-buffer-invariant"
---

# OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Volatile In-Memory Exporter Queuing Without Disk Spooling or Memory Throttling

## System Constraints
You are a Principal Observability Infrastructure Architect enforcing fault-tolerant OpenTelemetry Collector configurations. You mandate that any OpenTelemetry Collector deployment processing production telemetry must implement the file_storage persistent queue invariant on all network-bound exporters to prevent OOM termination and data loss during downstream outages.

## Strict Guidelines
- Engineers MUST ALWAYS configure the 'file_storage' extension whenever network-egress exporters (e.g., otlp, otlphttp) are defined.
- Engineers MUST ALWAYS link the file_storage extension to the exporter's 'sending_queue.storage' attribute rather than relying on in-memory buffers alone.
- Engineers MUST ALWAYS configure the 'memory_limiter' processor as the first processor in every telemetry pipeline (logs, metrics, traces).
- Services MUST mount dedicated Persistent Volumes (PVCs) for the file_storage directory to prevent root filesystem exhaustion.
- Components NEVER permit 'sending_queue.enabled: true' without specifying storage or explicit queue memory bounds coupled with an active memory limiter.
- Engineers MUST explicitly set 'check_interval', 'limit_percentage', and 'spike_limit_percentage' in the memory_limiter processor based on container cgroup limits.

## Bad vs Good Implementations
### Resilient Collector Pipeline Configuration with File-Storage Queue and Memory Limiter

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The collector uses an unbacked in-memory queue with 50,000 batches. During a downstream outage or network partition, heap allocations will rapidly exceed container memory limits, inducing a Kubernetes OOMKill event that drops all queued in-flight spans.
```yaml
extensions:
  health_check: {}

processors:
  batch:
    send_batch_size: 8192
    timeout: 1s

exporters:
  otlp:
    endpoint: "backend-telemetry.prod:4317"
    sending_queue:
      enabled: true
      queue_size: 50000 # Flaw: in-memory queue will exhaust memory under downstream partition

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch] # Flaw: missing memory_limiter as first processor
      exporters: [otlp]
```

#### Production Standard (Correct)
> **Standard**: The pipeline prepends memory_limiter to shed load safely prior to heap starvation, and delegates queue buffering to file_storage/queue mapped to a bounded persistent volume, guaranteeing persistence across partitions and restarts.
```yaml
extensions:
  health_check: {}
  file_storage/queue:
    directory: /var/lib/otelcol/queue
    timeout: 10s
    compaction:
      on_rebound: true
    max_file_size_mib: 100

processors:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 75
    spike_limit_percentage: 20
  batch:
    send_batch_size: 8192
    timeout: 1s

exporters:
  otlp:
    endpoint: "backend-telemetry.prod:4317"
    sending_queue:
      enabled: true
      storage: file_storage/queue
      queue_size: 5000

service:
  extensions: [health_check, file_storage/queue]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlp]
```

Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Kubernetes Cluster Inspector

Inspects and validates PersistentVolumeClaim mounts and container memory limits for OTel collector pods.

Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

OpenTelemetry Collector Config Validator

Validates schema correctness and validates extension linkages in otel-collector YAML manifests.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant

OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant defines an industrial-grade behavioral standard for devops engineering. Enforces file-storage-backed persistent queueing within OpenTelemetry Collector exporters alongside upstream memory_limiter guards. Guarantees zero telemetry loss and prevents out-of-memory (OOM) fatal crashes during extended downstream network partitions by spilling bounded batches to persistent volumes. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Volatile In-Memory Exporter Queuing Without Disk Spooling or Memory Throttling Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Volatile In-Memory Exporter Queuing Without Disk Spooling or Memory Throttling	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS configure the 'file_storage' extension whenever network-egress exporters (e.g., otlp, otlphttp) are defined.

Engineers MUST ALWAYS configure the 'file_storage' extension whenever network-egress exporters (e.g., otlp, otlphttp) are defined.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

2

Engineers MUST ALWAYS link the file_storage extension to the exporter's 'sending_queue.storage' attribute rather than relying on in-memory buffers alone.

Engineers MUST ALWAYS link the file_storage extension to the exporter's 'sending_queue.storage' attribute rather than relying on in-memory buffers alone.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

3

Engineers MUST ALWAYS configure the 'memory_limiter' processor as the first processor in every telemetry pipeline (logs, metrics, traces).

Engineers MUST ALWAYS configure the 'memory_limiter' processor as the first processor in every telemetry pipeline (logs, metrics, traces).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

4

Services MUST mount dedicated Persistent Volumes (PVCs) for the file_storage directory to prevent root filesystem exhaustion.

Services MUST mount dedicated Persistent Volumes (PVCs) for the file_storage directory to prevent root filesystem exhaustion.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

5

Components NEVER permit 'sending_queue.enabled

Components NEVER permit 'sending_queue.enabled: true' without specifying storage or explicit queue memory bounds coupled with an active memory limiter.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

6

Engineers MUST explicitly set 'check_interval', 'limit_percentage', and 'spike_limit_percentage' in the memory_limiter processor based on container cgroup limits.

Engineers MUST explicitly set 'check_interval', 'limit_percentage', and 'spike_limit_percentage' in the memory_limiter processor based on container cgroup limits.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is OpenTelemetry Collector Persistent Queue Disk-Buffer Invariant critical for AI coding assistants?

Enforces file-storage-backed persistent queueing within OpenTelemetry Collector exporters alongside upstream memory_limiter guards. Guarantees zero telemetry loss and prevents out-of-memory (OOM) fatal crashes during extended downstream network partitions by spilling bounded batches to persistent volumes. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Volatile In-Memory Exporter Queuing Without Disk Spooling or Memory Throttling) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related DEVOPS Rules

View all rules →

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

OpenTelemetry