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-continuous-profiling-otlp-standard

OpenTelemetry Continuous Profiling (OTLP/Profiles) Ingestion and Trace Correlation

Standardizes continuous CPU and memory profiling ingestion utilizing eBPF-based low-overhead collection over native OTLP/Profiles (v1development). Mandates explicit trace-to-profile context propagation via thread/task registration or stack sampling to correlate trace latency outliers directly to line-level allocations and CPU cycles.

Prohibited Anti-Pattern: Uncorrelated Standalone Profilers or High-Overhead Runtime Hooks Without Trace Association

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenTelemetry Continuous Profiling (OTLP/Profiles) Ingestion and Trace Correlation - Standardizes continuous CPU and memory profiling ingestion utilizing eBPF-based low-overhead collection over native OTLP/Profiles (v1development). Mandates explicit trace-to-profile context propagation via thread/task registration or stack sampling to correlate trace latency outliers directly to line-level allocations and CPU cycles.
globs: **/otel-collector*.{yaml,yml}, **/profiling*.{ts,js,py,go,rs}, **/k8s/**/*.{yaml,yml}, **/instrumentation*.{ts,js,py,go,rs}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/opentelemetry-continuous-profiling-otlp-standard"
---

# OpenTelemetry Continuous Profiling (OTLP/Profiles) Ingestion and Trace Correlation

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Uncorrelated Standalone Profilers or High-Overhead Runtime Hooks Without Trace Association

## System Constraints
You are a Principal Observability and Infrastructure Architect enforcing OpenTelemetry Continuous Profiling standards. Enforce the utilization of native OTLP/Profiles endpoints, eBPF non-intrusive collection or low-overhead runtimes, and strict propagation of trace context (TraceId/SpanId) within profile samples. Reject proprietary agent silos, non-standard pprof HTTP polling without schema conformity, and unannotated stack traces.

## Strict Guidelines
- Engineers MUST ALWAYS configure OpenTelemetry Collector instances to accept profiles via the `otlp` receiver (`profiles: { protocols: { grpc: ... } }`) using the standard OTLP/Profiles data model.
- Engineers MUST NOT rely on synchronous runtime-hook pollers or intrusive in-process profilers with >1% CPU or memory throughput overhead in production.
- Profilers MUST inject active W3C `trace_id` and `span_id` context into profile sample labels/attributes to permit bidirectional trace-to-profile pivoting.
- Deployments MUST ensure eBPF profilers (such as Pyroscope eBPF or Beyla) have host Linux kernel permissions (`CAP_SYS_ADMIN`, `CAP_BPF`, `CAP_PERFMON`) and access to host PID namespaces (`hostPID: true`) for accurate symbol resolution.
- Profiling pipelines MUST emit symbolicated or deferred-symbolication payloads containing explicit mapping table identifiers (build IDs / debuginfos) rather than raw unresolved hex memory addresses.

## Bad vs Good Implementations
### Configuring OTLP Profiles Ingestion and Client-Side Context Association

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to configure OTLP profiles ingestion. Profile samples sent via OTLP are dropped, breaking automated correlation between latency anomalies and code allocations.
```yaml
# Collector and Agent config missing OTLP profiles and trace correlation
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        # Missing 'profiles' receiver config; traces cannot correlate to samples

exporters:
  logging:
    verbosity: detailed

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [logging]
    # Missing profiles pipeline entirely
```

#### Production Standard (Correct)
> **Standard**: Correctly enables the native 'profiles' pipeline on the standard OTLP receiver and defines proper batching and memory-limiting processors for high-throughput profile streams.
```yaml
# Standardized OpenTelemetry Collector configuration for OTLP Profiles
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318

processors:
  batch:
    send_batch_size: 512
    timeout: 5s
  memory_limiter:
    check_interval: 1s
    limit_percentage: 75
    spike_limit_percentage: 20

exporters:
  otlp/storage:
    endpoint: profiling-backend.internal:4317
    tls:
      insecure: false

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlp/storage]
    profiles:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [otlp/storage]
```

### Application-Level Contextual Profiling Hook with Active Span Correlation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Directly writes standalone profiles to disk without exporting via OTLP or linking active TraceID and SpanID, causing severe I/O overhead and preventing latency correlation.
```typescript
// In-process manual CPU polling with no OpenTelemetry span correlation
import fs from 'fs';
import v8Profiler from 'v8-profiler-next';

export function startProfiling() {
  v8Profiler.startProfiling('cpu-profile', true);
  setInterval(() => {
    const profile = v8Profiler.stopProfiling('cpu-profile');
    profile.export((err, result) => {
      // Writing raw unassociated JSON/pprof to disk; no trace correlation or OTLP export
      if (!err && result) fs.writeFileSync('/tmp/profile.cpuprofile', result);
      profile.delete();
    });
    v8Profiler.startProfiling('cpu-profile', true);
  }, 60000);
}
```

