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: opentelemetry-otlp-arrow-batch-streaming-standard

OpenTelemetry OTLP Arrow Columnar Stream Framing & Batch Allocation Standard

Enforces columnar Apache Arrow IPC stream boundaries and batching invariants within OpenTelemetry pipelines to eliminate serialization CPU overhead and memory fragmentation. Guarantees memory safety and optimal dictionary encoding during peak ingestion by coordinating upstream batch processors with downstream OTLP Arrow stream allocations. Prevents collector out-of-memory (OOM) crashes and garbage collection thrashing under multi-gigabit telemetry loads.

Prohibited Anti-Pattern: Naive Row-Oriented OTLP Protobuf Ingestion Under High-Throughput Burst Conditions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry OTLP Arrow Columnar Stream Framing & Batch Allocation Standard - Enforces columnar Apache Arrow IPC stream boundaries and batching invariants within OpenTelemetry pipelines to eliminate serialization CPU overhead and memory fragmentation. Guarantees memory safety and optimal dictionary encoding during peak ingestion by coordinating upstream batch processors with downstream OTLP Arrow stream allocations. Prevents collector out-of-memory (OOM) crashes and garbage collection thrashing under multi-gigabit telemetry loads.
globs: **/otel-collector*.{yaml,yml}, **/collector/**/*.{yaml,yml}, deployments/**/otel*.{yaml,yml}, k8s/**/otel*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-otlp-arrow-batch-streaming-standard"
---

# OpenTelemetry OTLP Arrow Columnar Stream Framing & Batch Allocation Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Naive Row-Oriented OTLP Protobuf Ingestion Under High-Throughput Burst Conditions

## System Constraints
You are a Principal Observability Infrastructure Architect enforcing the OpenTelemetry OTLP Arrow Native Batch Streaming Standard. You must ensure telemetry pipelines avoid row-oriented Protobuf serialization bottlenecks under peak load by enforcing Apache Arrow columnar IPC streaming, dictionary encoding limits, stream boundary constraints, and memory-safe batch processor topology.

## Strict Guidelines
- Pipelines handling high-volume telemetry (>10k spans/sec or >50k metrics/sec per node) MUST utilize the 'otlp_arrow' receiver and exporter instead of standard row-oriented OTLP gRPC.
- The 'batch' processor MUST ALWAYS precede the Arrow exporter to guarantee that Arrow RecordBatches contain sufficient rows for dictionary compression to overcome IPC framing overhead.
- Engineers MUST configure explicit memory limits on Arrow streams via 'arrow.memory_limit_mib' and specify finite 'arrow.max_stream_lifetime' to prevent stale dictionaries and unbounded heap growth.
- Engineers MUST NOT allow unbatched or single-event streaming through Arrow exporters, as tiny Arrow IPC record batches degrade throughput below standard Protobuf.
- The OpenTelemetry Collector 'memory_limiter' processor MUST ALWAYS precede any 'batch' and 'otlp_arrow' components, with 'check_interval' set to 1s and 'limit_percentage' at 80% maximum.
- Pipelines MUST specify zstd compression on the Arrow IPC stream transport to achieve 5-10x compression ratios over standard gzip-compressed Protobuf.

## Bad vs Good Implementations
### Configuring OTLP Arrow Exporter and Pipeline Topology

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Standard OTLP Protobuf gRPC incurs severe CPU deserialization penalties and memory allocations under high throughput. Batch size is too small (100) for columnar efficiency, memory limiter is missing entirely, and transport uses legacy row-wise serialization causing collector OOMs during traffic spikes.
```yaml
# ANTI-PATTERN: Standard OTLP gRPC with unbounded row serialization under peak load
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    send_batch_size: 100
    timeout: 100ms

exporters:
  otlp:
    endpoint: otel-gateway:4317
    compression: gzip

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
```

