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-stream-backpressure-ceiling

OTLP/Arrow Ingestion Stream Backpressure and Columnar Chunk Sizing Guardrail

Enforces strict columnar record-batch sizing and stream-level reactive backpressure limits on OpenTelemetry Arrow (OTLP-Arrow) receiver and exporter topologies. Prevents catastrophic collector out-of-memory (OOM) fatal crashes and heap fragmentation when handling multi-gigabyte telemetry ingestion bursts.

Prohibited Anti-Pattern: Unbounded Arrow record batch sizes and unthrottled gRPC stream buffering causing collector OOM panics during high-volume spikes

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OTLP/Arrow Ingestion Stream Backpressure and Columnar Chunk Sizing Guardrail - Enforces strict columnar record-batch sizing and stream-level reactive backpressure limits on OpenTelemetry Arrow (OTLP-Arrow) receiver and exporter topologies. Prevents catastrophic collector out-of-memory (OOM) fatal crashes and heap fragmentation when handling multi-gigabyte telemetry ingestion bursts.
globs: **/otelcol*.{yaml,yml}, **/collector/*.{yaml,yml}, **/arrow*.{go,yaml,yml}, **/deployments/**/*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-arrow-stream-backpressure-ceiling"
---

# OTLP/Arrow Ingestion Stream Backpressure and Columnar Chunk Sizing Guardrail

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unbounded Arrow record batch sizes and unthrottled gRPC stream buffering causing collector OOM panics during high-volume spikes

## System Constraints
You are a Principal DevOps and Observability Infrastructure Architect enforcing strict ingestion safety invariants for OpenTelemetry Arrow (OTLP-Arrow) streaming pipelines. OTLP-Arrow leverages Apache Arrow IPC streams over gRPC, yielding high compression ratios at the expense of steep instantaneous memory allocations during dictionary encoding and batch serialization. You must enforce deterministic chunk ceilings, hard limits on concurrent streams, memory_limiter placement, and proactive stream backpressure to eliminate the risk of out-of-memory (OOM) process termination during sudden burst traffic.

## Strict Guidelines
- Engineers MUST ALWAYS declare an explicit `memory_limiter` processor as the FIRST processor in both metrics, logs, and traces pipelines handling Arrow streams.
- Engineers MUST ALWAYS configure the `arrow` block in the receiver with strict `max_stream_lifecycle` and concurrent stream ceilings (`max_concurrent_streams`) to prevent unconstrained Arrow dictionary growth.
- Engineers MUST configure explicit batch chunk limits (`max_rows_per_batch` or `max_bytes_per_batch`) rather than leaving batch boundaries unbound.
- Engineers MUST NEVER enable Arrow streaming without configuring both `check_interval` and `limit_percentage` (or `limit_mib`) alongside `spike_limit_percentage` (or `spike_limit_mib`) in the memory limiter processor.
- Receivers MUST reject or throttle incoming streams via gRPC status `RESOURCE_EXHAUSTED` (backpressure) before resident heap triggers the operating system Out-Of-Memory (OOM) killer.

## Bad vs Good Implementations
### OTLP-Arrow Receiver and Pipeline Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The 'arrow' block is empty, which uses default unbounded dictionary allocations and permits an indefinite number of active streaming sessions. The pipeline lacks a 'memory_limiter' processor, meaning multi-gigabyte telemetry bursts will cause instantaneous memory spikes during columnar decompression, triggering an unrecoverable SIGKILL from the Linux OOM killer.
```yaml
# Dangerous: Unconstrained Arrow receiver configuration without memory limits or stream backpressure
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        arrow: {}

processors:
  batch:
    send_batch_size: 10000
    timeout: 10s

service:
  pipelines:
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]

```

