OpenTelemetry Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard | 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-arrow-columnar-ingestion-standard-opentelemetry-ar-590

OpenTelemetry Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard

Mandates the deployment of Apache Arrow columnar telemetry encoding across all high-throughput OpenTelemetry collector tiers and edge daemons. Eliminates row-oriented protobuf object allocations to eradicate stop-the-world garbage collection pauses and reduce CPU utilization under high-cardinality telemetry loads.

Prohibited Anti-Pattern: Row-Oriented Protobuf Serialization Flooding Collector Heap and Triggering Fatal GC Stalls

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard - Mandates the deployment of Apache Arrow columnar telemetry encoding across all high-throughput OpenTelemetry collector tiers and edge daemons. Eliminates row-oriented protobuf object allocations to eradicate stop-the-world garbage collection pauses and reduce CPU utilization under high-cardinality telemetry loads.
globs: **/otel-collector*.{yaml,yml}, **/collector/**/*.{yaml,yml}, deployments/**/*.{yaml,yml}, k8s/**/*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-arrow-columnar-ingestion-standard-opentelemetry-ar-590"
---

# OpenTelemetry Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Row-Oriented Protobuf Serialization Flooding Collector Heap and Triggering Fatal GC Stalls

## System Constraints
You are a Principal Software Architect enforcing the OpenTelemetry Arrow Columnar Ingestion Throughput Standard. You MUST reject standard row-based OTLP (otlp/protobuf) in favor of the Apache Arrow columnar protocol (otelarrow) across edge collectors, gateways, and aggregation pipelines processing sustained loads exceeding 10,000 metrics/traces/logs per second. Enforce dictionary encoding, columnar batching, zstd stream compression, and strict memory limits to guarantee zero-copy performance and eliminate Go runtime garbage collection pauses.

## Strict Guidelines
- Collectors MUST configure the 'otelarrow' exporter and receiver plugins instead of standard row-oriented 'otlp' for high-throughput collector-to-collector and collector-to-backend hops.
- Pipelines MUST place the 'batch' processor directly before the 'otelarrow' exporter with a minimum send_batch_max_size of 8192 records to ensure optimal Arrow RecordBatch compression and dictionary utilization.
- Engineers MUST enable dictionary encoding in the 'otelarrow' configuration to deduplicate repeated high-cardinality string attributes (e.g., container_id, host_id, span attributes).
- Pipelines MUST include the 'memory_limiter' processor as the first processor in all telemetry pipelines, configured with check_interval: 1s and limit_percentage: 80 to prevent OOM kills during Arrow stream batching.
- Edge daemon collectors MUST NOT ingest or process raw unbatched protobuf streams without immediate columnar conversion if total export throughput exceeds 10k EPS/MPS.
- Services MUST enable stream-level zstd compression ('compression: zstd') within the otelarrow transport configuration to minimize inter-cluster egress bandwidth.

## Bad vs Good Implementations
### Migrating Edge/Gateway Collector Config to OTel Arrow Columnar Pipeline

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Standard OTLP via gRPC deserializes every span/metric into individual Go heap pointers, driving up GC pressure by 10x-50x and inducing latency spikes and dropped telemetry under peak traffic.
```yaml
# CRITICAL FAILURE: Standard OTLP protobuf pipeline causes extreme heap allocation,
# frequent GC pauses, and CPU saturation under high cardinality loads.
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    send_batch_size: 512
    timeout: 1s

exporters:
  otlp/backend:
    endpoint: telemetry-gateway.internal:4317
    tls:
      insecure: true

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

#### Production Standard (Correct)
> **Standard**: Configures the otelarrow receiver and exporter with memory safety bounds, high-density columnar batching, and zstd stream compression. Dictionary encoding eliminates redundant string allocations, reducing memory footprint by up to 70% and slashing collector CPU overhead.
```yaml
# PRODUCTION STANDARD: OpenTelemetry Arrow columnar pipeline
# Uses zero-copy Arrow memory buffers, dictionary encoding, and stream zstd compression.
receivers:
  otelarrow:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  memory_limiter:
    check_interval: 500ms
    limit_percentage: 80
    spike_limit_percentage: 20
  batch:
    send_batch_size: 8192
    send_batch_max_size: 16384
    timeout: 200ms

