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-collector-arrow-columnar-batching-invariant

OpenTelemetry Collector Apache Arrow Columnar Batching & Wire Protocol Invariant

Mandates the usage of Apache Arrow columnar encoding and batching protocols across high-throughput OpenTelemetry Collector pipelines. Standard row-oriented OTLP protobuf serialization introduces massive CPU serialization penalties and elevated egress bandwidth costs when handling high-cardinality metrics, traces, and logs. Columnar memory representations enable zero-copy processing, vectorized compression, and drastic memory footprint reduction across collector tiers.

Prohibited Anti-Pattern: Row-Oriented OTLP Protobuf Overhead Across High-Volume Collector Topologies

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: "OpenTelemetry Collector Apache Arrow Columnar Batching & Wire Protocol Invariant - Mandates the usage of Apache Arrow columnar encoding and batching protocols across high-throughput OpenTelemetry Collector pipelines. Standard row-oriented OTLP protobuf serialization introduces massive CPU serialization penalties and elevated egress bandwidth costs when handling high-cardinality metrics, traces, and logs. Columnar memory representations enable zero-copy processing, vectorized compression, and drastic memory footprint reduction across collector tiers."
globs: "**/otelcol*.yaml, **/otel-collector*.yaml, **/otel-collector*.yml, deployments/**/*.yaml, k8s/**/*.yaml"
alwaysApply: true
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-collector-arrow-columnar-batching-invariant"
---

# OpenTelemetry Collector Apache Arrow Columnar Batching & Wire Protocol Invariant

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Row-Oriented OTLP Protobuf Overhead Across High-Volume Collector Topologies

## System Constraints
You are a Principal Infrastructure & Observability Architect enforcing the Apache Arrow Columnar Batching Invariant for OpenTelemetry Collector topologies. Mandate zero-copy columnar batching, memory-safe Arrow stream allocations, and specialized Arrow gRPC exporters for all high-cardinality telemetry routing.

## Strict Guidelines
- Engineers MUST ALWAYS configure the `oteparow` receiver and exporter when shipping telemetry between gateway collectors and centralized processing tiers.
- Engineers MUST NOT use uncompressed row-oriented OTLP/gRPC or OTLP/HTTP protocols for multi-agent inter-collector transit exceeding 5,000 signals per second.
- Code SHOULD configure dictionary encoding explicitly in the Arrow exporter to deduplicate repeated high-cardinality metric names, resource attributes, and span attributes.
- Services MUST configure strict bounded columnar buffer pools with `memory_limit_mib` alongside `max_stream_lifetime` to prevent memory fragmentation and OOM killed collector pods.
- Components NEVER emit unbatched Arrow record batches; pipelines must enforce a dedicated `batch` processor with timeout and signal size minimums upstream of the Arrow exporter.

## Bad vs Good Implementations
### Configuring OTel Collector with Apache Arrow Columnar Exporter and Receiver

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Row-based OTLP protobuf serialization forces deep recursive tree traversal of attributes per span/log/metric, creating intense CPU serialization pressure and failing to compress high-cardinality string keys effectively across inter-collector networks.
```yaml
# INVARIANT VIOLATION: Using standard row-oriented OTLP/gRPC
# Causes severe CPU saturation due to protobuf serialization
# and inflated network egress payloads under high cardinality.
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    send_batch_size: 1000
    timeout: 10s

exporters:
  otlp/gateway:
    endpoint: gateway.observability.internal:4317
    tls:
      insecure: true

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

#### Production Standard (Correct)
> **Standard**: The Arrow extension converts spans and attributes into contiguous columnar memory chunks, amortizing schema overhead, enabling hardware-level vectorized compression via Zstandard, and eliminating unneeded deserialization allocations.
```yaml
# COMPLIANT: Arrow-accelerated OTLP with columnar batching and stream bounds
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        arrow:
          memory_limit_mib: 512

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

exporters:
  otlp/arrow_gateway:
    endpoint: gateway.observability.internal:4317
    tls:
      insecure: true
    arrow:
      num_streams: 4
      max_stream_lifetime: 2h
      zstd:
        level: 3

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

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

OTel Collector Config Validator MCP
Validates OpenTelemetry collector configurations against semantic conventions, component schemas, and memory limits.
Recommended Agent Skills (askills.dev)

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

OpenTelemetry Collector Builder (OCB)
CLI utility to generate custom collector binaries embedding the official Arrow receiver and exporter components.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Collector Apache Arrow Columnar Batching & Wire Protocol Invariant

OpenTelemetry Collector Apache Arrow Columnar Batching & Wire Protocol Invariant defines an industrial-grade behavioral standard for devops engineering. Mandates the usage of Apache Arrow columnar encoding and batching protocols across high-throughput OpenTelemetry Collector pipelines. Standard row-oriented OTLP protobuf serialization introduces massive CPU serialization penalties and elevated egress bandwidth costs when handling high-cardinality metrics, traces, and logs. Columnar memory representations enable zero-copy processing, vectorized compression, and drastic memory footprint reduction across collector tiers. 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: Row-Oriented OTLP Protobuf Overhead Across High-Volume Collector Topologies 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 DriftRow-Oriented OTLP Protobuf Overhead Across High-Volume Collector TopologiesCritical
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 configure the `oteparow` receiver and exporter when shipping telemetry between gateway collectors and centralized processing tiers.

Engineers MUST ALWAYS configure the `oteparow` receiver and exporter when shipping telemetry between gateway collectors and centralized processing tiers.

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 NOT use uncompressed row-oriented OTLP/gRPC or OTLP/HTTP protocols for multi-agent inter-collector transit exceeding 5,000 signals per second.

Engineers MUST NOT use uncompressed row-oriented OTLP/gRPC or OTLP/HTTP protocols for multi-agent inter-collector transit exceeding 5,000 signals per second.

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

Code SHOULD configure dictionary encoding explicitly in the Arrow exporter to deduplicate repeated high-cardinality metric names, resource attributes, and span attributes.

Code SHOULD configure dictionary encoding explicitly in the Arrow exporter to deduplicate repeated high-cardinality metric names, resource attributes, and span 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.
4

Services MUST configure strict bounded columnar buffer pools with `memory_limit_mib` alongside `max_stream_lifetime` to prevent memory fragmentation and OOM killed collector pods.

Services MUST configure strict bounded columnar buffer pools with `memory_limit_mib` alongside `max_stream_lifetime` to prevent memory fragmentation and OOM killed collector pods.

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 emit unbatched Arrow record batches

Components NEVER emit unbatched Arrow record batches; pipelines must enforce a dedicated `batch` processor with timeout and signal size minimums upstream of the Arrow exporter.

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 Apache Arrow Columnar Batching & Wire Protocol Invariant critical for AI coding assistants?

Mandates the usage of Apache Arrow columnar encoding and batching protocols across high-throughput OpenTelemetry Collector pipelines. Standard row-oriented OTLP protobuf serialization introduces massive CPU serialization penalties and elevated egress bandwidth costs when handling high-cardinality metrics, traces, and logs. Columnar memory representations enable zero-copy processing, vectorized compression, and drastic memory footprint reduction across collector tiers. 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 (Row-Oriented OTLP Protobuf Overhead Across High-Volume Collector Topologies) 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