Reported by FleetQ as a P2 power feature. A --telemetry-otlp <endpoint> flag (or env var) emitting OpenTelemetry spans for each capability call (net.fetch, fs.read, …) with timing/byte counts.
Ask
Per-capability OpenTelemetry spans, exportable to any OTLP collector. FleetQ already runs a tenant-scoped collector and would surface Boruna's resource usage right next to LLM/agent spans in their UI without writing glue code.
Notes for implementers
- The
opentelemetry and opentelemetry-otlp crates are stable. Wire them at the CapabilityGateway::call boundary in crates/llmvm/src/capability_gateway.rs.
- Suggested span names:
boruna.cap.<name> (e.g. boruna.cap.net.fetch).
- Suggested attributes:
cap.name, cap.budget_remaining, bytes_in, bytes_out, error.
- Activation: env var
OTEL_EXPORTER_OTLP_ENDPOINT (the OpenTelemetry standard) — no Boruna-specific flag needed.
- Make this a Cargo feature (
telemetry) so the dependency is opt-in for integrators who don't need it.
Source: FleetQ implementer feedback letter, 2026-04-25 (P2 #9).
Reported by FleetQ as a P2 power feature. A
--telemetry-otlp <endpoint>flag (or env var) emitting OpenTelemetry spans for each capability call (net.fetch,fs.read, …) with timing/byte counts.Ask
Per-capability OpenTelemetry spans, exportable to any OTLP collector. FleetQ already runs a tenant-scoped collector and would surface Boruna's resource usage right next to LLM/agent spans in their UI without writing glue code.
Notes for implementers
opentelemetryandopentelemetry-otlpcrates are stable. Wire them at theCapabilityGateway::callboundary incrates/llmvm/src/capability_gateway.rs.boruna.cap.<name>(e.g.boruna.cap.net.fetch).cap.name,cap.budget_remaining,bytes_in,bytes_out,error.OTEL_EXPORTER_OTLP_ENDPOINT(the OpenTelemetry standard) — no Boruna-specific flag needed.telemetry) so the dependency is opt-in for integrators who don't need it.Source: FleetQ implementer feedback letter, 2026-04-25 (P2 #9).