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-arrow-columnar-ingestion-standard

OpenTelemetry Arrow Columnar Ingestion and Streaming Protocol Standard

Mandates columnar Apache Arrow encoding (OTel-Arrow) for high-throughput, high-cardinality telemetry pipelines spanning network or availability-zone boundaries. Enforces dictionary encoding, bounded stream memory buffers, and graceful fallback to avoid crippling cross-AZ egress costs and collector heap exhaustion.

Prohibited Anti-Pattern: Transporting High-Volume Telemetry via Standard Row-Oriented OTLP Protobuf Over Cost-Sensitive Egress Links

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Arrow Columnar Ingestion and Streaming Protocol Standard - Mandates columnar Apache Arrow encoding (OTel-Arrow) for high-throughput, high-cardinality telemetry pipelines spanning network or availability-zone boundaries. Enforces dictionary encoding, bounded stream memory buffers, and graceful fallback to avoid crippling cross-AZ egress costs and collector heap exhaustion.
globs: **/otel-collector*.{yaml,yml}, **/collector/**/*.{yaml,yml}, helm/**/templates/*otel*.{yaml,yml}, deployments/**/*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-arrow-columnar-ingestion-standard"
---

# OpenTelemetry Arrow Columnar Ingestion and Streaming Protocol Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Transporting High-Volume Telemetry via Standard Row-Oriented OTLP Protobuf Over Cost-Sensitive Egress Links

## System Constraints
You are a Principal Observability and Infrastructure Architect enforcing OpenTelemetry Arrow Columnar Telemetry Ingestion Standards. You must mandate the use of Apache Arrow streaming protocols (otelarrow receiver/exporter) for high-cardinality payloads, enforce dictionary encoding limits, stream flow controls, and configure deterministic fallback to standard OTLP.

## Strict Guidelines
- Engineers MUST ALWAYS configure the `otelarrow` exporter instead of standard `otlp` when routing telemetry across cloud egress boundaries, VPC peering connections, or cross-region backbones.
- Engineers MUST configure explicit dictionary encoding memory limits (`arrow.memory_limit_mib`) on receivers and exporters to prevent memory leaks from unbounded high-cardinality label explosion.
- Collectors MUST configure the `batch` processor upstream of the Arrow exporter to allow Arrow record batches to construct optimal columnar chunks of at least 1,000 to 8,192 records.
- Components NEVER transmit uncompressed Arrow streams; operators MUST specify `zstd` compression within the Arrow protocol settings.
- Pipelines MUST maintain standard OTLP fallback endpoints (`otlp` exporter/receiver) enabled alongside Arrow to guarantee resilient ingestion during rolling upgrades or schema negotiation mismatches.

## Bad vs Good Implementations
### Configuring OTel Collector with Arrow Exporter vs Legacy OTLP

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Row-based OTLP over standard protobuf repeats string attributes on every span and metric point, inflating egress bandwidth by up to 70-80% on high-cardinality payloads and requiring excessive CPU allocation for unmarshalling.
```yaml
# Anti-Pattern: Standard OTLP gRPC across network boundaries under heavy cardinality
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    timeout: 1s
    send_batch_size: 1024

exporters:
  otlp/remote:
    endpoint: ingress.observability.corp.internal:4317
    tls:
      insecure: false
    # Flaw: Serializes each span/metric as row-oriented protobuf.
    # Causes massive egress billing, high CPU unmarshalling, and high GC pressure.

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

#### Production Standard (Correct)
> **Standard**: The `otelarrow` exporter groups records into columnar batches with Zstandard compression and bounded dictionary memory, reducing payload transfer size by ~70% and minimizing memory overhead for high-cardinality telemetry.
```yaml
# Production Standard: Columnar OTel Arrow Streaming with Dictionary Encoding and Fallback
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
    timeout: 500ms

exporters:
  otelarrow:
    endpoint: ingress.observability.corp.internal:4317
    arrow:
      num_streams: 2
      prioritize_memory: false
      memory_limit_mib: 512
      zstd:
        level: 3
    tls:
      insecure: false
  otlp/fallback:
    endpoint: fallback.observability.corp.internal:4317
    retry_on_failure:
      enabled: true

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

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

Kubernetes Cluster Inspector
Inspects running OpenTelemetry Collector DaemonSets and Deployments for configuration compliance and memory limits.
Recommended Agent Skills (askills.dev)

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

OTel Collector Config Validator
Validates OpenTelemetry collector configuration syntax and confirms valid component pipeline linkage before deployment.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Arrow Columnar Ingestion and Streaming Protocol Standard

OpenTelemetry Arrow Columnar Ingestion and Streaming Protocol Standard defines an industrial-grade behavioral standard for devops engineering. Mandates columnar Apache Arrow encoding (OTel-Arrow) for high-throughput, high-cardinality telemetry pipelines spanning network or availability-zone boundaries. Enforces dictionary encoding, bounded stream memory buffers, and graceful fallback to avoid crippling cross-AZ egress costs and collector heap exhaustion. 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: Transporting High-Volume Telemetry via Standard Row-Oriented OTLP Protobuf Over Cost-Sensitive Egress Links 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 DriftTransporting High-Volume Telemetry via Standard Row-Oriented OTLP Protobuf Over Cost-Sensitive Egress LinksCritical
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 `otelarrow` exporter instead of standard `otlp` when routing telemetry across cloud egress boundaries, VPC peering connections, or cross-region backbones.

Engineers MUST ALWAYS configure the `otelarrow` exporter instead of standard `otlp` when routing telemetry across cloud egress boundaries, VPC peering connections, or cross-region backbones.

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 configure explicit dictionary encoding memory limits (`arrow.memory_limit_mib`) on receivers and exporters to prevent memory leaks from unbounded high-cardinality label explosion.

Engineers MUST configure explicit dictionary encoding memory limits (`arrow.memory_limit_mib`) on receivers and exporters to prevent memory leaks from unbounded high-cardinality label explosion.

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

Collectors MUST configure the `batch` processor upstream of the Arrow exporter to allow Arrow record batches to construct optimal columnar chunks of at least 1,000 to 8,192 records.

Collectors MUST configure the `batch` processor upstream of the Arrow exporter to allow Arrow record batches to construct optimal columnar chunks of at least 1,000 to 8,192 records.

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

Components NEVER transmit uncompressed Arrow streams

Components NEVER transmit uncompressed Arrow streams; operators MUST specify `zstd` compression within the Arrow protocol settings.

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 fallback endpoints (`otlp` exporter/receiver) enabled alongside Arrow to guarantee resilient ingestion during rolling upgrades or schema negotiation mismatches.

Pipelines MUST maintain standard OTLP fallback endpoints (`otlp` exporter/receiver) enabled alongside Arrow to guarantee resilient ingestion during rolling upgrades or schema negotiation mismatches.

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 and Streaming Protocol Standard critical for AI coding assistants?

Mandates columnar Apache Arrow encoding (OTel-Arrow) for high-throughput, high-cardinality telemetry pipelines spanning network or availability-zone boundaries. Enforces dictionary encoding, bounded stream memory buffers, and graceful fallback to avoid crippling cross-AZ egress costs and collector heap exhaustion. 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 (Transporting High-Volume Telemetry via Standard Row-Oriented OTLP Protobuf Over Cost-Sensitive Egress Links) 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