AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
devopscritical PriorityID: otel-arrow-compression-memory-bounds

OpenTelemetry OTel-Arrow Stream Compression Memory Bound Invariant

Prevents telemetry pipeline buffer exhaustion under high-cardinality spikes by pinning Apache Arrow columnar record batch sizes and stream compression chunk allocation limits. Unbounded batch builders or missing memory-limiter processor envelopes in OTel-Arrow exporters induce catastrophic OOM panics when dynamic schema widening occurs during ingest bursts.

Prohibited Anti-Pattern: Unbounded Arrow Record Batching and Ungated Stream Compression under Dynamic Schema Bursts

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry OTel-Arrow Stream Compression Memory Bound Invariant - Prevents telemetry pipeline buffer exhaustion under high-cardinality spikes by pinning Apache Arrow columnar record batch sizes and stream compression chunk allocation limits. Unbounded batch builders or missing memory-limiter processor envelopes in OTel-Arrow exporters induce catastrophic OOM panics when dynamic schema widening occurs during ingest bursts.
globs: **/otel-collector-config*.{yaml,yml}, **/collector/*.{yaml,yml}, src/**/telemetry/*.{ts,go,rs,py}, deploy/**/collector*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-arrow-compression-memory-bounds"
---

# OpenTelemetry OTel-Arrow Stream Compression Memory Bound Invariant

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unbounded Arrow Record Batching and Ungated Stream Compression under Dynamic Schema Bursts

## System Constraints
You are a Principal DevOps and Observability Infrastructure Architect enforcing strict memory bounds on OpenTelemetry OTel-Arrow pipelines. You must ensure all OTel-Arrow exporters and receivers explicitly declare max_stream_bytes, batch_size limits, dictionary encoding thresholds, and strict memory limiter processors to prevent heap exhaustion during high-cardinality metadata bursts.

## Strict Guidelines
- Engineers MUST ALWAYS couple the `otelarrow` exporter and receiver with an upstream `memory_limiter` processor configured with explicit `check_interval`, `limit_percentage`, and `spike_limit_percentage`.
- Engineers MUST explicitly set `arrow.memory_limit_mib` and bound `arrow.max_stream_bytes` (or payload batch size) on Arrow stream encoders to prevent dynamic dictionary allocation runaways.
- Engineers MUST NOT leave `arrow.num_streams` or chunk buffers unpinned; stream concurrency MUST be sized proportionally to allocated container cgroup memory limits.
- Pipelines MUST enforce backpressure propagation by setting `arrow.wait_for_storage` or queue bounds with `retry_on_failure` and `sending_queue.storage` backstop.
- Components NEVER construct Arrow RecordBatches without pre-allocated capacity estimations or hard schema width ceilings when handling high-cardinality baggage or trace attributes.

## Bad vs Good Implementations
### OTel-Arrow Collector Exporter Configuration Bounds

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Default otelarrow configuration allows unbounded columnar record accumulation and ignores dynamic schema expansion. Under high-cardinality attribute bursts, dictionary tables explode beyond container limits without triggering pipeline backpressure.
```yaml
exporters:
  otelarrow:
    endpoint: "arrow-ingest.internal:4317"
    tls:
      insecure: true
    # ANTI-PATTERN: Default unbounded stream buffers and implicit dynamic batching.
    # High cardinality bursts cause Arrow columnar builder to allocate gigabytes
    # of untracked memory for dictionary encoding and wide schemas, triggering OOMKills.
service:
  pipelines:
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otelarrow]
```

#### Production Standard (Correct)
> **Standard**: Pins Arrow chunk size to 4MiB, bounds concurrent Arrow streams to 4, sets an explicit 512MiB Arrow builder memory limit, and inserts a strict memory_limiter processor ahead of batching to guarantee stable heap usage and enforce backpressure.
```yaml
processors:
  memory_limiter:
    check_interval: 250ms
    limit_percentage: 75
    spike_limit_percentage: 20
  batch:
    send_batch_size: 8192
    timeout: 500ms

exporters:
  otelarrow:
    endpoint: "arrow-ingest.internal:4317"
    tls:
      insecure: true
    arrow:
      memory_limit_mib: 512
      max_stream_bytes: 4194304 # 4MiB per chunk invariant
      num_streams: 4
      payload_compression: "zstd"
    sending_queue:
      enabled: true
      num_consumers: 8
      queue_size: 1024

service:
  pipelines:
    logs:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otelarrow]
```
Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource & Pod Inspector
Inspect collector container memory limits, cgroup throttling, and OOMKilled events in production.
Recommended Agent Skills (askills.dev)

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

OpenTelemetry Collector Config Validator
Validates OTel Collector YAML configurations against internal schema constraints and memory bounds.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry OTel-Arrow Stream Compression Memory Bound Invariant

OpenTelemetry OTel-Arrow Stream Compression Memory Bound Invariant defines an industrial-grade behavioral standard for devops engineering. Prevents telemetry pipeline buffer exhaustion under high-cardinality spikes by pinning Apache Arrow columnar record batch sizes and stream compression chunk allocation limits. Unbounded batch builders or missing memory-limiter processor envelopes in OTel-Arrow exporters induce catastrophic OOM panics when dynamic schema widening occurs during ingest bursts. 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 Arrow Record Batching and Ungated Stream Compression under Dynamic Schema Bursts 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUnbounded Arrow Record Batching and Ungated Stream Compression under Dynamic Schema BurstsCritical
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 InconsistencyAI 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 couple the `otelarrow` exporter and receiver with an upstream `memory_limiter` processor configured with explicit `check_interval`, `limit_percentage`, and `spike_limit_percentage`.

Engineers MUST ALWAYS couple the `otelarrow` exporter and receiver with an upstream `memory_limiter` processor configured with explicit `check_interval`, `limit_percentage`, and `spike_limit_percentage`.

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 explicitly set `arrow.memory_limit_mib` and bound `arrow.max_stream_bytes` (or payload batch size) on Arrow stream encoders to prevent dynamic dictionary allocation runaways.

Engineers MUST explicitly set `arrow.memory_limit_mib` and bound `arrow.max_stream_bytes` (or payload batch size) on Arrow stream encoders to prevent dynamic dictionary allocation runaways.

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 NOT leave `arrow.num_streams` or chunk buffers unpinned

Engineers MUST NOT leave `arrow.num_streams` or chunk buffers unpinned; stream concurrency MUST be sized proportionally to allocated container cgroup memory 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.
4

Pipelines MUST enforce backpressure propagation by setting `arrow.wait_for_storage` or queue bounds with `retry_on_failure` and `sending_queue.storage` backstop.

Pipelines MUST enforce backpressure propagation by setting `arrow.wait_for_storage` or queue bounds with `retry_on_failure` and `sending_queue.storage` backstop.

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 construct Arrow RecordBatches without pre-allocated capacity estimations or hard schema width ceilings when handling high-cardinality baggage or trace attributes.

Components NEVER construct Arrow RecordBatches without pre-allocated capacity estimations or hard schema width ceilings when handling high-cardinality baggage or trace attributes.

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 OTel-Arrow Stream Compression Memory Bound Invariant critical for AI coding assistants?

Prevents telemetry pipeline buffer exhaustion under high-cardinality spikes by pinning Apache Arrow columnar record batch sizes and stream compression chunk allocation limits. Unbounded batch builders or missing memory-limiter processor envelopes in OTel-Arrow exporters induce catastrophic OOM panics when dynamic schema widening occurs during ingest bursts. 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 Arrow Record Batching and Ungated Stream Compression under Dynamic Schema Bursts) 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 →
devops
86

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.

devops
118

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.

devops
40

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