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-zero-copy-ingestion-pipeline

OpenTelemetry OTLP Arrow Zero-Copy Telemetry Ingestion Pipeline Invariants

Standardizes OpenTelemetry Collector pipelines to ingest and process columnar telemetry records via Apache Arrow memory layouts without intermediary Protobuf deserialization. Eliminates CPU spikes and heap thrashing caused by row-oriented deserialization loops in high-throughput collector gateways. Mandates zero-copy handoffs, aligned dictionary encoding, and stream-aware memory pool allocations across collector components.

Prohibited Anti-Pattern: Falling Back to Row-Oriented Protobuf Deserialization in High-Throughput OTLP Ingestion Paths

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry OTLP Arrow Zero-Copy Telemetry Ingestion Pipeline Invariants - Standardizes OpenTelemetry Collector pipelines to ingest and process columnar telemetry records via Apache Arrow memory layouts without intermediary Protobuf deserialization. Eliminates CPU spikes and heap thrashing caused by row-oriented deserialization loops in high-throughput collector gateways. Mandates zero-copy handoffs, aligned dictionary encoding, and stream-aware memory pool allocations across collector components.
globs: **/collector.yaml, **/otel-collector*.yaml, **/otelcol-config*.yaml, deployments/**/otel-*.yaml, k8s/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-arrow-zero-copy-ingestion-pipeline"
---

# OpenTelemetry OTLP Arrow Zero-Copy Telemetry Ingestion Pipeline Invariants

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Falling Back to Row-Oriented Protobuf Deserialization in High-Throughput OTLP Ingestion Paths

## System Constraints
You are a Principal Observability Infrastructure Architect enforcing strict adherence to Apache Arrow zero-copy pipelines within OpenTelemetry Collector deployments. You must prevent row-oriented Protobuf serialization traps, enforce direct stream pass-through, ensure columnar memory pools are explicitly bounded, and preserve Arrow RecordBatch structures across receiver, processor, and exporter pipelines.

## Strict Guidelines
- Collectors MUST configure the 'oteparow' (or 'arrow') protocol receiver alongside gRPC endpoints to bypass standard OTLP Protobuf deserialization.
- Engineers MUST NOT introduce non-Arrow-aware processors (e.g., legacy regex transformprocessors or metricstransform) into the Arrow stream pipeline, which forces serialization fallback.
- Memory limiter processors MUST be placed before schema validation, configured with explicit memory ballast checks calibrated to Arrow off-heap or direct buffer allocations.
- Arrow exporters MUST maintain batch dictionary sharing and set 'arrow.low_memory' or bounded chunk limits to prevent uncontrolled arena growth in high-cardinality label spaces.
- Exporters MUST utilize HTTP/2 or gRPC streaming with bidirectional compression (Zstandard or LZ4) configured strictly at the Arrow RecordBatch level rather than frame-level re-encoding.

## Bad vs Good Implementations
### Configuring OTLP Arrow Receiver and Exporter with Zero-Copy Preservation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Standard OTLP receiver unmarshals protobuf payloads into pdata heap structures, and the row-oriented transform processor prevents columnar representation. This causes severe GC pauses and defeats Arrow zero-copy advantages.
```yaml
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318

processors:
  batch:
    send_batch_size: 8192
    timeout: 1s
  # ANTI-PATTERN: Standard transform processor forces row-oriented deserialization
  transform:
    error_mode: ignore
    log_statements:
      - context: log
        statements:
          - set(attributes["cluster"], "us-east-1")

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

service:
  pipelines:
    logs:
      receivers: [otlp]
      processors: [transform, batch]
      exporters: [otlp]
```

