OpenTelemetry Collector Tail-Sampling Latency Guardrail Quotas | 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: otel-collector-tail-sampling-latency-guardrails

OpenTelemetry Collector Tail-Sampling Latency Guardrail Quotas

Configures OpenTelemetry Collector tail-sampling pipelines to capture 100% of SLO-breaching latencies and unhandled errors while strictly enforcing deterministic downsampling and rate-limiting on high-frequency nominal traffic. Prevents catastrophic cloud observability ingestion cost overruns without creating blind spots in high-percentile latency distributions.

Prohibited Anti-Pattern: Naive Head-Sampling and Unbounded Tail-Sampling Causing Budget Depletion or Missed P99 Anomalies

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Collector Tail-Sampling Latency Guardrail Quotas - Configures OpenTelemetry Collector tail-sampling pipelines to capture 100% of SLO-breaching latencies and unhandled errors while strictly enforcing deterministic downsampling and rate-limiting on high-frequency nominal traffic. Prevents catastrophic cloud observability ingestion cost overruns without creating blind spots in high-percentile latency distributions.
globs: **/otel-collector*.yaml, **/otel-collector*.yml, **/collector-config*.yaml, deploy/kubernetes/**/*.yaml
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/otel-collector-tail-sampling-latency-guardrails"
---

# OpenTelemetry Collector Tail-Sampling Latency Guardrail Quotas

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Naive Head-Sampling and Unbounded Tail-Sampling Causing Budget Depletion or Missed P99 Anomalies

## System Constraints
You are a Principal Observability and Infrastructure Architect enforcing deterministic tail-sampling policies in OpenTelemetry Collector deployments. You must prevent memory exhaustion and runaway cloud telemetry billing by mandating memory_limiter order, explicit latency thresholds, error span guarantees, and probabilistic quotas on high-volume endpoints.

## Strict Guidelines
- Collectors MUST position the 'memory_limiter' processor BEFORE the 'tail_sampling' processor in the pipeline to prevent Out-Of-Memory (OOM) kills during trace buffering.
- The 'tail_sampling' configuration MUST include an inverted filter or drop policy for routine synthetic traffic (e.g., /healthz, /ready, metrics scrapes) prior to probabilistic evaluation.
- Pipelines MUST guarantee 100% sampling for traces containing span status 'STATUS_CODE_ERROR' or unhandled exceptions.
- Pipelines MUST guarantee 100% sampling for traces exceeding the defined SLO latency threshold (e.g., threshold_ms: 1500) using the 'numeric_attribute' or 'latency' filter.
- Nominal traffic that conforms to latency SLOs MUST be governed by a composite or probabilistic sampler with a maximum rate quota to cap vendor ingestion budgets.
- Collectors MUST specify 'expected_new_traces_per_sec' and 'decision_wait' parameters calibrated against maximum expected P99 duration and batch memory limits.

## Bad vs Good Implementations
### Tail-Sampling Processor Configuration with Latency Guardrails

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Random head-sampling discards 90% of P99 and P99.9 latency spikes and error traces before trace completion, destroying diagnostic utility while still transmitting high volumes of useless nominal health-check traces.
```yaml
# Anti-pattern: Missing memory_limiter guard, no error/SLO latency isolation, head-sampling only
processors:
  probabilistic_sampler:
    sampling_percentage: 10

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [probabilistic_sampler, batch]
      exporters: [otlp/datadog]
```

