Agent skill · data analytics · iii-hq
iii-observability
OpenTelemetry-backed tracing, structured logs, metrics with rollups, alerts, sampling, and baggage for the engine — emit and query telemetry through `engine::*` functions and react to logs with a `log` trigger.
Why this skill is useful
Provides domain-specific commands and configurations for OpenTelemetry that the AI wouldn't reliably generate on its own.
What it needs
Requires opentelemetry installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 18,563 stars on the source repository.
What this skill does
iii-observability The iii-observability worker provides OpenTelemetry-backed observability for the iii engine: distributed tracing, structured logs, metrics with rollups, alert rules, sampling configuration, and baggage propagation. Every surface is a callable engine:: function, plus a single log reactive trigger that fires on every ingested log entry. Functions span nine sub-namespaces — emit, query stored telemetry, inspect configuration, and propagate context. The worker is on by default (enabled: true). When disabled, the emit and read functions still register but become no-ops and the trigger never fires. Core config: servicename/serviceversion/servicenamespace (OTel resource attributes), exporter (memory otlp both), endpoint (OTLP collector URL, default http://localhost:4317), samplingratio (0.0–1.0), memorymaxspans, and per-pillar toggles/limits (metricsenabled, logsenabled, retention and count caps). Most fields accept OTEL env overrides. The in-memory query functions (logs, traces) require the memory or both exporter. Traces and metrics use OTLP/gRPC by default; https:// endpoints enable TLS and http:// endpoints use cleartext. Set OTELEXPORTEROTLPPROTOCOL=http/protobuf to use OTLP/HTTP protobuf for traces and metrics, or use OTELEXPORTEROTLPTRACESPROTOCOL / OTELEXPORTEROTLPMETRICSPROTOCOL for signal-specific overrides. The HTTP/protobuf path is appended automatically (/v1/traces, /v1/metrics) when the configured endpoint is a base collector URL. Logs export over OTLP/HTTP to /v1/logs. Use OTELEXPORTEROTLPHEADERS for collector headers and the signal-specific OTELEXPORTEROTLPTRACESHEADERS, OTELEXPORTEROTLPMETRICSHEADERS, or OTELEXPORTEROTLPLOGSHEADERS when needed. The logs exporter reads OTELEXPORTEROTLPLOGSHEADERS first and falls back to OTELEXPORTEROTLPHEADERS. Keep credentials in environment variables or a secret manager, not in config files. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills iii-hq/skills--39b327