OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance | 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-arrow-buffer-governance

OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance

Enforces strict memory governance, hard queue sizing, and Apache Arrow columnar compression on OpenTelemetry Collector pipelines. Prevents catastrophic OOM collector crashes during high-cardinality traffic surges through zero-copy batch streaming and calibrated memory limiter thresholds.

Prohibited Anti-Pattern: Unbounded In-Memory Batching and Row-Oriented Serialization Inducing Out-of-Memory Collector Cascades

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance - Enforces strict memory governance, hard queue sizing, and Apache Arrow columnar compression on OpenTelemetry Collector pipelines. Prevents catastrophic OOM collector crashes during high-cardinality traffic surges through zero-copy batch streaming and calibrated memory limiter thresholds.
globs: **/otel-collector*.{yaml,yml}, **/collector/*.{yaml,yml}, deploy/k8s/**/*.yaml, infra/terraform/**/*.tf
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-collector-arrow-buffer-governance"
---

# OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unbounded In-Memory Batching and Row-Oriented Serialization Inducing Out-of-Memory Collector Cascades

## System Constraints
You are a Principal Observability Infrastructure Architect enforcing OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance. Mandate absolute memory limiter placement, queue-bound backpressure, and zero-copy Apache Arrow encoding to guarantee collectors survive 10x traffic surges without exceeding cgroup limits.

## Strict Guidelines
- Engineers MUST ALWAYS place the `memory_limiter` processor as the very first processor in every telemetry pipeline.
- Engineers MUST configure `check_interval` to 1s or less and define explicit `limit_percentage` (maximum 80%) and `spike_limit_percentage` (maximum 20%) relative to container cgroup allocations.
- Pipelines processing high-cardinality telemetry MUST enable the OTLP/Arrow receiver and exporter protocol (`arrow: { enabled: true }`) to convert row-based Protobuf into zero-copy columnar batches.
- Engineers MUST NOT configure unbudgeted `sending_queue` instances; queue storage sizes MUST be bounded using `queue_size` with backpressure signaling enabled, never allowing unbounded in-memory queues.
- Services MUST configure GOMEMLIMIT environment variables set to 80-85% of the Kubernetes container memory limit alongside GOGC=80 to guarantee runtime GC preempts container eviction.
- Batch processors MUST declare `send_batch_max_size` proportional to downstream Arrow batch requirements and MUST NOT omit `timeout` constraints.

## Bad vs Good Implementations
### Unbounded Row-Oriented OTLP Collector vs. Guarded OTLP/Arrow Columnar Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omitting the memory_limiter processor leaves the collector completely defenseless against traffic surges. The unbounded sending_queue (1,000,000 items) and lack of send_batch_max_size ensure an immediate OOMKilled eviction under downstream throttling or high-cardinality spikes.
```yaml
# Anti-Pattern: No memory limiter, unbounded queues, standard row-oriented OTLP
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    # Missing send_batch_max_size and memory bounds
    send_batch_size: 10000
    timeout: 10s

exporters:
  otlp:
    endpoint: downstream.telemetry.svc:4317
    sending_queue:
      enabled: true
      num_consumers: 10
      queue_size: 1000000 # Dangerous: massive memory footprint during backpressure

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [batch] # Memory limiter missing entirely!
      exporters: [otlp]
```

#### Production Standard (Correct)
> **Standard**: Memory limiter is mandated as the first processor to reject payloads before allocation. OTLP/Arrow enables 70-80% payload memory compression via columnar transport, and queue sizes are strictly budgeted to fit safely inside the container cgroup boundary.
```yaml
# Production Invariant: Arrow Columnar Streaming with Strict Budget Enforcement
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        arrow:
          enabled: true # Ingest directly via Apache Arrow columnar format

processors:
  memory_limiter:
    check_interval: 500ms
    limit_percentage: 75
    spike_limit_percentage: 15

  batch:
    send_batch_size: 8192
    send_batch_max_size: 16384
    timeout: 2s

exporters:
  otlp:
    endpoint: downstream.telemetry.svc:4317
    arrow:
      enabled: true
      num_streams: 4
    sending_queue:
      enabled: true
      num_consumers: 8
      queue_size: 5000 # Strictly bounded queue budget

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [memory_limiter, batch] # memory_limiter MUST be first
      exporters: [otlp]
```

Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Inspector

MCP server to query active container cgroup memory limits, OOMKilled events, and OpenTelemetry collector pod metrics.

Recommended Agent Skills (askills.dev)

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

OpenTelemetry Collector Config Validator

CLI utility to lint collector pipeline topologies and validate memory limiter positioning and buffer configurations.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance

OpenTelemetry Collector OTLP/Arrow Columnar Ingestion and Buffer Budget Governance defines an industrial-grade behavioral standard for devops engineering. Enforces strict memory governance, hard queue sizing, and Apache Arrow columnar compression on OpenTelemetry Collector pipelines. Prevents catastrophic OOM collector crashes during high-cardinality traffic surges through zero-copy batch streaming and calibrated memory limiter thresholds. 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: Unbounded In-Memory Batching and Row-Oriented Serialization Inducing Out-of-Memory Collector Cascades 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	Unbounded In-Memory Batching and Row-Oriented Serialization Inducing Out-of-Memory Collector Cascades	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 place the `memory_limiter` processor as the very first processor in every telemetry pipeline.

Engineers MUST ALWAYS place the `memory_limiter` processor as the very first processor in every telemetry pipeline.

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 configure `check_interval` to 1s or less and define explicit `limit_percentage` (maximum 80%) and `spike_limit_percentage` (maximum 20%) relative to container cgroup allocations.

Engineers MUST configure `check_interval` to 1s or less and define explicit `limit_percentage` (maximum 80%) and `spike_limit_percentage` (maximum 20%) relative to container cgroup allocations.

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

Pipelines processing high-cardinality telemetry MUST enable the OTLP/Arrow receiver and exporter protocol (`arrow

Pipelines processing high-cardinality telemetry MUST enable the OTLP/Arrow receiver and exporter protocol (`arrow: { enabled: true }`) to convert row-based Protobuf into zero-copy columnar batches.

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

Engineers MUST NOT configure unbudgeted `sending_queue` instances

Engineers MUST NOT configure unbudgeted `sending_queue` instances; queue storage sizes MUST be bounded using `queue_size` with backpressure signaling enabled, never allowing unbounded in-memory queues.

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

Services MUST configure GOMEMLIMIT environment variables set to 80-85% of the Kubernetes container memory limit alongside GOGC=80 to guarantee runtime GC preempts container eviction.

Services MUST configure GOMEMLIMIT environment variables set to 80-85% of the Kubernetes container memory limit alongside GOGC=80 to guarantee runtime GC preempts container eviction.

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

Batch processors MUST declare `send_batch_max_size` proportional to downstream Arrow batch requirements and MUST NOT omit `timeout` constraints.

Batch processors MUST declare `send_batch_max_size` proportional to downstream Arrow batch requirements and MUST NOT omit `timeout` constraints.

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 OTLP/Arrow Columnar Ingestion and Buffer Budget Governance critical for AI coding assistants?

Enforces strict memory governance, hard queue sizing, and Apache Arrow columnar compression on OpenTelemetry Collector pipelines. Prevents catastrophic OOM collector crashes during high-cardinality traffic surges through zero-copy batch streaming and calibrated memory limiter thresholds. 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 (Unbounded In-Memory Batching and Row-Oriented Serialization Inducing Out-of-Memory Collector Cascades) 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