opentelemetry-instrumentation-groq
OpenTelemetry Groq instrumentation
Decision gist · record as of 2026-08-14
Yes, if you use the Groq SDK and need observability. The package is actively maintained, has no known vulnerabilities, and integrates seamlessly with OpenTelemetry. The privacy control (TRACELOOP_TRACE_CONTENT) makes it suitable for production use. Install it if you want automatic LLM tracing without manual instrumentation code.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; Groq SDK must be installed separately for instrumentation to function.
- Low friction: pure Python wheel with four stable OpenTelemetry runtime dependencies.
- Actively maintained with a recent release (4 days old) and no known vulnerabilities.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows free use, modification, and distribution in both open and proprietary projects without copyleft obligations.
last release 2026-08-10 (4 days) · last repo commit 2026-08-10 · 7,377 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 2,858,863 downloads/mo, #2,858 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-groq
from opentelemetry.instrumentation.groq import GroqInstrumentor
GroqInstrumentor().instrument()- Whether the instrumentation works with all Groq SDK versions or has version constraints beyond what the fact sheet states
- Performance overhead of tracing on high-volume LLM applications
- Whether sensitive data redaction beyond the TRACELOOP_TRACE_CONTENT flag is supported
What it is and what it does
This package is an OpenTelemetry instrumentation plugin that hooks into the official Groq Python SDK to automatically capture traces of LLM API calls. When installed and initialized, it intercepts Groq SDK requests and logs prompts, completions, and other metadata as OpenTelemetry span attributes, giving you visibility into how your LLM application behaves in production.
By default, it logs full prompt and completion content to help with debugging and quality evaluation. However, you can disable content logging by setting the TRACELOOP_TRACE_CONTENT environment variable to false if you need to protect sensitive user data or reduce trace size. The instrumentation integrates with the standard OpenTelemetry ecosystem, so traces can be exported to any compatible backend (Jaeger, Datadog, etc.) for centralized monitoring.
Use it for
- Debug LLM application behavior by inspecting actual prompts and completions sent to Groq in production traces.
- Monitor token usage and latency of Groq API calls across your application using OpenTelemetry-compatible observability platforms.
- Evaluate output quality by correlating prompts with completions in distributed traces for performance analysis.
- Audit LLM interactions for compliance by capturing structured span data without modifying application code.
- Troubleshoot integration issues between your application and Groq by examining instrumented request/response cycles.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you use the Groq SDK and need observability.
The package is actively maintained, has no known vulnerabilities, and integrates seamlessly with OpenTelemetry. The privacy control (TRACELOOP_TRACE_CONTENT) makes it suitable for production use. Install it if you want automatic LLM tracing without manual instrumentation code.
Install
opentelemetry-instrumentation-groq on PyPI
Before you install
Low friction: pure Python wheel with four stable OpenTelemetry runtime dependencies. Actively maintained with a recent release (4 days old) and no known vulnerabilities.
Requires Python 3.10 or later; Groq SDK must be installed separately for instrumentation to function.
License in practice
Apache-2.0 permissive license allows free use, modification, and distribution in both open and proprietary projects without copyleft obligations.
Quickstart
pip install opentelemetry-instrumentation-groq
from opentelemetry.instrumentation.groq import GroqInstrumentor
GroqInstrumentor().instrument()Verify before relying
- Whether the instrumentation works with all Groq SDK versions or has version constraints beyond what the fact sheet states
- Performance overhead of tracing on high-volume LLM applications
- Whether sensitive data redaction beyond the TRACELOOP_TRACE_CONTENT flag is supported
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release <4,>=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesopentelemetry-apiopentelemetry-instrumentationopentelemetry-semantic-conventions-aiopentelemetry-semantic-conventions |
| Maintenance | Actively maintained 4 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 2,858,863 / month, #2,858 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: opentelemetry_instrumentation_groq-0.62.3-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “groq api tracing”
- opentelemetry-instrumentation-groqAutomatically captures traces of Groq SDK API calls, logging prompts,…
- opentelemetry-instrumentation-openai-v2Automatically traces and logs OpenAI API calls (and compatible…
- langchain-groqConnects Groq's inference API to LangChain, enabling language model…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also opentelemetry-instrumentation-alephalpha · opentelemetry-instrumentation-openai · opentelemetry-instrumentation-watsonx · openfeature-hooks-opentelemetry · opentelemetry-instrumentation-sagemaker · raindrop-ai · opentelemetry-instrumentation-anthropic · langwatch · traceloop-sdk · opentelemetry-instrumentation-litellm