#### Production Standard (Correct)
> **Standard**: Enables the Arrow extension within the gRPC receiver and routes directly to the otlp_arrow exporter without disruptive row-based processors, maintaining zero-copy Arrow RecordBatches end-to-end.
```yaml
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        arrow:
          memory_limit_mib: 512
          max_concurrent_streams: 128

processors:
  memory_limiter:
    check_interval: 250ms
    limit_percentage: 80
    spike_limit_percentage: 20
  batch:
    send_batch_size: 16384
    timeout: 500ms

exporters:
  otlp_arrow:
    endpoint: downstream-collector:4317
    tls:
      insecure: true
    arrow:
      num_streams: 4
      compression: zstd
      dict_size_limit_mib: 16

service:
  pipelines:
    logs:
      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.

Kubernetes Resource Inspector
Inspects running OpenTelemetry Collector DaemonSets and ConfigMaps to verify Arrow configuration directives.
Recommended Agent Skills (askills.dev)

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

OTel Collector Config Validator
Validates OpenTelemetry Collector pipeline components and flags incompatible row/columnar processor combinations via otelcol validate.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry OTLP Arrow Zero-Copy Telemetry Ingestion Pipeline Invariants

OpenTelemetry OTLP Arrow Zero-Copy Telemetry Ingestion Pipeline Invariants defines an industrial-grade behavioral standard for devops engineering. Standardizes OpenTelemetry Collector pipelines to ingest and process columnar telemetry records via Apache Arrow memory layouts without intermediary Protobuf deserialization. Eliminates CPU spikes and heap thrashing caused by row-oriented deserialization loops in high-throughput collector gateways. Mandates zero-copy handoffs, aligned dictionary encoding, and stream-aware memory pool allocations across collector components. 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: Falling Back to Row-Oriented Protobuf Deserialization in High-Throughput OTLP Ingestion Paths 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 DriftFalling Back to Row-Oriented Protobuf Deserialization in High-Throughput OTLP Ingestion PathsCritical
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

Collectors MUST configure the 'oteparow' (or 'arrow') protocol receiver alongside gRPC endpoints to bypass standard OTLP Protobuf deserialization.

Collectors MUST configure the 'oteparow' (or 'arrow') protocol receiver alongside gRPC endpoints to bypass standard OTLP Protobuf deserialization.

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 introduce non-Arrow-aware processors (e.g., legacy regex transformprocessors or metricstransform) into the Arrow stream pipeline, which forces serialization fallback.

Engineers MUST NOT introduce non-Arrow-aware processors (e.g., legacy regex transformprocessors or metricstransform) into the Arrow stream pipeline, which forces serialization fallback.

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

Memory limiter processors MUST be placed before schema validation, configured with explicit memory ballast checks calibrated to Arrow off-heap or direct buffer allocations.

Memory limiter processors MUST be placed before schema validation, configured with explicit memory ballast checks calibrated to Arrow off-heap or direct buffer 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.
4

Arrow exporters MUST maintain batch dictionary sharing and set 'arrow.low_memory' or bounded chunk limits to prevent uncontrolled arena growth in high-cardinality label spaces.

Arrow exporters MUST maintain batch dictionary sharing and set 'arrow.low_memory' or bounded chunk limits to prevent uncontrolled arena growth in high-cardinality label spaces.

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

Exporters MUST utilize HTTP/2 or gRPC streaming with bidirectional compression (Zstandard or LZ4) configured strictly at the Arrow RecordBatch level rather than frame-level re-encoding.

Exporters MUST utilize HTTP/2 or gRPC streaming with bidirectional compression (Zstandard or LZ4) configured strictly at the Arrow RecordBatch level rather than frame-level re-encoding.

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 Zero-Copy Telemetry Ingestion Pipeline Invariants critical for AI coding assistants?

Standardizes OpenTelemetry Collector pipelines to ingest and process columnar telemetry records via Apache Arrow memory layouts without intermediary Protobuf deserialization. Eliminates CPU spikes and heap thrashing caused by row-oriented deserialization loops in high-throughput collector gateways. Mandates zero-copy handoffs, aligned dictionary encoding, and stream-aware memory pool allocations across collector components. 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 (Falling Back to Row-Oriented Protobuf Deserialization in High-Throughput OTLP Ingestion Paths) 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