{"categories":[{"label":"Monitoring","url":"https://skillfed.io/packages/category/system-monitoring/3"}],"enrichment":{"capability":"Adds OpenTelemetry tracing to LiteLLM, capturing LLM prompts, completions, and embeddings as spans and metrics across all LLM providers that LiteLLM supports.","skillfed_tags":["observability","llm-instrumentation","opentelemetry"],"use_cases":["Debug LLM application behavior by viewing exact prompts and completions in traces alongside latency and error data.","Monitor token usage and cost across multiple LLM providers in a unified observability platform.","Audit LLM interactions for compliance or quality review by exporting traces to a central collector.","Correlate LLM calls with upstream application requests using OpenTelemetry's trace context propagation.","Measure and optimize LLM performance across different providers or models using consistent metrics."],"what_it_does":"This package wraps LiteLLM to emit OpenTelemetry spans and metrics for every LLM call. Because LiteLLM normalizes responses from all providers into a single OpenAI-style format, the instrumentation produces consistent gen_ai.* spans regardless of whether you're calling different providers or custom LLM implementations. By default it logs prompts, completions, and embeddings to span attributes for visibility and debugging; you can disable this via the TRACELOOP_TRACE_CONTENT environment variable if the data is sensitive.\n\nThe package depends on opentelemetry-api, opentelemetry-instrumentation, opentelemetry-semantic-conventions-ai, and opentelemetry-semantic-conventions, and requires Python 3.10 or later. It integrates directly into your LiteLLM calls with a single .instrument() call, making it straightforward to add observability to existing LLM applications without rewriting call sites.","worth_installing":"Yes. The package is actively maintained, has no known vulnerabilities, low install friction, and solves a real problem: getting consistent observability across LiteLLM's multi-provider abstraction. The privacy control via environment variable is a thoughtful addition. Install it if you're using LiteLLM and need tracing; skip it only if you have no observability requirements."},"id":"opentelemetry-instrumentation-litellm","links":{"html":"https://skillfed.io/packages/opentelemetry-instrumentation-litellm","md":"https://skillfed.io/packages/opentelemetry-instrumentation-litellm.md","pypi":"https://pypi.org/project/opentelemetry-instrumentation-litellm/"},"maintenance":{"status":"active"},"meta":{"latest_release":"2026-08-10","license_spdx":"Apache-2.0","license_treatment":"permissive","name":"opentelemetry-instrumentation-litellm","python_support":"supports_current","summary":"OpenTelemetry LiteLLM instrumentation"},"popularity":{"monthly_downloads":748066,"position":5166,"tier":"top_15000"},"security":{"n_vulnerabilities":0},"version":"0.62.3"}