#### Production Standard (Correct)
> **Standard**: Leverages continuous profiling client configured with dynamic span labels, attaching active W3C trace_id and span_id to runtime profile samples to guarantee seamless trace-to-profile pivoting.
```typescript
// OpenTelemetry-compliant continuous profiling integration linking trace context
import { trace } from '@opentelemetry/api';
import Pyroscope from '@pyroscope/nodejs';

export function initializeContinuousProfiling(): void {
  Pyroscope.init({
    serverAddress: process.env.OTEL_EXPORTER_OTLP_PROFILES_ENDPOINT || 'http://otel-collector.observability:4040',
    appName: process.env.OTEL_SERVICE_NAME || 'payment-service',
    tags: {
      env: process.env.NODE_ENV || 'production',
      service_version: process.env.SERVICE_VERSION || '1.0.0'
    }
  });

  Pyroscope.start();
}

export async function profileWork<T>(name: string, fn: () => Promise<T>): Promise<T> {
  const activeSpan = trace.getActiveSpan();
  const spanContext = activeSpan?.spanContext();

  // Propagate trace and span IDs to the continuous profiling samples
  const labels: Record<string, string> = {
    action: name,
    ...(spanContext ? {
      trace_id: spanContext.traceId,
      span_id: spanContext.spanId
    } : {})
  };

  return Pyroscope.wrap(labels, async () => {
    return await fn();
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

OTel Collector Contrib MCP
Validation and schema inspector for OpenTelemetry Collector receivers, processors, and profile pipelines.
Recommended Agent Skills (askills.dev)

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

OpenTelemetry Collector Config Validator
CLI tool to validate collector configurations, component schemas, and OTLP pipeline invariants.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenTelemetry Continuous Profiling (OTLP/Profiles) Ingestion and Trace Correlation

OpenTelemetry Continuous Profiling (OTLP/Profiles) Ingestion and Trace Correlation defines an industrial-grade behavioral standard for devops engineering. Standardizes continuous CPU and memory profiling ingestion utilizing eBPF-based low-overhead collection over native OTLP/Profiles (v1development). Mandates explicit trace-to-profile context propagation via thread/task registration or stack sampling to correlate trace latency outliers directly to line-level allocations and CPU cycles. 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: Uncorrelated Standalone Profilers or High-Overhead Runtime Hooks Without Trace Association 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 DriftUncorrelated Standalone Profilers or High-Overhead Runtime Hooks Without Trace AssociationCritical
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 OpenTelemetry Collector instances to accept profiles via the `otlp` receiver (`profiles

Engineers MUST ALWAYS configure OpenTelemetry Collector instances to accept profiles via the `otlp` receiver (`profiles: { protocols: { grpc: ... } }`) using the standard OTLP/Profiles data model.

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 synchronous runtime-hook pollers or intrusive in-process profilers with >1% CPU or memory throughput overhead in production.

Engineers MUST NOT rely on synchronous runtime-hook pollers or intrusive in-process profilers with >1% CPU or memory throughput overhead in production.

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

Profilers MUST inject active W3C `trace_id` and `span_id` context into profile sample labels/attributes to permit bidirectional trace-to-profile pivoting.

Profilers MUST inject active W3C `trace_id` and `span_id` context into profile sample labels/attributes to permit bidirectional trace-to-profile pivoting.

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

Deployments MUST ensure eBPF profilers (such as Pyroscope eBPF or Beyla) have host Linux kernel permissions (`CAP_SYS_ADMIN`, `CAP_BPF`, `CAP_PERFMON`) and access to host PID namespaces (`hostPID

Deployments MUST ensure eBPF profilers (such as Pyroscope eBPF or Beyla) have host Linux kernel permissions (`CAP_SYS_ADMIN`, `CAP_BPF`, `CAP_PERFMON`) and access to host PID namespaces (`hostPID: true`) for accurate symbol resolution.

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

Profiling pipelines MUST emit symbolicated or deferred-symbolication payloads containing explicit mapping table identifiers (build IDs / debuginfos) rather than raw unresolved hex memory addresses.

Profiling pipelines MUST emit symbolicated or deferred-symbolication payloads containing explicit mapping table identifiers (build IDs / debuginfos) rather than raw unresolved hex memory addresses.

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 Continuous Profiling (OTLP/Profiles) Ingestion and Trace Correlation critical for AI coding assistants?

Standardizes continuous CPU and memory profiling ingestion utilizing eBPF-based low-overhead collection over native OTLP/Profiles (v1development). Mandates explicit trace-to-profile context propagation via thread/task registration or stack sampling to correlate trace latency outliers directly to line-level allocations and CPU cycles. 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 (Uncorrelated Standalone Profilers or High-Overhead Runtime Hooks Without Trace Association) 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