OpenTelemetry OTLP Arrow Columnar Ingestion Pipeline Guardrail | 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: opentelemetry-otlp-arrow-columnar-ingestion-pipeline

OpenTelemetry OTLP Arrow Columnar Ingestion Pipeline Guardrail

Enforces deterministic memory bounds, stream multiplexing parameters, and memory limiter pipeline order for OpenTelemetry OTLP/Arrow ingestion. Prevents out-of-memory (OOM) crashes and CPU starvation by guaranteeing strict columnar batch ceilings, Arrow record dictionary reuse, and resilient protobuf fallbacks across collector topologies.

Prohibited Anti-Pattern: Unbounded Arrow Stream Buffering and Missing Memory-Limiter Interceptors Triggering Ingestion OOMs

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry OTLP Arrow Columnar Ingestion Pipeline Guardrail - Enforces deterministic memory bounds, stream multiplexing parameters, and memory limiter pipeline order for OpenTelemetry OTLP/Arrow ingestion. Prevents out-of-memory (OOM) crashes and CPU starvation by guaranteeing strict columnar batch ceilings, Arrow record dictionary reuse, and resilient protobuf fallbacks across collector topologies.
globs: **/otel-collector*.yaml, **/otel-collector*.yml, **/collector/*.yaml, **/k8s/**/collector-*.yaml, **/helm/**/values*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-otlp-arrow-columnar-ingestion-pipeline"
---

# OpenTelemetry OTLP Arrow Columnar Ingestion Pipeline Guardrail

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unbounded Arrow Stream Buffering and Missing Memory-Limiter Interceptors Triggering Ingestion OOMs

## System Constraints
You are a Principal Observability Infrastructure Architect enforcing OpenTelemetry OTLP Arrow Columnar Serialization Ingestion Pipelines. Mandate strict memory limiter precedence, Arrow-specific buffer and stream quotas, dictionary encoding thresholds, and explicit payload compression invariants across all OpenTelemetry collector manifests.

## Strict Guidelines
- Collectors MUST configure the `memory_limiter` processor as the FIRST processor in all pipelines before batching or Arrow columnar decoding.
- Receivers using `otlparrow` MUST declare explicit `arrow.memory_limit_mib`, `arrow.max_stream_lifetime`, and `max_concurrent_streams` to constrain off-heap record allocations.
- Exporters using `otlparrow` MUST specify deterministic batch parameters (`timeout`, `send_batch_size`, and `send_batch_max_size`) paired with dictionary deduplication to maximize Arrow columnar compression ratios.
- Engineers MUST NOT configure unbounded in-memory queues or omit `zstd` payload compression when routing Arrow streams across network failure domains.
- Pipelines MUST maintain standard OTLP gRPC/Protobuf negotiation fallbacks to avoid telemetry blackholing during upstream Arrow transport degradation.

## Bad vs Good Implementations
### OpenTelemetry Collector OTLP/Arrow Pipeline Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits the memory_limiter processor as the first pipeline interceptor, configures no stream concurrency or memory boundaries on the otlparrow receiver, and sets oversized batch sizes without memory limits, resulting in catastrophic OOM kills under bursty telemetry loads.
```yaml
# Anti-Pattern: Missing memory limiter, unbounded Arrow streams, unconstrained queueing
receivers:
  otlparrow:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    send_batch_size: 50000
    timeout: 10s

exporters:
  otlparrow:
    endpoint: downstream-collector:4317
    tls:
      insecure: true

service:
  pipelines:
    metrics:
      receivers: [otlparrow]
      processors: [batch]
      exporters: [otlparrow]
```