#### Production Standard (Correct)
> **Standard**: Enforces memory limiter safeguards before batching, sets optimal batch sizes (8k-16k) for Arrow dictionary encoding, configures the otlp_arrow exporter with dedicated stream concurrency (4 streams), memory caps (512 MiB), finite stream lifetime (1h), and zstd compression to optimize CPU and RAM utilization.
```yaml
# PRODUCTION STANDARD: OTLP Arrow columnar stream with memory-bounded batching
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 80
    spike_limit_percentage: 20

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

exporters:
  otlp_arrow:
    endpoint: otel-gateway:4317
    tls:
      insecure: false
    arrow:
      num_streams: 4
      max_stream_lifetime: 1h
      memory_limit_mib: 512
      prioritize: memory
    compression: zstd

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

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

OTel Collector Config Validator
Validates OpenTelemetry collector configuration pipelines, schema integrity, and component dependency order.
Recommended Agent Skills (askills.dev)

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

OpenTelemetry Collector Builder CLI
Compiles and benchmarks custom OpenTelemetry Collector distributions with OTLP Arrow native plugins enabled.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry OTLP Arrow Columnar Stream Framing & Batch Allocation Standard

OpenTelemetry OTLP Arrow Columnar Stream Framing & Batch Allocation Standard defines an industrial-grade behavioral standard for devops engineering. Enforces columnar Apache Arrow IPC stream boundaries and batching invariants within OpenTelemetry pipelines to eliminate serialization CPU overhead and memory fragmentation. Guarantees memory safety and optimal dictionary encoding during peak ingestion by coordinating upstream batch processors with downstream OTLP Arrow stream allocations. Prevents collector out-of-memory (OOM) crashes and garbage collection thrashing under multi-gigabit telemetry loads. 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: Naive Row-Oriented OTLP Protobuf Ingestion Under High-Throughput Burst Conditions 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 DriftNaive Row-Oriented OTLP Protobuf Ingestion Under High-Throughput Burst ConditionsCritical
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

Pipelines handling high-volume telemetry (>10k spans/sec or >50k metrics/sec per node) MUST utilize the 'otlp_arrow' receiver and exporter instead of standard row-oriented OTLP gRPC.

Pipelines handling high-volume telemetry (>10k spans/sec or >50k metrics/sec per node) MUST utilize the 'otlp_arrow' receiver and exporter instead of standard row-oriented OTLP gRPC.

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

The 'batch' processor MUST ALWAYS precede the Arrow exporter to guarantee that Arrow RecordBatches contain sufficient rows for dictionary compression to overcome IPC framing overhead.

The 'batch' processor MUST ALWAYS precede the Arrow exporter to guarantee that Arrow RecordBatches contain sufficient rows for dictionary compression to overcome IPC framing overhead.

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 configure explicit memory limits on Arrow streams via 'arrow.memory_limit_mib' and specify finite 'arrow.max_stream_lifetime' to prevent stale dictionaries and unbounded heap growth.

Engineers MUST configure explicit memory limits on Arrow streams via 'arrow.memory_limit_mib' and specify finite 'arrow.max_stream_lifetime' to prevent stale dictionaries and unbounded heap growth.

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 allow unbatched or single-event streaming through Arrow exporters, as tiny Arrow IPC record batches degrade throughput below standard Protobuf.

Engineers MUST NOT allow unbatched or single-event streaming through Arrow exporters, as tiny Arrow IPC record batches degrade throughput below standard Protobuf.

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

The OpenTelemetry Collector 'memory_limiter' processor MUST ALWAYS precede any 'batch' and 'otlp_arrow' components, with 'check_interval' set to 1s and 'limit_percentage' at 80% maximum.

The OpenTelemetry Collector 'memory_limiter' processor MUST ALWAYS precede any 'batch' and 'otlp_arrow' components, with 'check_interval' set to 1s and 'limit_percentage' at 80% maximum.

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

Pipelines MUST specify zstd compression on the Arrow IPC stream transport to achieve 5-10x compression ratios over standard gzip-compressed Protobuf.

Pipelines MUST specify zstd compression on the Arrow IPC stream transport to achieve 5-10x compression ratios over standard gzip-compressed Protobuf.

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 Stream Framing & Batch Allocation Standard critical for AI coding assistants?

Enforces columnar Apache Arrow IPC stream boundaries and batching invariants within OpenTelemetry pipelines to eliminate serialization CPU overhead and memory fragmentation. Guarantees memory safety and optimal dictionary encoding during peak ingestion by coordinating upstream batch processors with downstream OTLP Arrow stream allocations. Prevents collector out-of-memory (OOM) crashes and garbage collection thrashing under multi-gigabit telemetry loads. 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 (Naive Row-Oriented OTLP Protobuf Ingestion Under High-Throughput Burst Conditions) 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