exporters:
  otelarrow/backend:
    endpoint: telemetry-gateway.internal:4317
    tls:
      insecure: true
    arrow:
      num_streams: 4
      compression: zstd
      dict_limit: 1024

service:
  pipelines:
    traces:
      receivers: [otelarrow]
      processors: [memory_limiter, batch]
      exporters: [otelarrow/backend]
```

Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Inspector

Verifies deployed OpenTelemetry collector daemonsets, pod memory limits, and container runtime restart metrics.

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 otelarrow components and memory limiter constraints.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard

OpenTelemetry Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard defines an industrial-grade behavioral standard for devops engineering. Mandates the deployment of Apache Arrow columnar telemetry encoding across all high-throughput OpenTelemetry collector tiers and edge daemons. Eliminates row-oriented protobuf object allocations to eradicate stop-the-world garbage collection pauses and reduce CPU utilization under high-cardinality 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: Row-Oriented Protobuf Serialization Flooding Collector Heap and Triggering Fatal GC Stalls 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	Row-Oriented Protobuf Serialization Flooding Collector Heap and Triggering Fatal GC Stalls	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 'otelarrow' exporter and receiver plugins instead of standard row-oriented 'otlp' for high-throughput collector-to-collector and collector-to-backend hops.

Collectors MUST configure the 'otelarrow' exporter and receiver plugins instead of standard row-oriented 'otlp' for high-throughput collector-to-collector and collector-to-backend hops.

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

Pipelines MUST place the 'batch' processor directly before the 'otelarrow' exporter with a minimum send_batch_max_size of 8192 records to ensure optimal Arrow RecordBatch compression and dictionary utilization.

Pipelines MUST place the 'batch' processor directly before the 'otelarrow' exporter with a minimum send_batch_max_size of 8192 records to ensure optimal Arrow RecordBatch compression and dictionary utilization.

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 enable dictionary encoding in the 'otelarrow' configuration to deduplicate repeated high-cardinality string attributes (e.g., container_id, host_id, span attributes).

Engineers MUST enable dictionary encoding in the 'otelarrow' configuration to deduplicate repeated high-cardinality string attributes (e.g., container_id, host_id, 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

Pipelines MUST include the 'memory_limiter' processor as the first processor in all telemetry pipelines, configured with check_interval

Pipelines MUST include the 'memory_limiter' processor as the first processor in all telemetry pipelines, configured with check_interval: 1s and limit_percentage: 80 to prevent OOM kills during Arrow stream batching.

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

Edge daemon collectors MUST NOT ingest or process raw unbatched protobuf streams without immediate columnar conversion if total export throughput exceeds 10k EPS/MPS.

Edge daemon collectors MUST NOT ingest or process raw unbatched protobuf streams without immediate columnar conversion if total export throughput exceeds 10k EPS/MPS.

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

Services MUST enable stream-level zstd compression ('compression

Services MUST enable stream-level zstd compression ('compression: zstd') within the otelarrow transport configuration to minimize inter-cluster egress bandwidth.

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 Arrow Columnar Ingestion Throughput and Zero-Copy Pipeline Standard critical for AI coding assistants?

Mandates the deployment of Apache Arrow columnar telemetry encoding across all high-throughput OpenTelemetry collector tiers and edge daemons. Eliminates row-oriented protobuf object allocations to eradicate stop-the-world garbage collection pauses and reduce CPU utilization under high-cardinality 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 (Row-Oriented Protobuf Serialization Flooding Collector Heap and Triggering Fatal GC Stalls) 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