agento11y-instrument

Instruments LLM applications to send generations and OTel telemetry to Grafana Agent Observability.

581|46|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/grafana/gcx --skill agento11y-instrument
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agento11y-instrument
Source: https://github.com/grafana/gcx/tree/main/claude-plugin/skills/agento11y-instrument
Command: npx skills add https://github.com/grafana/gcx --skill agento11y-instrument

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers wiring their own LLM app or agent to Grafana Agent Observability often end up with silent failures — generations never arrive, metrics vanish into a no-op OTel provider, or a misconfigured .env ships data to localhost — with no error signal to diagnose. This Skill audits the real code against a fixed gap checklist and verifies through gcx that data actually lands in the stack.

Core Features & Use Cases

  • Gap checklist audit: Classifies instrumentation state (none / partial / broken) and checks 12 known failure points with file:line evidence, headed by the missing TracerProvider/MeterProvider silent failure.
  • Verified instrument→run→verify loop: Applies minimal confirmed diffs, runs the app, and uses gcx agento11y agents|conversations|generations to confirm generations arrive, iterating up to 3-4 times.
  • Two-channel verification: Separately validates generation ingest (via gcx) and OTel traces/metrics (by construction, runtime OTLP POSTs, or the Performance/Tempo UI), since gcx cannot see the OTel channel.
  • Use Case: A developer says "my generations aren't showing up" — the Skill reads the app, finds the .env is overridden by a library's import-time defaults, fixes the load order, and confirms via gcx that the agent's generation count climbs.

Quick Start

Ask the agent to instrument my LLM app with Grafana Agent Observability and verify that generations actually land in my Grafana Cloud stack.

Frequently Asked Questions about agento11y-instrument

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I instrument my LLM app with Grafana Agent Observability?

Set the AGENTO11Y_* and OTEL_* environment variables, create OTel TracerProvider and MeterProvider before the SDK client, then wrap the LLM client with a provider wrapper, framework adapter, or hand-instrumentation. This Skill audits the code, applies minimal diffs with confirmation, and verifies data lands via gcx.

Why are my generations not showing up in Grafana Agent Observability?

Common silent causes include a .env overridden by library import-time defaults, missing AGENTO11Y_PROTOCOL=http and AGENTO11Y_AUTH_MODE=basic (causing a 401), or unchecked SDK recorder errors. The Skill's gap checklist diagnoses each with file:line evidence.

Why is the Performance view empty even though conversations appear?

Conversations use the generation ingest channel while Performance uses OTel metrics — a missing or no-op MeterProvider silently drops all latency, token, and cost metrics. gcx cannot see this channel, so the Skill verifies it by construction, runtime OTLP POSTs, or the Tempo/Performance UI.

Which languages and frameworks does Agent Observability instrumentation support?

Python has the most framework adapters, JavaScript fewer, and Go only google-adk; Java and .NET support the core SDK plus providers and google-adk. The Skill confirms adapter availability per language before recommending, preferring provider wrapper, then framework adapter, then hand-instrumentation.

Does this Skill write test suites or set up evaluation rules?

No. Offline test suites are handled by the agento11y-test-starter skill and tenant eval rules plus guards by agento11y-prod-setup. This Skill focuses solely on instrumentation and hands off once generations and metrics flow.