OpenInference Groq Instrumentation
Python autoinstrumentation library for the Groq package
This package implements OpenInference tracing for both Groq and AsyncGroq clients.
These traces are fully OpenTelemetry compatible and can be sent to an OpenTelemetry collector for viewing, such as Arize Phoenix or Arize AX.
Installation
pip install openinference-instrumentation-groq
Quickstart
Through your terminal, install required packages.
pip install openinference-instrumentation-groq groq arize-phoenix opentelemetry-sdk opentelemetry-exporter-otlp
You can start Phoenix with the following terminal command:
python -m phoenix.server.main serve
By default, Phoenix listens on http://localhost:6006. You can visit the app via a browser at the same address. (Phoenix does not send data over the internet. It only operates locally on your machine.)
Try the following code in a Python file.
- Set up
GroqInstrumentorto trace your application and sends the traces to Phoenix. - Then, set your Groq API key as an environment variable.
- Lastly, create a Groq client, make a request, then go see your results in Phoenix at
http://localhost:6006!
import os
from groq import Groq
from openinference.instrumentation.groq import GroqInstrumentor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.sdk import trace as trace_sdk
from opentelemetry.sdk.trace.export import SimpleSpanProcessor
# Configure GroqInstrumentor with Phoenix endpoint
endpoint = "http://127.0.0.1:6006/v1/traces"
tracer_provider = trace_sdk.TracerProvider()
tracer_provider.add_span_processor(SimpleSpanProcessor(OTLPSpanExporter(endpoint)))
GroqInstrumentor().instrument(tracer_provider=tracer_provider)
os.environ["GROQ_API_KEY"] = "YOUR_KEY_HERE"
client = Groq()
chat_completion = client.chat.completions.create(
messages=[
{
"role": "user",
"content": "Explain the importance of low latency LLMs",
}
],
model="llama3-8b-8192",
)
if __name__ == "__main__":
print(chat_completion.choices[0].message.content)
Now, on the Phoenix UI on your browser, you should see the traces from your Groq application. Click on a trace, then the "Attributes" tab will provide you with in-depth information regarding execution!
More Info
Metadata
Release files for openinference-instrumentation-groq 0.1.28
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openinference_instrumentation_groq-0.1.28.tar.gz | 12.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openinference_instrumentation_groq-0.1.28-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.5 kB
Release files / openinference_instrumentation_groq-0.1.28.tar.gz
| Download URL | openinference_instrumentation_groq-0.1.28.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56b397bb2d9a3f9d17a2faa4d16575978b2f3ede3ca6557e160a305ced4fda62
|
|
BLAKE2b-256 checksum How to use checksums |
9e1ab6d1bfcc6e7888685a1a0d245a0bc621df7c3d92c868f46cb2aa177857f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / openinference_instrumentation_groq-0.1.28-py3-none-any.whl
| Download URL | openinference_instrumentation_groq-0.1.28-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d48471e9a07da3a7ce7f3ae1ccfadd02a5cadb0761b7a52bbabc96ac56d89701
|
|
BLAKE2b-256 checksum How to use checksums |
8f3a5e404452461858ac08febaf03085506a391552fd6791bd21d2a1a3e2d4a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log