#### Production Standard (Correct)
> **Standard**: The hardened configuration constrains gRPC stream concurrency, enforces a stream lifecycle expiration to cycle Arrow dictionary encoders, bounds batch row limits, and positions the memory_limiter at the entry point of the pipeline to trigger downstream backpressure and signal RESOURCE_EXHAUSTED before memory capacity is exceeded.
```yaml
# Hardened: Explicit Arrow record batch ceilings, stream concurrency constraints, and proactive backpressure
receivers:
  otlp:
`protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        max_concurrent_streams: 1024
        arrow:
          max_stream_lifecycle: 5m
          memory_limit_mib: 1024

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

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

```
Recommended MCP Servers (mcp-serverlist.com)

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

OTel Config Validator MCP
Validates OpenTelemetry collector topologies, components, and processor order against production schema standards.
Recommended Agent Skills (askills.dev)

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

Collector Validation CLI
Runs dry-run validation and syntax checks directly on OpenTelemetry Collector configuration bundles.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OTLP/Arrow Ingestion Stream Backpressure and Columnar Chunk Sizing Guardrail

OTLP/Arrow Ingestion Stream Backpressure and Columnar Chunk Sizing Guardrail defines an industrial-grade behavioral standard for devops engineering. Enforces strict columnar record-batch sizing and stream-level reactive backpressure limits on OpenTelemetry Arrow (OTLP-Arrow) receiver and exporter topologies. Prevents catastrophic collector out-of-memory (OOM) fatal crashes and heap fragmentation when handling multi-gigabyte telemetry ingestion bursts. 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: Unbounded Arrow record batch sizes and unthrottled gRPC stream buffering causing collector OOM panics during high-volume spikes 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 DriftUnbounded Arrow record batch sizes and unthrottled gRPC stream buffering causing collector OOM panics during high-volume spikesCritical
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 declare an explicit `memory_limiter` processor as the FIRST processor in both metrics, logs, and traces pipelines handling Arrow streams.

Engineers MUST ALWAYS declare an explicit `memory_limiter` processor as the FIRST processor in both metrics, logs, and traces pipelines handling Arrow streams.

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 ALWAYS configure the `arrow` block in the receiver with strict `max_stream_lifecycle` and concurrent stream ceilings (`max_concurrent_streams`) to prevent unconstrained Arrow dictionary growth.

Engineers MUST ALWAYS configure the `arrow` block in the receiver with strict `max_stream_lifecycle` and concurrent stream ceilings (`max_concurrent_streams`) to prevent unconstrained Arrow dictionary 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.
3

Engineers MUST configure explicit batch chunk limits (`max_rows_per_batch` or `max_bytes_per_batch`) rather than leaving batch boundaries unbound.

Engineers MUST configure explicit batch chunk limits (`max_rows_per_batch` or `max_bytes_per_batch`) rather than leaving batch boundaries unbound.

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 NEVER enable Arrow streaming without configuring both `check_interval` and `limit_percentage` (or `limit_mib`) alongside `spike_limit_percentage` (or `spike_limit_mib`) in the memory limiter processor.

Engineers MUST NEVER enable Arrow streaming without configuring both `check_interval` and `limit_percentage` (or `limit_mib`) alongside `spike_limit_percentage` (or `spike_limit_mib`) in the memory limiter processor.

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

Receivers MUST reject or throttle incoming streams via gRPC status `RESOURCE_EXHAUSTED` (backpressure) before resident heap triggers the operating system Out-Of-Memory (OOM) killer.

Receivers MUST reject or throttle incoming streams via gRPC status `RESOURCE_EXHAUSTED` (backpressure) before resident heap triggers the operating system Out-Of-Memory (OOM) killer.

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 OTLP/Arrow Ingestion Stream Backpressure and Columnar Chunk Sizing Guardrail critical for AI coding assistants?

Enforces strict columnar record-batch sizing and stream-level reactive backpressure limits on OpenTelemetry Arrow (OTLP-Arrow) receiver and exporter topologies. Prevents catastrophic collector out-of-memory (OOM) fatal crashes and heap fragmentation when handling multi-gigabyte telemetry ingestion bursts. 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 (Unbounded Arrow record batch sizes and unthrottled gRPC stream buffering causing collector OOM panics during high-volume spikes) 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

OTLP/Arrow