instrument-llm-observability

Add OpenTelemetry tracing to LLM applications capturing prompts, tool calls, token usage, latency, and cost.

29|8|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/ContextJet-ai/awesome-llm-observability --skill instrument-llm-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: instrument-llm-observability
Source: https://github.com/ContextJet-ai/awesome-llm-observability/tree/main/skills/instrument-llm-observability
Command: npx skills add https://github.com/ContextJet-ai/awesome-llm-observability --skill instrument-llm-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of adding tracing and observability to LLM or AI-agent applications, ensuring every run is inspectable with details like prompts, tool calls, token usage, latency, and cost per step.

Core Features & Use Cases

  • Tracing Integration: Offers vendor-neutral OpenTelemetry for tracing LLM applications.
  • Cost and Performance Monitoring: Captures cost per span and latency data.
  • Custom Instrumentation: Allows manual spans for custom tool/retrieval steps.
  • Use Case: When debugging an LLM app in production or implementing cost and performance tracking, this Skill can be triggered to add the necessary tracing and observability features.

Quick Start

Run the 'instrument-llm-observability' skill to add production-grade tracing to your LLM application.

Frequently Asked Questions about instrument-llm-observability

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

FAQPage Schema
How do I add tracing to my LLM application to monitor token usage and latency?

To add tracing to an LLM application, you need production-grade instrumentation that captures prompts, tool calls, token usage, latency, and cost per step, ensuring every run is fully inspectable for monitoring.

Does OpenTelemetry work for LLM observability in AI agent applications?

OpenTelemetry works for LLM observability by providing vendor-neutral GenAI semantic conventions, enabling tracing integration that captures cost per span and latency data across various LLM SDKs in AI agent applications.

How do I track cost per step when debugging an LLM app in production?

To track cost per step when debugging an LLM app in production, implement observability instrumentation that captures cost per span and latency data, allowing you to inspect detailed performance metrics for each run.

Can I create custom spans for my own tool and retrieval steps in an AI agent?

You can create custom spans for tool and retrieval steps in an AI agent through custom instrumentation, allowing manual span creation to capture specific operations and enhance tracing observability.

What is the best way to instrument an AI agent for cost and performance tracking?

The best way to instrument an AI agent for cost and performance tracking is using vendor-neutral OpenTelemetry tracing, which captures cost per span, latency data, and tool calls to ensure every run is fully inspectable.