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-otlp-over-quic-ingestion-standard

OpenTelemetry OTLP-over-QUIC Loss-Resilient Ingestion Standard

Mandates the use of HTTP/3 and QUIC transport protocols for OpenTelemetry Protocol (OTLP) pipelines crossing WAN boundaries and availability zones. Multiplexed independent QUIC streams eliminate TCP head-of-line blocking, preventing catastrophic trace dropouts and telemetry buffer backpressure under degraded network conditions.

Prohibited Anti-Pattern: TCP Head-of-Line Blocking Inducing Telemetry Buffer Overflows During WAN Congestion

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry OTLP-over-QUIC Loss-Resilient Ingestion Standard - Mandates the use of HTTP/3 and QUIC transport protocols for OpenTelemetry Protocol (OTLP) pipelines crossing WAN boundaries and availability zones. Multiplexed independent QUIC streams eliminate TCP head-of-line blocking, preventing catastrophic trace dropouts and telemetry buffer backpressure under degraded network conditions.
globs: **/otel-collector*.{yaml,yml}, **/collector/*.{yaml,yml}, deploy/kubernetes/**/*.{yaml,yml}, src/observability/**/*.{ts,js,go}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-otlp-over-quic-ingestion-standard"
---

# OpenTelemetry OTLP-over-QUIC Loss-Resilient Ingestion Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: TCP Head-of-Line Blocking Inducing Telemetry Buffer Overflows During WAN Congestion

## System Constraints
You are a Principal Software Architect enforcing the OpenTelemetry OTLP-over-QUIC Loss-Resilient Ingestion Standard. You must reject any cross-region or inter-datacenter telemetry pipeline that couples multi-tenant traces and metrics to single TCP connections (standard gRPC/HTTP/2) without head-of-line blocking mitigations. Enforce multiplexed QUIC (HTTP/3) transport configurations, bounded memory queues, and robust TLS 1.3 / ALPN parameters.

## Strict Guidelines
- Engineers MUST ALWAYS configure cross-region OTLP exporters to use HTTP/3 (QUIC) to decouple stream packet losses across independent span/metric batches.
- Engineers MUST NOT rely on standard gRPC-over-TCP or HTTP/2 across lossy WAN networks where a single dropped packet stalls the entire telemetry stream.
- Collectors MUST configure bounded memory-limiter processors before queued retry processors to prevent out-of-memory (OOM) panics during upstream degradation.
- Pipelines SHOULD implement ALPN negotiation explicitly specifying 'h3' alongside fallback mechanisms with exponential jittered backoff.
- Exporters NEVER use infinite retry intervals or unconstrained send queues when underlying QUIC congestion control triggers flow backpressure.

## Bad vs Good Implementations
### OpenTelemetry Collector OTLP Egress Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using standard OTLP/gRPC over TCP causes cross-stream TCP head-of-line blocking during cross-region packet drops. When packet loss occurs, all span and metric batches on the TCP connection stall waiting for retransmissions, exhausting local buffers and dropping critical observability data.
```yaml
# Anti-Pattern: Standard gRPC (HTTP/2 over TCP) across WAN boundaries.
# A single dropped packet stalls all multiplexed telemetry channels (Head-of-Line blocking).
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

exporters:
  otlp:
    endpoint: regional-collector.us-east.corp.internal:4317
    tls:
      insecure: false
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s

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

#### Production Standard (Correct)
> **Standard**: Configuring OTLP HTTP/3 over QUIC isolates span batches into independent transport streams. Packet drops only delay the affected batch stream, preserving throughput on non-impacted streams while the memory_limiter and bounded sending_queue safeguard memory stability.
```yaml
# Production Standard: OTLP HTTP/3 (QUIC) Transport with Bounded Ingestion
receivers:
  otlp:
    protocols:
      http:
        endpoint: 0.0.0.0:4318

processors:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 75
    spike_limit_percentage: 20
  batch:
    send_batch_size: 8192
    timeout: 500ms

exporters:
  otlphttp:
    endpoint: https://regional-collector.us-east.corp.internal:4318
    encoding: proto
    http3:
      enabled: true
    tls:
      min_version: '1.3'
    retry_on_failure:
      enabled: true
      initial_interval: 1s
      max_interval: 10s
      max_elapsed_time: 1m
    sending_queue:
      enabled: true
      num_consumers: 8
      queue_size: 5000

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

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

OTel Collector Config Validator
Validates OpenTelemetry collector configuration components, pipeline schemas, and transport protocol parameters.
Recommended Agent Skills (askills.dev)

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

OTel Collector Validator CLI
Executes static configuration validation tests against otel-collector deployment manifests.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry OTLP-over-QUIC Loss-Resilient Ingestion Standard

OpenTelemetry OTLP-over-QUIC Loss-Resilient Ingestion Standard defines an industrial-grade behavioral standard for devops engineering. Mandates the use of HTTP/3 and QUIC transport protocols for OpenTelemetry Protocol (OTLP) pipelines crossing WAN boundaries and availability zones. Multiplexed independent QUIC streams eliminate TCP head-of-line blocking, preventing catastrophic trace dropouts and telemetry buffer backpressure under degraded network conditions. 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: TCP Head-of-Line Blocking Inducing Telemetry Buffer Overflows During WAN Congestion 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 DriftTCP Head-of-Line Blocking Inducing Telemetry Buffer Overflows During WAN CongestionCritical
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 cross-region OTLP exporters to use HTTP/3 (QUIC) to decouple stream packet losses across independent span/metric batches.

Engineers MUST ALWAYS configure cross-region OTLP exporters to use HTTP/3 (QUIC) to decouple stream packet losses across independent span/metric batches.

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 rely on standard gRPC-over-TCP or HTTP/2 across lossy WAN networks where a single dropped packet stalls the entire telemetry stream.

Engineers MUST NOT rely on standard gRPC-over-TCP or HTTP/2 across lossy WAN networks where a single dropped packet stalls the entire telemetry stream.

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 bounded memory-limiter processors before queued retry processors to prevent out-of-memory (OOM) panics during upstream degradation.

Collectors MUST configure bounded memory-limiter processors before queued retry processors to prevent out-of-memory (OOM) panics during upstream degradation.

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 SHOULD implement ALPN negotiation explicitly specifying 'h3' alongside fallback mechanisms with exponential jittered backoff.

Pipelines SHOULD implement ALPN negotiation explicitly specifying 'h3' alongside fallback mechanisms with exponential jittered backoff.

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 NEVER use infinite retry intervals or unconstrained send queues when underlying QUIC congestion control triggers flow backpressure.

Exporters NEVER use infinite retry intervals or unconstrained send queues when underlying QUIC congestion control triggers flow backpressure.

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-over-QUIC Loss-Resilient Ingestion Standard critical for AI coding assistants?

Mandates the use of HTTP/3 and QUIC transport protocols for OpenTelemetry Protocol (OTLP) pipelines crossing WAN boundaries and availability zones. Multiplexed independent QUIC streams eliminate TCP head-of-line blocking, preventing catastrophic trace dropouts and telemetry buffer backpressure under degraded network conditions. 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 (TCP Head-of-Line Blocking Inducing Telemetry Buffer Overflows During WAN Congestion) 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