OpenTelemetry Two-Tier Tail-Based Sampling and Memory Limiter Guardrail | 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-tail-sampling-adaptive-buffer-standard

OpenTelemetry Two-Tier Tail-Based Sampling and Memory Limiter Guardrail

Enforces a two-tier OpenTelemetry Collector architecture utilizing trace-ID load balancing and tail-based sampling with memory limiter processors. Guarantees 100% capture of distributed traces exhibiting errors or latency anomalies while adaptively shedding nominal traffic and preventing out-of-memory crashes.

Prohibited Anti-Pattern: Blind Head-Based Sampling and Unbounded Collector In-Memory Buffers

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Two-Tier Tail-Based Sampling and Memory Limiter Guardrail - Enforces a two-tier OpenTelemetry Collector architecture utilizing trace-ID load balancing and tail-based sampling with memory limiter processors. Guarantees 100% capture of distributed traces exhibiting errors or latency anomalies while adaptively shedding nominal traffic and preventing out-of-memory crashes.
globs: **/otel-collector*.{yaml,yml}, **/collector/**/*.{yaml,yml}, **/telemetry/**/*.{ts,js,yaml,yml}, k8s/**/collector*.{yaml,yml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-tail-sampling-adaptive-buffer-standard"
---

# OpenTelemetry Two-Tier Tail-Based Sampling and Memory Limiter Guardrail

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Blind Head-Based Sampling and Unbounded Collector In-Memory Buffers

## System Constraints
You are a Principal Observability and Infrastructure Architect enforcing industrial-grade OpenTelemetry configurations. You mandate deterministic retention of distributed traces containing errors, exceptions, and p95+ latency degradations while controlling network egress costs and eliminating collector buffer starvation.

## Strict Guidelines
- Engineers MUST configure upstream SDKs with ParentBased(AlwaysOn) or 100% head sampling, delegating sampling decisions entirely to downstream tail-sampling collectors.
- Engineers MUST deploy a two-tier collector topology where Tier-1 (daemon/agent) routes traces using `loadbalancingexporter` keyed by `trace_id` so all spans of a trace arrive at the same Tier-2 tail-sampling instance.
- Tier-2 collectors MUST configure the `memory_limiter` processor immediately before the `tail_sampling` processor in the trace pipeline to prevent process termination under unexpected traffic spikes.
- The `tail_sampling` processor MUST implement composite policies prioritizing: (1) 100% capture of error status codes (`STATUS_CODE_ERROR`, HTTP 5xx), (2) 100% capture of latency exceeding service SLAs, and (3) deterministic low-percentage probabilistic sampling for nominal traffic.
- Collectors MUST configure `decision_wait` to exceed the p99 end-to-end distributed transaction duration while tuning `num_traces` and memory limits to prevent premature span eviction.
- Components NEVER drop root spans at the client SDK level when downstream services may fail asynchronously.

## Bad vs Good Implementations
### Tier-2 OpenTelemetry Collector Tail-Sampling Pipeline Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Applying purely probabilistic sampling at the tail drops 90% of business-critical runtime errors and latency anomalies. Allocating an unbounded `num_traces` buffer without a preceding `memory_limiter` processor results in catastrophic collector OOM termination during traffic surges.
```yaml
# Anti-Pattern: Unprotected tail sampling, no load balancing consideration, missing error catch
processors:
  tail_sampling:
    decision_wait: 30s
    num_traces: 1000000 # Memory hazard: unbounded trace allocation causes OOM kills
    expected_new_traces_per_sec: 10000
    policies:
      - name: probabilistic-only
        type: probabilistic
        probabilistic:
          sampling_percentage: 10 # Drops 90% of failures, outages, and latency spikes

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [tail_sampling, batch] # Missing memory_limiter before tail_sampling
      exporters: [otlp]
```

#### Production Standard (Correct)
> **Standard**: Guarantees full capture of system failures and SLA violations (latency > 1500ms and HTTP 5xx/ERROR status codes), while pruning 95% of nominal traffic to control egress costs. The `memory_limiter` processor is ordered first to enforce hard limits and prevent process crashes.
```yaml
# Standard: Fault-tolerant tail sampling with memory bounds and deterministic anomaly capture
processors:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 75
    spike_limit_percentage: 20

  tail_sampling:
    decision_wait: 10s
    num_traces: 50000
    expected_new_traces_per_sec: 2500
    policies:
      - name: capture-errors
        type: status_code
        status_code:
          status_codes: [ERROR]
      - name: capture-http-5xx
        type: numeric_attribute
        numeric_attribute:
          key: http.status_code
          min_value: 500
          max_value: 599
      - name: capture-high-latency
        type: latency
        latency:
          threshold_ms: 1500
      - name: nominal-sample-rate
        type: probabilistic
        probabilistic:
          sampling_percentage: 5.0

  batch:
    send_batch_size: 8192
    timeout: 5s

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

Recommended MCP Servers (mcp-serverlist.com)

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

Prometheus & OpenTelemetry Collector Metrics MCP

Inspects live collector buffer utilization, trace decision latency, and dropped trace metrics.

Recommended Agent Skills (askills.dev)

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

OTel Collector Config Validator

CLI tool to validate OpenTelemetry Collector configuration syntax, processor ordering, and memory constraints prior to deployment.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Two-Tier Tail-Based Sampling and Memory Limiter Guardrail

OpenTelemetry Two-Tier Tail-Based Sampling and Memory Limiter Guardrail defines an industrial-grade behavioral standard for devops engineering. Enforces a two-tier OpenTelemetry Collector architecture utilizing trace-ID load balancing and tail-based sampling with memory limiter processors. Guarantees 100% capture of distributed traces exhibiting errors or latency anomalies while adaptively shedding nominal traffic and preventing out-of-memory crashes. 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: Blind Head-Based Sampling and Unbounded Collector In-Memory Buffers 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	Blind Head-Based Sampling and Unbounded Collector In-Memory Buffers	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

Engineers MUST configure upstream SDKs with ParentBased(AlwaysOn) or 100% head sampling, delegating sampling decisions entirely to downstream tail-sampling collectors.

Engineers MUST configure upstream SDKs with ParentBased(AlwaysOn) or 100% head sampling, delegating sampling decisions entirely to downstream tail-sampling collectors.

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 deploy a two-tier collector topology where Tier-1 (daemon/agent) routes traces using `loadbalancingexporter` keyed by `trace_id` so all spans of a trace arrive at the same Tier-2 tail-sampling instance.

Engineers MUST deploy a two-tier collector topology where Tier-1 (daemon/agent) routes traces using `loadbalancingexporter` keyed by `trace_id` so all spans of a trace arrive at the same Tier-2 tail-sampling instance.

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

Tier-2 collectors MUST configure the `memory_limiter` processor immediately before the `tail_sampling` processor in the trace pipeline to prevent process termination under unexpected traffic spikes.

Tier-2 collectors MUST configure the `memory_limiter` processor immediately before the `tail_sampling` processor in the trace pipeline to prevent process termination under unexpected traffic spikes.

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

The `tail_sampling` processor MUST implement composite policies prioritizing

The `tail_sampling` processor MUST implement composite policies prioritizing: (1) 100% capture of error status codes (`STATUS_CODE_ERROR`, HTTP 5xx), (2) 100% capture of latency exceeding service SLAs, and (3) deterministic low-percentage probabilistic sampling for nominal traffic.

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

Collectors MUST configure `decision_wait` to exceed the p99 end-to-end distributed transaction duration while tuning `num_traces` and memory limits to prevent premature span eviction.

Collectors MUST configure `decision_wait` to exceed the p99 end-to-end distributed transaction duration while tuning `num_traces` and memory limits to prevent premature span eviction.

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

Components NEVER drop root spans at the client SDK level when downstream services may fail asynchronously.

Components NEVER drop root spans at the client SDK level when downstream services may fail asynchronously.

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 Two-Tier Tail-Based Sampling and Memory Limiter Guardrail critical for AI coding assistants?

Enforces a two-tier OpenTelemetry Collector architecture utilizing trace-ID load balancing and tail-based sampling with memory limiter processors. Guarantees 100% capture of distributed traces exhibiting errors or latency anomalies while adaptively shedding nominal traffic and preventing out-of-memory crashes. 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 (Blind Head-Based Sampling and Unbounded Collector In-Memory Buffers) 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