Architectural Invariant Design: OpenTelemetry GenAI Semantic Conventions and Streaming Backpressure Telemetry
OpenTelemetry GenAI Semantic Conventions and Streaming Backpressure Telemetry defines an industrial-grade behavioral standard for backend engineering. Standardizes OpenTelemetry GenAI semantic conventions across asynchronous LLM streaming pipelines to prevent distributed trace fragmentation and metrics drift. Enforces strict parent-child span linkage, time-to-first-token (TTFT) duration recording, prompt-injection guardrail span containment, and backpressure queue latency telemetry across reactive streams. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.
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 | Detached LLM Stream Tracing with Opaque Latency and Uninstrumented Backpressure | 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. |
Step-by-Step Production Directives
Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:
Engineers MUST ALWAYS use standard OpenTelemetry GenAI semantic conventions (`gen_ai.system`, `gen_ai.request.model`, `gen_ai.response.model`, `gen_ai.usage.input_tokens`, `gen_ai.usage.output_tokens`, `gen_ai.response.finish_reasons`).
Engineers MUST ALWAYS use standard OpenTelemetry GenAI semantic conventions (`gen_ai.system`, `gen_ai.request.model`, `gen_ai.response.model`, `gen_ai.usage.input_tokens`, `gen_ai.usage.output_tokens`, `gen_ai.response.finish_reasons`).
Engineers MUST NOT emit custom non-standard attributes like `prompt_tokens`, `model_name`, or `total_cost` in lieu of official OTel `gen_ai.*` attributes.
Engineers MUST NOT emit custom non-standard attributes like `prompt_tokens`, `model_name`, or `total_cost` in lieu of official OTel `gen_ai.*` attributes.
Pipelines MUST record Time-To-First-Token (TTFT) as a span event or attribute using monotonic high-resolution timestamps (`performance.now()`), calculating the delta between stream invocation and the first emitted byte/chunk.
Pipelines MUST record Time-To-First-Token (TTFT) as a span event or attribute using monotonic high-resolution timestamps (`performance.now()`), calculating the delta between stream invocation and the first emitted byte/chunk.
All guardrail, moderation, and prompt-injection detection checks MUST execute inside child spans contextualized directly under the active root GenAI operation span before or concurrently with stream initiation.
All guardrail, moderation, and prompt-injection detection checks MUST execute inside child spans contextualized directly under the active root GenAI operation span before or concurrently with stream initiation.
Streaming iterators MUST capture downstream backpressure latency by recording write-buffer saturation delays (`stream.write() === false` or `highWaterMark` stalls) as explicit trace events or histogram metrics.
Streaming iterators MUST capture downstream backpressure latency by recording write-buffer saturation delays (`stream.write() === false` or `highWaterMark` stalls) as explicit trace events or histogram metrics.
The root GenAI streaming span MUST NEVER close until the underlying iterator or `ReadableStream` fires its terminal event (`end`, `close`, or uncaught error), ensuring accurate span duration and total token usage counts.
The root GenAI streaming span MUST NEVER close until the underlying iterator or `ReadableStream` fires its terminal event (`end`, `close`, or uncaught error), ensuring accurate span duration and total token usage counts.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is OpenTelemetry GenAI Semantic Conventions and Streaming Backpressure Telemetry critical for AI coding assistants?
Standardizes OpenTelemetry GenAI semantic conventions across asynchronous LLM streaming pipelines to prevent distributed trace fragmentation and metrics drift. Enforces strict parent-child span linkage, time-to-first-token (TTFT) duration recording, prompt-injection guardrail span containment, and backpressure queue latency telemetry across reactive streams. 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 (Detached LLM Stream Tracing with Opaque Latency and Uninstrumented Backpressure) 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.