#### Production Standard (Correct)
> **Standard**: Protects collector memory with memory_limiter first, guarantees 100% capture of error states and SLO breaches (>1200ms), prunes noisy liveness checks, and downsamples routine nominal requests to 1% to strictly enforce cloud ingest budgets.
```yaml
# Production Standard: Memory-guarded tail-sampling with SLO preservation and routine quota caps
processors:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 75
    spike_limit_percentage: 15

  tail_sampling:
    decision_wait: 10s
    num_traces: 100000
    expected_new_traces_per_sec: 5000
    policy_processors:
      # Invariant 1: Preserve 100% of Error Traces
      - name: drop-or-keep-errors
        type: status_code
        status_code: { status_codes: [ ERROR ] }

      # Invariant 2: Preserve 100% of SLO Latency Violations (> 1200ms)
      - name: preserve-slo-latency-violations
        type: latency
        latency: { threshold_ms: 1200 }

      # Invariant 3: Drop high-frequency internal synthetic endpoints
      - name: drop-healthchecks
        type: string_attribute
        string_attribute:
          key: http.target
          values: [ "/healthz", "/livez", "/readyz", "/metrics" ]
          enabled_regex_matching: false
          invert_match: true

      # Invariant 4: Probabilistic sample on remaining nominal traffic
      - name: nominal-traffic-quota
        type: probabilistic
        probabilistic: { sampling_percentage: 1.0 }

  batch:
    send_batch_size: 8192
    timeout: 5s

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

Recommended MCP Servers (mcp-serverlist.com)

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

Kubernetes Resource Manager

Inspects running OpenTelemetry Collector deployments, ConfigMaps, and memory usage metrics within Kubernetes clusters.

Recommended Agent Skills (askills.dev)

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

OpenTelemetry Config Validator

Validates syntax, pipeline ordering, and component configurations for OpenTelemetry Collector core and contrib manifests.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Collector Tail-Sampling Latency Guardrail Quotas

OpenTelemetry Collector Tail-Sampling Latency Guardrail Quotas defines an industrial-grade behavioral standard for devops engineering. Configures OpenTelemetry Collector tail-sampling pipelines to capture 100% of SLO-breaching latencies and unhandled errors while strictly enforcing deterministic downsampling and rate-limiting on high-frequency nominal traffic. Prevents catastrophic cloud observability ingestion cost overruns without creating blind spots in high-percentile latency distributions. 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: Naive Head-Sampling and Unbounded Tail-Sampling Causing Budget Depletion or Missed P99 Anomalies 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	Naive Head-Sampling and Unbounded Tail-Sampling Causing Budget Depletion or Missed P99 Anomalies	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

Collectors MUST position the 'memory_limiter' processor BEFORE the 'tail_sampling' processor in the pipeline to prevent Out-Of-Memory (OOM) kills during trace buffering.

Collectors MUST position the 'memory_limiter' processor BEFORE the 'tail_sampling' processor in the pipeline to prevent Out-Of-Memory (OOM) kills during trace buffering.

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

The 'tail_sampling' configuration MUST include an inverted filter or drop policy for routine synthetic traffic (e.g., /healthz, /ready, metrics scrapes) prior to probabilistic evaluation.

The 'tail_sampling' configuration MUST include an inverted filter or drop policy for routine synthetic traffic (e.g., /healthz, /ready, metrics scrapes) prior to probabilistic evaluation.

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

Pipelines MUST guarantee 100% sampling for traces containing span status 'STATUS_CODE_ERROR' or unhandled exceptions.

Pipelines MUST guarantee 100% sampling for traces containing span status 'STATUS_CODE_ERROR' or unhandled exceptions.

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 MUST guarantee 100% sampling for traces exceeding the defined SLO latency threshold (e.g., threshold_ms

Pipelines MUST guarantee 100% sampling for traces exceeding the defined SLO latency threshold (e.g., threshold_ms: 1500) using the 'numeric_attribute' or 'latency' filter.

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

Nominal traffic that conforms to latency SLOs MUST be governed by a composite or probabilistic sampler with a maximum rate quota to cap vendor ingestion budgets.

Nominal traffic that conforms to latency SLOs MUST be governed by a composite or probabilistic sampler with a maximum rate quota to cap vendor ingestion budgets.

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

Collectors MUST specify 'expected_new_traces_per_sec' and 'decision_wait' parameters calibrated against maximum expected P99 duration and batch memory limits.

Collectors MUST specify 'expected_new_traces_per_sec' and 'decision_wait' parameters calibrated against maximum expected P99 duration and batch memory limits.

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 Collector Tail-Sampling Latency Guardrail Quotas critical for AI coding assistants?

Configures OpenTelemetry Collector tail-sampling pipelines to capture 100% of SLO-breaching latencies and unhandled errors while strictly enforcing deterministic downsampling and rate-limiting on high-frequency nominal traffic. Prevents catastrophic cloud observability ingestion cost overruns without creating blind spots in high-percentile latency distributions. 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 (Naive Head-Sampling and Unbounded Tail-Sampling Causing Budget Depletion or Missed P99 Anomalies) 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