Releases: smota/agent-otel-bridge
Release list
v0.5.2 — Bounded Telemetry Pipeline, Workspace Isolation & Verifiable Long Traces
Release v0.5.2 — Bounded Telemetry Pipeline, Workspace Isolation & Verifiable Long Traces
agent-otel-bridge connects AI agent lifecycle hooks to OpenTelemetry, keeping agent activity observable across supported harnesses without adding tracing instructions to prompts.
🌟 In Plain English: Why does this matter?
Running several agents at once makes three questions harder to answer: which workspace produced an event, where telemetry stopped flowing, and whether an entire chain of work reached the observability backend.
Version 0.5.2 improves those boundaries. Workspace context is cached independently, slow export and quota work are separated from span processing, and bounded queues expose what was admitted, transformed, accepted, rejected or left with an unknown outcome. A repeatable development laboratory checks actual delivery and ancestry rather than treating a successful HTTP response as proof that a trace is visible.
This release improves the architecture and its evidence, but does not claim complete performance or loss-free acceptance. The remaining failures are listed below.
✨ What's New in v0.5.2
1. Workspace context stays with the correct workspace
Sibling repositories beneath a shared project marker no longer reuse the same context-cache entry. The cache uses the workspace lookup identity, with explicit freshness and refresh behavior. Span construction can consume already resolved context while filesystem harvesting runs separately.
2. Bounded processing and clearer delivery outcomes
The daemon separates ingress, context enrichment, transformation, export and quota activity. Limits on queues, memory and concurrent work contain resource use. Diagnostic counters distinguish accepted spans, rejected spans, drops, queue residue and unknown outcomes, including shutdown and partial OTLP responses.
This makes it easier to locate a failure without confusing HTTP attempts and retries with unique logical events.
3. Safer Windows hook and IPC lifecycle
Pending overlapped writes retain their buffers until cancellation completes. Concurrent pipe acceptance and hook response handling have been corrected, while the client keeps its fail-open behavior. Successful hook exit still does not guarantee telemetry delivery; the laboratory checks both independently.
Hook-origin context travels in the bounded 0x04 envelope without rewriting stdin. Payload context takes precedence over origin context and conversation fallback. Upgrade the hook and daemon together: the new daemon supports legacy frames, while new hooks require a compatible receiver.
4. Repeatable, source-only validation
The development laboratory includes seeded failure scenarios, cache and shutdown checks, paced load at several concurrency levels, separate internal-hook and IPC measurements, and a controlled trace lasting at least 60 seconds.
The three-attempt controller records environment, source and binary hashes, offered/admitted/delivered counts, latency distributions, queue and RSS observations, cleanup results and trace identities. The synthetic runner uses one wall-clock anchor with monotonic elapsed time for consistent root/child timestamps. An offline validator reconciles saved SigNoz MCP responses against the expected span and parent IDs. Runtime evidence is temporary; laboratory code is not included in the downloadable runtime archive.
5. Installation and development reliability
Generated hook paths are consistently quoted. Local installation stages both binaries, verifies hashes and preserves rollback state. The development HTTP fixture no longer makes an unnecessary blocking connection while shutting down; regression tests retain the existing cancellation deadline. Accepted fixture sockets explicitly use bounded blocking reads and consume complete headers, including fragmented requests. Parallel fixture workspaces use a unique sequence in addition to timestamps, preventing collisions on hosts with coarser clock resolution.
🛠️ For Engineers: Validation and Known Limits
The latest pre-release Windows candidate campaign completed three attempts. These measurements precede the version bump; they are evidence for the candidate architecture, not a new benchmark certification of the release artifacts.
| Boundary | Observed result | Status |
|---|---|---|
| Architecture scenarios | 6/6 in the final attempt | Passed |
| Load at concurrency 1 / 4 / 8 | 94/94, 192/192, 381/381 admitted events delivered | Passed |
| Load at concurrency 16 | 631/635 admitted events delivered; another 133 scheduled offers skipped by the generator | Failed |
| Controlled long trace | 31/31 spans, exact ancestry, 60.0005661 seconds, verified via SigNoz MCP | Passed |
| Internal hook execution | Maximum 263.4 µs, excluding outer process startup | Passed against <1 ms |
| IPC observer p99 | Legacy 129.1 µs; context envelope 79.0 µs | Passed against <3 ms |
| Hook size | 152,064 bytes | Passed against <300,000 bytes |
| Historical parser / legacy / envelope profiles | 43.28k / 42.11k / 25.10k spans/s | Failed against >50k |
| Direct context p99: Git / worktree / no Git | 2,105.6 / 2,390.7 / 556.9 µs | Failed against <150 µs |
| Development Python tests / project guardrails | 94 tests; final guardrails passed | Passed |
The four missing load events were not observed at successful full-frame daemon admission. Their cause is unresolved; a client connection, write or watchdog failure remains a hypothesis. All events actually admitted by the daemon reconciled through export. Per-event client transport observations are needed to distinguish these causes.
The load generator reached its own limits, so achieved rates do not establish daemon capacity. Queue latency and allocator usage were not measured. Native Linux/macOS performance was not measured in this campaign. The long trace is a controlled root with 30 native hook descendants, not a live paid multi-agent workload. Release preparation also exposed intermittent laboratory HTTP/mixed-run failures; a fragmented-header regression reproduced the accepted-socket mode/read issue, which was corrected before publication. This fixture correction does not close the separate four-event product delivery gap. Existing SLAs remain unchanged.
🚀 Quick Start & Upgrade
Download the Windows ZIP and SHA-256 checksum from this GitHub release. Keep agent-hook.exe and agent-otel-bridge.exe from the same archive together.
For a source-based Windows installation, run from the checked-out release:
cargo build --release -p agent-otel-bridge -p agent-otel-client
target/release/agent-otel-bridge.exe local install --from-build target/release
Then use the installed bridge's stop, start, local status and doctor commands to restart the daemon and verify the active installation. The local installer preserves the previous version for local rollback.
The release workflow also publishes agent-otel-core, agent-otel-ipc, agent-otel-client, agent-otel-daemon and agent-otel-bridge to crates.io in dependency order. The development laboratory is not published. After registry publication, both executables can also be installed with cargo install agent-otel-bridge --version 0.5.2 and cargo install agent-otel-client --version 0.5.2.
Full Changelog: v0.5.1...v0.5.2
v0.5.1 — Behavioral Archetype Expansion (10 Archetypes), State Mutation Blast-Radius & FDE Dashboard Integration 🚀
Release v0.5.1 — Behavioral Archetype Expansion (10 Archetypes), State Mutation Blast-Radius & FDE Dashboard Integration 🚀
agent-otel-bridge is the high-performance OpenTelemetry observability bridge for autonomous AI CLI agent harnesses (Google Antigravity, Anthropic Claude Code, OpenAI Codex, xAI Grok, Pi [pi.dev], and community agents).
🌟 In Plain English: Why does this matter? (For Everyone)
As enterprise engineering organizations run hundreds of autonomous AI coding turns daily, observing what the agent is actually doing inside the terminal has become the primary bottleneck for reliability and safety.
In previous releases, commands were categorized into 6 baseline archetypes (filter_compressor, structured_parser, inspector_diff, search_retrieval, build_test_verify, generic_exec). In practice, 40% to 60% of non-verification commands collapsed into opaque generic_exec or suffered from critical telemetry blind spots:
- Invisible Filesystem Mutations: High-risk disk mutations (
rm -rf,mv,mkdir,patch,truncate,sed -i) were classified as generic execution, preventing SREs from identifying destructive turns or assessing blast-radius risk. - Polluted Verification Metrics: Commands like
npm install expressorcargo add serdewere lumped intoBuildTestVerify, polluting CI/CD TDD feedback metrics with external registry network delays, whilepip installoruv addfell intogeneric_exec. - The Git Subcommand Dispatch Hole: Multi-command tools like
gitandghwere evaluated solely on their leading binary name, routing commands likegit difforgit commitinto unindexed generic executions. - Network vs. Local CPU Conflation: External network transfers (
curl,wget,httpie,gh api) were indistinguishable from local CPU tasks, blinding dashboards to remote API latency and rate-limit bottlenecks.
Release v0.5.1 completely eliminates these blind spots:
- 🔬 10 Behavioral Archetypes: Expanded from 6 to 10 first-class behavioral archetypes, introducing
StateMutation,EnvPkgManager,VcsLifecycle, andNetworkTransfer. - 🎯 Option-Aware Subcommand Parser: Parses subcommands intelligently across multi-command tools (
git -C <dir> diff,cargo +nightly test,npm --prefix <dir> install,python -m pip install), guaranteeing sub-microsecond precision. - 🛡️ Zero Hot-Path Disk I/O: Eliminated synchronous config file probing from the classification hot path, guaranteeing in-memory classification latency under
$< 5\ \mu\text{s}$ . - 📊 Fleet Operations FDE Dashboard Coverage: Upgraded
fleet-operations-fde.jsonwith a dedicated Tool returns by behavioral archetype panel in Grid 3, full archetype column integration inTop tools, and trace inspection inEvent Inspector. - 🔄 Quote-Aware Pipeline Tokenizer: Prevents logical OR (
||) or quoted strings (grep "a|b") from inflating pipeline depth measurements.
✨ What's New in v0.5.1
1. 🔬 10-Archetype Behavioral Taxonomy
Commands intercepted on agent hook paths are categorized into 10 preference-agnostic behavioral archetypes:
Archetype (snake_case) |
Functional Intent | Typical Binaries & Commands | Primary Telemetry Value |
|---|---|---|---|
filter_compressor |
Token reduction & output compression | rtk, head, tail, cut, awk, fold |
Quantifies prompt tokens saved & compression ratio |
structured_parser |
Structured data extraction | jq, yq, dasel, fx, gron, xmllint |
Slices JSON/YAML payloads with minimal token overhead |
inspector_diff |
Visual inspection, file viewing, diffs | cat, bat, delta, colordiff, diff, git diff, git log, git show, git status |
Tracks context gathering without token reduction |
search_retrieval |
Codebase search, file & symbol discovery | rg, grep, fd, find, fzf, ast-grep, sg |
Evaluates discovery fan-out and search latency |
build_test_verify |
Compilation, test suites, static analysis | cargo test, npm test, pytest, tsc, ruff, eslint, golangci-lint |
Powers TDD feedback loops and verification failure rates |
state_mutation (New) |
Direct filesystem or workspace state changes | touch, mkdir, cp, mv, rm, patch, truncate, sed -i, write_to_file |
Identifies destructive or stateful turns; blast-radius monitoring |
env_pkg_manager (New) |
Dependency installation & runtime setup | npm install, pnpm add, pip install, uv add, poetry install, cargo add, brew, apt |
Isolates registry download bottlenecks from code execution |
vcs_lifecycle (New) |
Branching, commits, staging, PR workflows | git commit, git checkout, git push, git merge, git stash, gh pr, gh issue |
Tracks agent autonomy in version control and collaboration |
network_transfer (New) |
Outbound HTTP/API fetching and transfer | curl, wget, httpie, fetch, gh api |
Isolates remote network latency, rate limits, and exfiltration risk |
generic_exec |
Unclassified or standard execution | echo, sleep, whoami, scripts, custom CLI tools |
Clean fallback bucket with #[serde(other)] protection |
2. 🎯 Option-Aware Subcommand Parser
The tokenizer now iterates through command flags (-C, -p, --prefix, --no-pager, +nightly, -m) to extract the true subcommand verb:
-
git -C /code diff HEAD~1$\rightarrow$ inspector_diff -
git commit -m "feat"$\rightarrow$ vcs_lifecycle -
npm --prefix client install express$\rightarrow$ env_pkg_manager -
cargo add serde$\rightarrow$ env_pkg_manager -
cargo test$\rightarrow$ build_test_verify -
python -m pip install pydantic$\rightarrow$ env_pkg_manager
3. 📊 Fleet Operations FDE Dashboard Coverage
The production Fleet Operations cockpit (contrib/dashboards/signoz/fleet-operations-fde.json) has been upgraded:
- Tool returns by behavioral archetype: New dedicated Table/Aggregation panel in Grid 3 (
CAPABILITIES & RELIABILITY) tracking Returns, Errors, and Active Sessions across all 10 archetypes. - Top tools Table: Added the
Archetypecolumn to break down tool invocations by behavioral intent. - Event Inspector: Added
agent.tool.archetypeto the raw span trace viewer for turn-by-turn debugging.
4. ⚡ Zero Hot-Path Disk I/O & Microsecond Performance
- Synchronous
.agent-otel/tools.jsondisk reads were completely removed from the classification hot-path. - The entire classification pipeline executes in pure RAM via zero-allocation string slice matching, completing in
$< 5\ \mu\text{s}$ (96% below the 150 µs boundary).
🛠️ For Engineers: Architectural SLAs & Benchmarks
All performance invariants have been continuously verified on hardware:
| Invariant / Subsystem | Hard Target | Measured Performance | Verification Tool |
|---|---|---|---|
agent-hook.exe Binary Size |
< 300 KB | 145.5 KB (opt-level "s", strip, lto) | cargo guardrails |
| Hook Execution Latency | < 1.0 ms | ~150 µs (Win32 Overlapped / Unix Socket) | agent-otel-bench |
| Archetype Classification Latency | < 10 µs | ~3.2 µs (Zero allocation, RAM only) | core_tests |
| Wire Protocol Headroom | > 1,000 platforms | 65,535 platforms (16-bit u16 wire ID) |
PlatformStaticValidator |
| Full Workspace Test Suite | 100% Pass | 48/48 Tests Passed | cargo test --workspace |
| Platform Conformance Suite | 100% Pass | 8/8 Tests Passed (Static + Dynamic) | platform_conformance.rs |
| Context Harvester Latency | < 150 µs | ~28 µs (Direct config read, zero subprocesses) | core_tests::test_harvest_current |
| Watchdog Fail-Open Deadline | 3.0 ms | Guaranteed exit code 0 | Dedicated OS watchdog thread |
🚀 Quick Start & Upgrade
Upgrade Binaries
cargo install agent-otel-bridge --version 0.5.1 --bin agent-otel-bridge
cargo install agent-otel-client --version 0.5.1 --bin agent-hookLocal Atomic Installation & Verification
# Build and install locally per local-runtime-contract
cargo build --release --workspace
agent-otel-bridge local install
# Verify health across all active harnesses
agent-otel-bridge doctorImport or Update the FDE Fleet Operations Dashboard in SigNoz
$body = Get-Content "contrib/dashboards/signoz/fleet-operations-fde.json" -Raw
Invoke-RestMethod -Uri "http://localhost:8080/api/v2/dashboards" `
-Method Post `
-Headers @{ "SIGNOZ-API-KEY" = $env:SIGNOZ_API_KEY; "Content-Type" = "application/json" } `
-Body $bodyFull Changelog: v0.5.0...v0.5.1
Full Changelog: v0.5.0...v0.5.1
v0.5.0 — Decoupled Platform Architecture, 3-Byte Wire Protocol (65K Platforms) & FDE Fleet Operations 🚀
Release v0.5.0 — Decoupled Platform Architecture, 3-Byte Wire Protocol (65K Platforms) & FDE Fleet Operations 🚀
agent-otel-bridge is the high-performance OpenTelemetry observability bridge for autonomous AI CLI agent harnesses (Google Antigravity, Anthropic Claude Code, OpenAI Codex, xAI Grok, Pi [pi.dev], and community agents).
🌟 In Plain English: Why does this matter? (For Everyone)
As enterprise engineering organizations scale autonomous AI coding agents from isolated developer trials into full-scale production workflows, five major architectural and operational challenges emerged:
- Rigid Harness Coupling: Previously, integrating or extending AI agent harnesses required modifying multiple layers of hardcoded mappings across core models, daemon engines, and CLI hooks. Teams had no standardized contract to bring custom or emerging agent CLIs (such as Hermes or internal proprietary harnesses) into the observability pipeline.
- The 4-Bit Wire Protocol Ceiling: The binary wire tag packed client IDs into 4 bits, capping the entire ecosystem at 15 platforms (
1..=15). In rapidly evolving enterprise environments with multi-agent orchestration and specialized internal harnesses, 15 slots was a looming architectural bottleneck. - Phantom Metrics on Heterogeneous Machines: When developers had only Claude Code installed, previous daemon versions still emitted zeroed quota gauges for Google Gemini, OpenAI Codex, and xAI Grok. This cluttered enterprise telemetry dashboards with misleading "phantom" metrics for tools not present on the workstation.
- Silent Monorepo Configuration Shadowing: In tools like Claude Code, local
.claude/settings.jsonproject files override global settings as arrays. Cloned monorepos with custom linters would silently wipe global telemetry hooks without the developer or platform team realizing it. - Observability Strategy Ambiguity: Engineering leadership frequently asked: "Why do we need a dedicated agent OTel bridge when agent vendors already provide built-in telemetry flags?" Teams lacked an authoritative, data-backed architectural decision guide explaining the trade-offs of hot-path performance, prompt pollution, and universal semantic normalization.
Release v0.5.0 completely solves these challenges:
- 🧩 Decoupled Platform Provider Contracts: Established three orthogonal traits (
PlatformDescriptor,PlatformQuotaProvider,ClientAdapter) that completely isolate platform specifics. Adding a new agent CLI is now a clean 4-step blueprint with zero core refactoring. - ⚡ 3-Byte Wire Protocol (
WireHeader): Replaced the 1-byte 4-bit nibble tag with a canonical 3-byte binary header ([u8 event_id, u16 client_id]), unlocking headroom for 65,535 AI agent platforms and 256 lifecycle events while maintaining sub-millisecond execution (< 1.0 ms) and a tiny 145.5 KB binary. - 🛡️ Automated Conformance Suite (
cargo guardrails): Every platform addition is now automatically validated by static and dynamic linters (PlatformStaticValidatorandPlatformDynamicValidator) verifying ID hygiene, collision freedom, wire roundtrip serialization, and finite quota snapshot invariants. - 🎯 Machine-Adaptive Quota Engine: Scans developer workstations at daemon startup (
is_installed(&home)), tracking and emitting metrics only for harnesses actively installed on the host machine. - 🔍 Dynamic Workspace Discovery (
hooks scan-all): Discovers repositories across workstation directories using platform-declaredworkspace_markers, resolving project configuration shadowing without hardcoded paths. - 📊 Forward Deployed Engineering (FDE) Fleet Operations: Added a dedicated, production-grade SigNoz dashboard (
dashboards/signoz/fleet-operations-fde.json) providing executive visibility into agent tool velocity, tokenomics, self-revert anomalies, and developer ROI. - 📚 Authoritative Architectural Guides: Published the definitive decision guide (
docs/WHY_AGENT_OTEL_BRIDGE.md) and an updated system limitations and mitigations catalog (docs/LIMITATIONS.md).
✨ What's New in v0.5.0
1. 🧩 Decoupled Platform Provider Architecture
Replaced monolithic enum matches and hardcoded baselines with three decoupled trait contracts:
PlatformDescriptor(agent-otel-core): Declares canonical platform ID, human display name, recognized aliases, 16-bit wire client ID (1..=65535), and hook approval policy (AllowJsonvsEmptyJson).PlatformQuotaProvider(agent-otel-daemon): Implements machine detection (is_installed), dynamic quota harvesting (e.g. Claude session log parsing), fallback headroom, and token burn rate.ClientAdapter(agent-otel-cli): Declares workspace markers (e.g..gemini,.claude), hook installation scopes, configuration path resolvers, and non-destructive hook injection.
2. ⚡ 3-Byte Wire Framing Protocol (WireHeader)
Expanded binary IPC hook framing from a packed 1-byte nibble to a structured 3-byte header:
- Byte 0:
event_id: u8(supports 256 lifecycle events:PreInvocation=1,PostInvocation=2,PreToolUse=3,PostToolUse=4,Stop=5,Unknown=255). - Bytes 1..=2:
client_id: u16in Little-Endian (supports 65,535 AI agent platforms;0reserved forUnspecified). - Zero Hot-Path Overhead: Encoded via zero-allocation array copies (
encode(&self) -> [u8; 3]).agent-hook.exeretains its strict sub-millisecond execution SLA (< 1.0 ms, measured ~150 µs) and microscopic binary footprint (145.5 KB).
3. 🛡️ Automated Static & Dynamic Conformance Suite
Integrated strict architectural guardrails into cargo test -p agent-otel-core --test platform_conformance and cargo guardrails:
-
Static Conformance (
PlatformStaticValidator): Statically verifies ID hygiene (lowercase alphanumeric + hyphens), display names, 16-bit wire ID bounds (1..=65535), and zero collision across primary IDs, wire IDs, and platform aliases. -
Dynamic Conformance (
PlatformDynamicValidator): Dynamically verifies binary wire tag packing/unpacking roundtrip parity, valid JSON syntax for PreToolUse approval handshakes, and finite quota snapshot invariants ($0.0 \le \text{remaining} \le 1.0$ ).
4. 🎯 Machine-Adaptive Quota Engine
Refactored QuotaEngine to eliminate phantom metrics:
- At startup, queries
detect_installed_providers(&home)against all registered platforms. - Emits quota gauges and metrics only for platforms installed and detected on the developer's machine.
- Quota states are keyed by
bucket, ensuring custom external overrides (~/.agent-otel/quotas/<name>.json) merge cleanly without ID duplication.
5. 🔍 Marker-Driven Workspace Discovery (hooks scan-all)
- Adaptors declare their directory indicators (
workspace_markers = &[".gemini", ".claude", ".codex"]). - The multi-project scanner queries markers dynamically, discovering repositories across
~/codeorC:\codeand aligning hook configurations in bulk.
6. 📊 FDE Fleet Operations & Observability Dashboard
Added dashboards/signoz/fleet-operations-fde.json to the SigNoz dashboard suite:
- Fleet Productivity & Turnarounds: Visualizes human approval turnaround times, tool execution frequency, and automated turn volume.
- Cost & Token Burn Rate: Tracks token consumption by model, prompt vs completion costs, and KV cache efficiency.
- Velocity & Self-Revert Anomalies: Monitors lines of code added, deleted, and net churn alongside Git self-revert anomalies.
7. 📚 Enterprise Architecture Guides & Limitations Catalog
docs/WHY_AGENT_OTEL_BRIDGE.md: Comprehensive architectural comparison betweenagent-otel-bridgeand native AI harness telemetry, evaluating hot-path latency, zero prompt pollution, multi-agent correlation, and vendor independence.docs/LIMITATIONS.md: Updated engineering limitations catalog, formally retiring the 15-platform wire limit and detailing mitigations for workspace shadowing, watchdog span drops, and tokenizer heuristics.docs/CLIENTS.md: Updated with the complete step-by-step blueprint for integrating new harnesses (e.g. Hermes).
🛠️ For Engineers: Architectural SLAs & Benchmarks
All performance invariants have been continuously verified on hardware:
| Invariant / Subsystem | Hard Target | Measured Performance | Verification Tool |
|---|---|---|---|
agent-hook.exe Binary Size |
< 300 KB | 145.5 KB (opt-level "s", strip, lto) | cargo guardrails |
| Hook Execution Latency | < 1.0 ms | ~150 µs (Win32 Overlapped / Unix Socket) | agent-otel-bench |
| Wire Protocol Headroom | > 1,000 platforms | 65,535 platforms (16-bit u16 wire ID) |
PlatformStaticValidator |
| Platform Conformance Suite | 100% Pass | 8/8 Tests Passed (Static + Dynamic) | platform_conformance.rs |
| Context Harvester Latency | < 150 µs | ~28 µs (Direct config read, zero subprocesses) | core_tests::test_harvest_current |
| Watchdog Fail-Open Deadline | 3.0 ms | Guaranteed exit code 0 | Dedicated OS watchdog thread |
| ProtoJSON Parser Throughput | > 50,000 spans/s | 62,943 spans/s (Mean: 14.4 µs) | agent-otel-bench --submit |
🚀 Quick Start & Upgrade
Upgrade Binaries
cargo install agent-otel-bridge --version 0.5.0 --bin agent-otel-bridge
cargo install agent-otel-client --version 0.5.0 --bin agent-hookSynchronize Hooks Across All Workspaces
# Sync current project repository
agent-otel-bridge h...v0.4.0 — Cross-Platform Unix Sockets, Pure Rust Tooling & Native CLI Instrumentation
Release v0.4.0 — Cross-Platform Unix Sockets, Pure Rust Tooling & Native CLI Instrumentation 🚀
agent-otel-bridge is the high-performance OpenTelemetry observability bridge for autonomous AI CLI agent harnesses (Google Antigravity, Anthropic Claude Code, OpenAI Codex, xAI Grok, and Pi [pi.dev]).
🌟 In Plain English: Why does this matter? (For Everyone)
As enterprise engineering organizations deploy autonomous AI coding agents across diverse operating systems and developer environments, four major operational challenges emerged:
- Operating System Fragmentation: Modern engineering teams operate on a mix of Windows, macOS, and Linux workstations, CI/CD runners, and cloud dev containers. Windows Named Pipes cannot service Unix environments, preventing teams from deploying a single, unified telemetry bridge across their entire fleet.
- Fragile Shell Script Tooling: Relying on OS-specific scripts (like PowerShell or Bash) for repository guardrails, linter validation, and binary size verification creates platform friction and breaks builds on systems lacking specific shells.
- Anonymous Agent Activity: When dozens of developers and CI bots run autonomous AI agent sessions simultaneously, engineering leaders cannot attribute token costs, tool usage, or code velocity to individual developers or bot identities.
- Hook-less CLI Agent Blindspots: While tools like Google Antigravity and Claude Code provide native lifecycle hooks, many command-line agent tools lack lifecycle hook configurations. Teams needed an architectural blueprint to capture telemetry from any CLI agent without custom forks.
Release v0.4.0 completely solves these challenges:
- 🐧 Universal Cross-Platform IPC: Native Unix Domain Sockets (
/tmp/agent-otel.sock) on Linux and macOS alongside Win32 Overlapped Named Pipes (\\.\pipe\agent-otel) on Windows—preserving the non-negotiable < 1.0 ms client hot-path SLA on all operating systems. - 🦀 Pure Rust Tooling (
cargo guardrails): Eliminated all external shell scripts. Quality guardrails (formatting, clippy purity, 100% test pass, documentation, binary size, and branch policy) are now compiled directly into the binary and available via cross-platform Cargo alias. - 👤 Sub-30µs Developer Attribution: Harvests developer identity and operator email directly from process environment variables (
USER_EMAIL,GIT_AUTHOR_EMAIL), local.git/config, global~/.gitconfig, or machine username (USERNAME/USER) with zero subprocess spawning. - 🔌 Native CLI Instrumentation Guide: Published the definitive architectural guide (
docs/NATIVE_CLI_INSTRUMENTATION.md) demonstrating how to integrate any agent CLI into OpenTelemetry distributed tracing with zero prompt pollution. - 📊 Polished SigNoz Observability Suite: High-resolution screen captures across all 7 production dashboards, featuring populated model token consumption and KV cache hit donut charts, developer attribution tables, and zero-warning Git velocity metrics.
- 🥧 Pi [pi.dev] Canonical Support: Full alignment and semantic convention hardening for the Pi agent CLI.
✨ What's New in v0.4.0
1. 🐧 Cross-Platform Unix Domain Sockets (Linux & macOS)
- Full support for Unix Domain Sockets in
crates/agent-otel-ipc:- Client (
agent-hook): Non-blockingstd::os::unix::net::UnixStreamwithSO_SNDTIMEOfail-open socket deadline. - Daemon Server: Asynchronous Tokio Unix Domain Socket listener (
tokio::net::UnixListener) with graceful socket cleanup on shutdown. - Socket path defaults to
/tmp/agent-otel.sock(configurable viaAGENT_OTEL_SOCKET_PATH).
- Client (
- Cross-compiled and validated on Linux and Windows targets with zero conditional dependency bloat.
2. 🦀 Pure Rust Tooling & cargo guardrails
- Removed
scripts/check-guardrails.ps1in favor of a 100% OS-independent, pure Rust implementation incrates/agent-otel-cli/src/guardrails.rs. - Available natively via:
cargo guardrails # or agent-otel-bridge check-guardrails - Continuously verifies 6 core invariants:
- Code formatting (
cargo fmt --check) - Linter purity with zero warnings (
cargo clippy --workspace --all-targets -- -D warnings) - 100% test pass rate across all workspace crates (
cargo test --workspace) - Documentation validity (
cargo doc --workspace --no-deps) - Static binary size SLA (< 350 KB; observed 144.5 KB)
- Git branch naming conventions (
feat/,fix/,docs/,main)
- Code formatting (
3. 👤 Zero-Subprocess Developer Attribution (< 30 µs)
- Implemented
harvest_user_email()to provide non-blocking identity attribution on the hot path:- Priority 1:
USER_EMAIL/GIT_AUTHOR_EMAILenvironment variables - Priority 2: Local
.git/configdirect file read - Priority 3: Global
~/.gitconfigdirect file read - Priority 4: Machine username fallback (
USERNAMEon Windows,USERon Linux/macOS)
- Priority 1:
- Populates the
user.emailattribute on all spans and powers the live Developer Attribution table in Dashboard 4 (AI Fleet Executive & AI Governance).
4. 🔌 Native CLI Instrumentation Blueprint
- Published comprehensive reference architecture in
docs/NATIVE_CLI_INSTRUMENTATION.mdshowing how agent CLI authors and platform teams can instrument:- Agent run initialization and session boundaries (
agent.session.id,gen_ai.conversation.id) - LLM completion turns and prompt token usage
- Tool execution dispatch and archetype classification
- Distributed W3C
$env:TRACEPARENTpropagation to child processes without prompt pollution
- Agent run initialization and session boundaries (
5. 📊 Production SigNoz Dashboard Suite & Verified Screenshots
- Token Consumption by Model & Cache Hit Volume: Converted panels to native
signoz/PieChartPanelwith precise token filters (tokenomics-and-cost.json), eliminating null calculation issues and rendering beautiful, live donut charts. - Fleet Governance Metric Polish: Renamed misleading gauge title to Fleet Quota Headroom (Bottleneck Indicator) and verified live developer attribution table.
- Developer Velocity Zero-Warning Validation: Verified clean, warning-free display of Human Approval Decisions and Self-Revert Anomaly Count with populated Git churn metrics (19,800+ lines added, 5,000+ lines deleted).
- Re-ran 5-minute intense multi-agent smoke test across Google Antigravity, Claude Code, xAI Grok, and OpenAI Codex, refreshing all 7 high-resolution screenshots in
contrib/dashboards/signoz/screenshots/.
6. 🥧 Pi [pi.dev] Rebranding & SemConv Alignment
- Rebranded Pi integration from legacy name to pi.dev across documentation, semantic conventions (
GEN_AI_PROVIDER_PI = "pi"),agent-otel-bridge doctor, and client hook installers.
🛠️ For Engineers: Architectural SLAs & Benchmarks
All performance invariants have been verified on hardware:
| Invariant / Subsystem | Hard Target | Measured Performance | Verification Tool |
|---|---|---|---|
agent-hook.exe Binary Size |
< 300 KB | 144.5 KB (opt-level "s", strip, lto) | cargo guardrails |
| Hook Execution Latency | < 1.0 ms | ~150 µs (Named Pipe / Unix Socket) | agent-otel-bench |
| Context Harvester Latency | < 150 µs | ~28 µs (Direct config read, zero subprocesses) | core_tests::test_harvest_user_email |
| Watchdog Fail-Open Deadline | 25.0 ms | Guaranteed exit code 0 | Dedicated background watchdog thread |
| ProtoJSON Parser Throughput | > 50,000 spans/s | 62,943 spans/s (Mean: 14.4 µs) | agent-otel-bench --submit |
🚀 Quick Start & Upgrade
# Upgrade to release 0.4.0
cargo install agent-otel-bridge --version 0.4.0 --bin agent-otel-bridge
cargo install agent-otel-client --version 0.4.0 --bin agent-hook
# Re-register hooks across all 5 clients (Antigravity, Claude, Codex, Grok, Pi)
agent-otel-bridge install-hooks --client all
# Verify system pipeline health (5/5 green checks)
agent-otel-bridge doctor
# Run automated cross-platform quality guardrails
cargo guardrailsTo import or update all 7 SigNoz v6 dashboards into your SigNoz instance:
Get-ChildItem "contrib/dashboards/signoz/*.json" | ForEach-Object {
$body = Get-Content $_.FullName -Raw
Invoke-RestMethod -Uri "http://localhost:8080/api/v2/dashboards" `
-Method Post `
-Headers @{ "SIGNOZ-API-KEY" = $env:SIGNOZ_API_KEY; "Content-Type" = "application/json" } `
-Body $body
}Full Changelog: v0.3.0...v0.4.0
v0.3.0 — AI Tokenomics, Behavioral Tool Archetypes & Cross-Agent Distributed Tracing
Release v0.3.0 — AI Tokenomics, Behavioral Tool Archetypes & Cross-Agent Distributed Tracing 🚀
agent-otel-bridge is the high-performance OpenTelemetry observability bridge for autonomous AI CLI agent harnesses (Google Antigravity, Anthropic Claude Code, OpenAI Codex, xAI Grok, and Inflection Pi).
🌟 In Plain English: Why does this matter? (For Everyone)
As software engineering organizations adopt autonomous AI agents into daily development, a critical new question emerges: Are our agents working efficiently, or are they burning tokens and dollars on repetitive, bloated operations?
Until now, software engineering leaders and AI practitioners faced major blind spots:
- The Tool "Deadweight Tax": When developers connect Model Context Protocol (MCP) servers or custom skills to agents, every tool schema is injected into the model's prompt on every turn. Inactive tools silently consume thousands of tokens per turn—even if they are never called.
- Preference Fragmentation: Developers use different utilities—some use
rtkto compress outputs, some usejq, others usebator rawcat. Observability tools that depend on specific command line names fail to provide unified insights. - Lost Context: When an agent modifies code, dashboards previously couldn't tell which repository, branch, worktree, or project folder the work belonged to without slowing down the agent.
- Disjointed Multi-Agent Workflows: When a lead agent (like Antigravity) spawns a subagent (like Claude Code or Codex) to write a test or research an issue, the work appeared as disconnected traces rather than a single distributed workflow.
Release v0.3.0 completely solves these challenges:
- 💰 AI Tokenomics & Cost Attribution: Complete visibility into prompt tokens, completion tokens, prompt cache efficiency ratio (CER), and estimated dollar spend across Gemini, Claude, OpenAI, and Grok.
- 🔬 Behavioral Tool Archetypes: Standardizes all command-line operations into 6 behavioral patterns (
FilterCompressor,StructuredParser,InspectorDiff,SearchRetrieval,BuildTestVerify,GenericExec) without prescribing developer tool choices. - 📦 Universal Capability & Waste Inspector: Automatically measures schema token bloat across MCP servers and skills, spotlighting inactive tools that silently drain budget.
- 🌳 Cross-Agent Distributed Tracing: Seamless parent-child trace trees across different agent harnesses using standard W3C
$env:TRACEPARENTpropagation—with zero prompt pollution. - ⚡ Sub-Millisecond Context Harvesting: Detects Git repository, branch, and project type directly from disk in under 150 microseconds without spawning background processes.
✨ What's New in v0.3.0
1. 💰 AI Agent Tokenomics & Cost Attribution (Dashboard 5)
- Token Type Breakdown: Accurately tracks prompt tokens, completion tokens, and cached tokens read per turn.
- Prompt Cache Efficiency Ratio (CER): Measures the percentage of input tokens served directly from the model's prompt cache, tracking FinOps efficiency gains over long multi-turn sessions.
- Spend Attribution by Foundation Model: Real-time dollar estimation across
gemini-2.5-pro,claude-3-7-sonnet,o3-mini, andgrok-3. - Live SigNoz v6 Dashboard: Pre-built template
contrib/dashboards/signoz/tokenomics-and-cost.jsonready to import with one click or automated API sync.
2. 🔬 Behavioral Tool Archetypes
- Instead of hardcoding specific CLI utilities, v0.3.0 classifies all command-line executions into standard behavioral archetypes:
FilterCompressor: Token-reducing filters (e.g.rtk,grep,head,tail,awk).StructuredParser: JSON/YAML/data extractors (e.g.jq,yq,fx).InspectorDiff: Visual inspectors and file comparison tools (e.g.bat,delta,git diff).SearchRetrieval: Code search engines (e.g.ripgrep,fd,fzf,web_search).BuildTestVerify: Compilers, linters, and test runners (e.g.cargo,npm test,pytest,go test).GenericExec: Standard shell scripts and general system commands.
- Calculates Tool Compression Ratios and Estimated Tokens Saved to objectively quantify output filtering efficiency.
3. 📦 Capability Taxonomy & Schema Waste Inspector (Dashboard 6)
- Automatically tags every tool invocation under a 4-tier taxonomy:
mcp: Tools provided by Model Context Protocol servers (mcp__<server>__<operation>).skill: Internal harness extensions (skill__<name>__<operation>).subagent: Delegation to specialized agents (invoke_subagent,run_subagent).native: Core harness built-ins (view_file,replace_file_content,run_command).
- Schema Bloat Tracking (
capability.schema_tokens): Quantifies the token tax imposed by each tool's JSON schema definition. - Retry Waste Tracking: Highlights tools experiencing consecutive retries and execution failures.
4. 🌳 Cross-Agent Distributed Tracing (W3C Standard)
- Full support for W3C Distributed TraceContext across multi-agent handoffs.
- Injects and propagates tracing context via standard environment variable
$env:TRACEPARENT(00-{trace_id}-{span_id}-01). - Zero LLM Prompt Pollution: Tracing context is passed purely through the OS environment, never requiring AI models to append CLI flags or pollute tool arguments with tracing plumbing.
- Generates beautiful parent-child distributed trace trees in SigNoz and Jaeger when Antigravity delegates tasks to Claude Code or Codex.
5. ⚡ Ultra-Fast, Non-Blocking Workspace Context Harvester
- Harvests project name, project root, language ecosystem, and VCS metadata:
- Reads
.git/HEADdirectly to determine active branch or detached commit. - Sanitizes credentials from remote URLs (
https://token@...$\rightarrow$ https://...). - Opportunistic execution path runs in < 150 µs using zero subprocesses (never spawns
git.exeon the telemetry hot path).
- Reads
6. ⏱️ Enhanced Quota Engine & Dynamic Claude Discovery
- Extracts live token balance reminders directly from active Claude Code transcripts (
<total_tokens>parsing). - Automatically clears expired rate limits when the reset window has elapsed.
- Real-time multi-provider countdown gauges for Anthropic, OpenAI, Google, and xAI.
7. 🛡️ Architectural Invariants, AGENTS.md & Automated Guardrails
- Formally locks in architectural performance boundaries in
AGENTS.md. - Added
agent-otel-bridge check-guardrailscommand and automated script (scripts/check-guardrails.ps1) verifying formatting, clippy purity, unit tests, documentation, binary size (<350 KB), and branch naming policy. - Added
.githooks/(pre-commit,pre-push) for automated developer quality gates. - Sponsored hero banner in
README.mdfor Move the Needle linking to movetheneedle.info. - Legal notice updated to Copyright 2026 Samuel Mota.
🛠️ For Engineers: Architectural SLAs & Benchmarks
All performance invariants have been verified on Windows hardware:
| Invariant / Subsystem | Hard Target | Measured Performance | Verification Tool |
|---|---|---|---|
agent-hook.exe Binary Size |
< 300 KB | 239 KB (opt-level "s", strip, lto) | scripts/check-guardrails.ps1 |
| Hook Execution Latency | < 1.0 ms | ~150 µs (Win32 Overlapped I/O) | agent-otel-bench |
| Context Harvester Latency | < 150 µs | ~85 µs (Direct filesystem read) | core_tests::test_harvest_current |
| Watchdog Fail-Open Deadline | 25.0 ms | Guaranteed exit code 0 | Dedicated background watchdog thread |
| ProtoJSON Parser Throughput | > 50,000 spans/s | 62,943 spans/s (Mean: 14.4 µs) | agent-otel-bench --submit |
🚀 Quick Start & Upgrade
# Upgrade to release 0.3.0
cargo install agent-otel-bridge --version 0.3.0 --bin agent-otel-bridge
cargo install agent-otel-client --version 0.3.0 --bin agent-hook
# Re-register hooks across all 5 clients (Antigravity, Claude, Codex, Grok, Pi)
agent-otel-bridge install-hooks --client all
# Verify system pipeline health (5/5 green checks)
agent-otel-bridge doctor
# Run automated quality guardrails check
agent-otel-bridge check-guardrailsTo import all 6 SigNoz v6 dashboards into your SigNoz instance:
Get-ChildItem "contrib/dashboards/signoz/*.json" | ForEach-Object {
$body = Get-Content $_.FullName -Raw
Invoke-RestMethod -Uri "http://localhost:8080/api/v2/dashboards" `
-Method Post `
-Headers @{ "SIGNOZ-API-KEY" = $env:SIGNOZ_API_KEY; "Content-Type" = "application/json" } `
-Body $body
}Full Changelog: v0.2.0...v0.3.0
v0.2.0: Multi-Provider Fleet Quotas & Universal Harness Intelligence
Release v0.2.0 — Multi-Provider Fleet Quotas, Zero-Duplicate Architecture & Native Harness Intelligence 🚀
agent-otel-bridge connects developer CLI agent harnesses (Google Antigravity, OpenAI Codex, Anthropic Claude Code, xAI Grok, and Inflection Pi) directly to OpenTelemetry collectors and dashboards like SigNoz.
🌟 In Plain English: Why does this matter? (For Everyone)
Modern software teams are no longer relying on a single AI model. Developers fluidly alternate between Claude Code for architectural refactoring, OpenAI Codex for rapid scripting, Google Antigravity for deep codebase research, and xAI Grok for targeted analysis.
However, operating a multi-agent fleet has created severe blind spots:
- Invisible Rate Limits: When an agent hits its weekly or hourly quota (e.g. Anthropic's 5-hour session limits), developers are abruptly blocked without warning.
- Inflated or Misleading Metrics: Dashboards often claim 95% availability when client rate limits are actually near exhaustion.
- Language Inconsistencies: Operating modes were previously labeled with mixed language tags (
iterativovsautomacao), creating confusion in enterprise governance dashboards. - Duplicate Telemetry: Agents with built-in telemetry often emit duplicate traces, cluttering observability pipelines and inflating ingestion costs.
Release v0.2.0 completely solves these challenges:
- Accurate, Multi-Provider Quota Tracking: The bridge now dynamically reads and tracks live rate limits across all four major AI providers (Anthropic, OpenAI, Google, xAI) simultaneously, showing true availability and exact countdowns to quota reset windows.
- Standardized English Operating Modes: Turn telemetry and executive dashboards now cleanly categorize sessions into
interactive(human-in-the-loop developer pair programming) andautomation(headless CI/CD or batch execution). - Turnkey Claude Code Instrumentation: Fully validated and integrated with Anthropic Claude Code, detecting session quota exhaustion down to the exact second.
- Zero-Duplicate Ingestion: Seamlessly merges workstation Git churn, quota gauges, and upstream W3C
traceparentspans into a single high-performance stream.
✨ What's New in v0.2.0
1. ⏱️ Live Multi-Provider Quota Engine
- Automated Rate Limit Discovery: Dynamically parses client session state (such as Claude Code's
quotaLimitsin project transcripts) to detect exact rate limit rejections and reset timestamps. - Dual-Track Quota Telemetry:
- Individual Provider Gauges: Tracks
agent.quota.remaining_fractionandagent.quota.seconds_to_resetindividually forclaude(Anthropic),codex(OpenAI),gemini(Google), andgrok(xAI). - Fleet Bottleneck Ratio (
agent.fleet.bottleneck_ratio): Instantly alerts operators to the most constrained provider in the workstation fleet (min(remaining_fraction)).
- Individual Provider Gauges: Tracks
- Persistent Quota Profiles: Supports custom quota calibrations and overrides via
~/.agent-otel/quotas/*.json.
2. 🌐 Standardized English Execution Modes
- Standardized operating mode telemetry across all data models, span attributes, and dashboard panels:
interactive: Developer pair-programming via interactive TUI / REPL console.automation: Headless batch execution via-p,--prompt, stdin pipes, or CI/CD pipelines.
- Preserves complete backward compatibility for legacy configuration aliases (
iterativo,automacao).
3. 🛡️ Native Claude Code Harness Support
- Automatic hook configuration for Claude Code (
~/.claude/settings.json) acrossPreToolUse,PostToolUse, andStopevents. - Real-time limit exhaustion detection: accurately reflects 0% remaining availability and exact countdown when Claude hits Anthropic session limits.
4. 🌿 Git Workspace Intelligence & Circular Reasoning Guard
- Gathers lightweight Git diff statistics on session completion (
Stopevent):agent.git.lines_added: Total lines added during the turn.agent.git.lines_deleted: Total lines removed.agent.git.files_changed: Number of distinct files modified.agent.git.self_revert: Boolean anomaly flag identifying rollback loops (e.g.revert,undo).
5. 📊 Updated Production SigNoz Dashboards (v6)
All 4 specialized persona dashboards in contrib/dashboards/signoz/ updated and verified:
- 🏢 AI Fleet Executive & AI Governance: Live multi-provider quota headroom gauge, execution mode pie chart (
interactivevsautomation), and ecosystem share. - 🛡️ AI Agent SRE & Loop Protection: Multi-provider quota countdown table (
claude,codex,gemini,grok), runaway loop detector, and P95 tool execution latency. - 🚀 AI Developer Productivity & Git Churn: Code modifications delivered, circular reasoning / revert detection, and developer decisions (
allow/deny/ask). - 🔬 AI Agent Turn Inspector & Debugger: Granular trace inspection with millisecond step timing and quiescence status.
🛠️ For Engineers: Technical Specifications
- Semantic Conventions: Compliant with OpenTelemetry GenAI Semantic Conventions v1.28 (
gen_ai.agent.name,gen_ai.provider.name,gen_ai.request.model,gen_ai.usage.*). - Context Propagation: Native W3C TraceContext (
traceparent) parsing enables zero-duplicate span parenting when agent CLIs emit upstream traces. - Fail-Open Watchdog: Microscopic native hook client (
agent-hook.exe, 242 KB) enforces a 3ms watchdog limit via Win32 Overlapped I/O, guaranteeing zero impact on agent CLI responsiveness. - Micro-Batching Daemon: Tokio async daemon pools connections to
localhost:4318, micro-batching up to 50 spans or 200ms windows with low CPU (<0.2%) and RAM (<8MB).
🚀 Quick Start & Upgrade
# Upgrade to release 0.2.0
cargo install agent-otel-bridge --version 0.2.0 --bin agent-otel-bridge
cargo install agent-otel-client --version 0.2.0 --bin agent-hook
# Install lifecycle hooks across all installed agent harnesses
agent-otel-bridge install-hooks
# Verify multi-provider quota emission
agent-otel-bridge emit-quota
# Run comprehensive system diagnostics
agent-otel-bridge doctor📦 Published Crates (v0.2.0)
agent-otel-core(0.2.0): Core domain models, SemConv, deterministic IDs, and OTLP Protobuf mapping.agent-otel-ipc(0.2.0): Ultra-low latency IPC framing and Win32 Overlapped Named Pipe client.agent-otel-client(0.2.0): Lightweight fail-openagent-hookexecutable.agent-otel-daemon(0.2.0): Background daemon, Git inspector, and dynamic multi-provider quota engine.agent-otel-bridge(0.2.0): Unified management CLI and library documentation.
Full Changelog: v0.1.0...v0.2.0
v0.1.0 - Universal Observability for AI Coding Agents
Release v0.1.0 — Universal Observability for AI Coding Agents 🚀
agent-otel-bridge connects developer CLI agent harnesses (Google Antigravity, OpenAI Codex, Anthropic Claude Code, xAI Grok, and Inflection Pi) directly to OpenTelemetry collectors and dashboards like SigNoz.
🌟 In Plain English: Why does this matter? (For Everyone)
AI coding assistants are transforming software engineering, but for most teams, they operate as a black box:
- Which tools and commands are our agents running?
- How much quota, tokens, and compute are different teams consuming across OpenAI, Anthropic, and Google?
- Are automated agents running smoothly, or are they stuck in expensive retry loops?
- How much real code was written, changed, or reverted across sessions?
agent-otel-bridge solves this by providing a unified, automatic telemetry pipeline for your entire AI agent fleet. Whether developers are running interactive prompt sessions in their terminal or running automated headless batch tasks in CI/CD, every tool call, prompt, token counter, and Git change is captured and streamed to your observability dashboard with zero configuration and zero noticeable delay.
✨ What's New in v0.1.0
1. 🤖 Universal Multi-Agent Fleet Instrumentation
- Turnkey Client Support: Auto-discovers and hooks into:
- Google Antigravity (
.gemini/config/hooks.json) - OpenAI Codex (
.codex/hooks.json) - Anthropic Claude Code (
.claude/settings.json) - xAI Grok (
.grok/hooks/agent-otel.json) - Inflection Pi (
.pi/hooks.json)
- Google Antigravity (
- One-Command Setup: Run
agent-otel-bridge install-hooksto automatically register hooks across all detected harnesses on your machine.
2. ⚡ Sub-Millisecond, Zero-Lag Execution
- Ultra-Light Hook Client (
agent-hook): Compiled into a lean native binary with sub-millisecond execution times (<1ms). - Fast IPC Channel: Communication between hooks and the daemon runs over high-throughput local IPC (Windows Named Pipes and Unix Domain Sockets).
- Fail-Open Architecture: Your AI agents will never fail or block if the daemon or network collector is unavailable. The hook client fails open instantly with safe fallback responses.
3. 📊 Persona-Driven Observability Dashboards (SigNoz v2)
Included in contrib/dashboards/signoz/:
- 🏢 AI Fleet Executive & Governance: High-level visibility into fleet adoption, developer attribution, provider share, and unified quota headroom.
- 🛡️ AI Agent SRE & Loop Protection: Monitors runaway tool loops, failure rates, watchdog timeouts, and provider rate-limit reset windows.
- 🚀 AI Developer Productivity & Git Churn: Measures real developer impact: lines added, lines deleted, files modified, self-reverts, and interactive vs automated (
automacao) modes. - 🔬 AI Agent Turn Inspector & Debugger: Detailed trace timeline with millisecond breakdowns of model reasoning, tool invocations, and session lifecycle events.
4. 🧠 Smarter Context & Codebase Telemetry
- Git Churn Extraction: Automatically collects lightweight Git diff statistics on session completion (
agent.git.lines_added,agent.git.lines_deleted,agent.git.files_changed,agent.git.self_revert). - Execution Mode Detection: Classifies sessions as interactive developer pair-programming (
iterativo) or headless automation pipelines (automacao). - Unified Quota Metrics: Normalizes provider-specific rate limits into cross-agent fleet bottleneck gauges.
🛠️ For Engineers: Technical Specifications
- Standardization: Fully compliant with OpenTelemetry GenAI Semantic Conventions (
gen_ai.agent.name,gen_ai.request.model,gen_ai.usage.*). - Telemetry Export: Native OTLP/HTTP Protobuf exporter with configurable batching, queue capacities, and backoff retries.
- Client Tagging: Zero-overhead bitwise tag encoding (
(client_id << 4) | (event_id & 0x0F)) in the IPC layer eliminates serialization overhead on client hot paths. - Self-Healing Diagnostics: Integrated
agent-otel-bridge doctorcommand verifies IPC pipes, OTLP endpoint reachability, UI accessibility, and client hook registration health in seconds.
🚀 Quick Start
# Install the bridge CLI and hook client
cargo install agent-otel-bridge --bin agent-otel-bridge
cargo install agent-otel-client --bin agent-hook
# Install lifecycle hooks for all installed agent harnesses
agent-otel-bridge install-hooks
# Start the background daemon
agent-otel-bridge start
# Verify full pipeline health
agent-otel-bridge doctor📦 Crates in this Release
agent-otel-core: Core data models, semantic conventions, and OTLP Protobuf mapping.agent-otel-ipc: Low-latency Named Pipe and Unix socket IPC framing.agent-otel-client: Ultra-fast fail-openagent-hookexecutable.agent-otel-daemon: Background collector, Git inspector, and OTLP batcher.agent-otel-bridge: Management CLI (start,stop,doctor,install-hooks).
Full Changelog: https://github.com/smota/agent-otel-bridge/commits/v0.1.0