#### Production Standard (Correct)
> **Standard**: Guarantees cluster stability by declaring memory_limiter as the first processor, strictly bounding Arrow receiver memory and stream lifetimes, enforcing realistic batch bounds for dictionary construction, and isolating transport failures with bounded queues.
```yaml
# Production Standard: Enforced memory limits, explicit Arrow stream ceilings, and bounded batching
receivers:
  otlparrow:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        max_concurrent_streams: 1024
    arrow:
      memory_limit_mib: 512
      max_stream_lifetime: 2h

processors:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 75
    spike_limit_percentage: 20
  batch:
    timeout: 200ms
    send_batch_size: 8192
    send_batch_max_size: 16384

exporters:
  otlparrow:
    endpoint: downstream-collector:4317
    arrow:
      num_streams: 4
      zstd:
        level: 3
    sending_queue:
      enabled: true
      num_consumers: 8
      queue_size: 1000
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s

service:
  pipelines:
    metrics:
      receivers: [otlparrow]
      processors: [memory_limiter, batch]
      exporters: [otlparrow]
```

Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Cluster Inspector

Inspects running OpenTelemetry Collector Pod metrics, OOMKilled statuses, and active ConfigMaps.

Recommended Agent Skills (askills.dev)

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

OTel Collector Config Validator

CLI utility to validate OpenTelemetry Collector configuration syntax, component availability, and pipeline wiring.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry OTLP Arrow Columnar Ingestion Pipeline Guardrail

OpenTelemetry OTLP Arrow Columnar Ingestion Pipeline Guardrail defines an industrial-grade behavioral standard for devops engineering. Enforces deterministic memory bounds, stream multiplexing parameters, and memory limiter pipeline order for OpenTelemetry OTLP/Arrow ingestion. Prevents out-of-memory (OOM) crashes and CPU starvation by guaranteeing strict columnar batch ceilings, Arrow record dictionary reuse, and resilient protobuf fallbacks across collector topologies. 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 Stream Buffering and Missing Memory-Limiter Interceptors Triggering Ingestion OOMs 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 Arrow Stream Buffering and Missing Memory-Limiter Interceptors Triggering Ingestion OOMs	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

Collectors MUST configure the `memory_limiter` processor as the FIRST processor in all pipelines before batching or Arrow columnar decoding.

Collectors MUST configure the `memory_limiter` processor as the FIRST processor in all pipelines before batching or Arrow columnar decoding.

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

Receivers using `otlparrow` MUST declare explicit `arrow.memory_limit_mib`, `arrow.max_stream_lifetime`, and `max_concurrent_streams` to constrain off-heap record allocations.

Receivers using `otlparrow` MUST declare explicit `arrow.memory_limit_mib`, `arrow.max_stream_lifetime`, and `max_concurrent_streams` to constrain off-heap record 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

Exporters using `otlparrow` MUST specify deterministic batch parameters (`timeout`, `send_batch_size`, and `send_batch_max_size`) paired with dictionary deduplication to maximize Arrow columnar compression ratios.

Exporters using `otlparrow` MUST specify deterministic batch parameters (`timeout`, `send_batch_size`, and `send_batch_max_size`) paired with dictionary deduplication to maximize Arrow columnar compression ratios.

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 unbounded in-memory queues or omit `zstd` payload compression when routing Arrow streams across network failure domains.

Engineers MUST NOT configure unbounded in-memory queues or omit `zstd` payload compression when routing Arrow streams across network failure domains.

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

Pipelines MUST maintain standard OTLP gRPC/Protobuf negotiation fallbacks to avoid telemetry blackholing during upstream Arrow transport degradation.

Pipelines MUST maintain standard OTLP gRPC/Protobuf negotiation fallbacks to avoid telemetry blackholing during upstream Arrow transport degradation.

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 OTLP Arrow Columnar Ingestion Pipeline Guardrail critical for AI coding assistants?

Enforces deterministic memory bounds, stream multiplexing parameters, and memory limiter pipeline order for OpenTelemetry OTLP/Arrow ingestion. Prevents out-of-memory (OOM) crashes and CPU starvation by guaranteeing strict columnar batch ceilings, Arrow record dictionary reuse, and resilient protobuf fallbacks across collector topologies. 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 Stream Buffering and Missing Memory-Limiter Interceptors Triggering Ingestion OOMs) 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