sigil-telemetry
Plug-and-play telemetry for AI agents. Install it, call init(), and every LLM call your agent makes is automatically tracked.
Quick Start
pip install sigil-telemetry[all]
from sigil_telemetry import init
init()
# Set your agent's ID and collector endpoint
SIGIL_AGENT_ID=your-agent-slug
SIGIL_COLLECTOR_URL=https://your-collector-endpoint/
That's it. Every LLM API call is now captured — tokens, model, latency, errors — and sent to your collector.
What's New in v0.6.0
- Every LLM call is captured, however it is made. Before 0.6.0 only calls through an instrumented SDK were seen — an agent calling a model with plain
httpx.post(...)sent nothing.init()now also watches the HTTP clients underneath (httpxand its forkhttpx2, which the OpenAI SDK uses from 3.x,requests/urllib3,boto3,aiohttp,urllib) pluswebsockets(OpenAI Realtime) andgrpc(older Gemini/Vertex SDKs). A call is recognised from its host, its route, or its request/response shape — Anthropic, OpenAI (Chat and Responses), Azure OpenAI and Foundry, Gemini/Vertex, Bedrock, Ollama, Cohere and any OpenAI-compatible server — streamed (SSE, NDJSON, AWS event-stream) or not, compressed or not. - No double counting. When an SDK instrumentor is already recording a call, transport capture records no span of its own; SDK spans keep their richer detail (tool calls, agent names) and get the agent attributes below.
- Prompts and answers recorded on every LLM span (
gen_ai.input.messages,gen_ai.output.messages,gen_ai.system_instructions, tool calls and results included). What Sigil receives is kept as valid JSON under 8000 characters, below the Application Insights property limit of 8192 — the latest turn is protected, older turns are shortened or dropped first. Every other long string on every span, including the instrumentors' own prompt copies (gen_ai.prompt.N.content,llm.input_messages.N…,input.value), is cut to 8000 too, ending in…[truncated]. (If the app also exports to its own backend, that export gets the content unshortened, as the SDK instrumentors always sent it.) Turn off withSIGIL_CAPTURE_CONTENT=false. - One attribute vocabulary. Spans from older OpenLLMetry versions (
gen_ai.system,gen_ai.usage.prompt_tokens,gen_ai.prompt.N.*) and from OpenInference (llm.*, e.g. LiteLLM) are exported with the currentgen_ai.*names too, so a different instrumentor version can't silently change Sigil's numbers. - Works alongside the app's own tracing. If the Azure Monitor distro, Logfire or anything else already set a TracerProvider, Sigil's exporter is added to it instead of being silently dropped.
- Processes too.
ProcessPoolExecutorandmultiprocessing.Processwork keeps the request's trace and user, and is flushed when it ends. Celery tasks are traced from the code that queued them ([celery]extra). - Agents told apart, from what they do. Every LLM span says which of the agent's functions made it (
sigil.agent.site, e.g.app.services.llm._llm_extract ← …). Calls from one site are compared, and what stays the same across them is the agent's fixed prompt: after 5 calls with at least 3 different inputs (and 2 different users, when calls carry a user) the span getssigil.prompt.status = splitandsigil.prompt.id— one id per AI task, so the same instructions called from two places in the code are one agent, and different instructions are different agents. The fixed prompt is sent once per process per version (sigil.prompt.fixed.0,.1, …, scrubbed of emails, phone numbers, IBANs, card and national id numbers), and from then on each run'sgen_ai.input.messagescarries only its input, with{"type": "fixed"}where the fixed prompt was. - Non-text input described in
sigil.input.files:pdf · Renewal_2026.pdf · 2.1 MB,image · png · 88 KB,audio · wav · 388 KB · 12.4 s(seconds exact for WAV and Realtime audio,~estimated for MP3). Files uploaded to start a request (FastAPIUploadFile, Flaskrequest.files, Djangorequest.FILES) are described on the request span — name, type and size only; this followsSIGIL_CAPTURE_USER.sigil.input.charsis the whole prompt's length before any cutting. - Handoffs between agents.
sigil.handoff.fromlists the earlier spans (<trace id>-<span id>) whose answer this call's input carries (at least 30% of it) — one agent's output becoming another's input.sigil.handoff.in/sigil.handoff.out/sigil.handoff.in_maxare hashed fingerprints of the input and answer, so your backend can find handoffs across processes and hours (a person reviewing in between). Ids, sites, file descriptions and fingerprints are sent even withSIGIL_CAPTURE_CONTENT=false; no text is.
What's New in v0.3.0
- Automatic user identity capture — Extracts the calling user from Azure AD / SSO headers or JWT Bearer tokens on every request. No code changes needed — works out of the box with
init(). Disable withSIGIL_CAPTURE_USER=false. - Worker agent support — Set
SIGIL_USER_IDenv var for scheduled jobs and queue workers that don't have HTTP requests. - Background work stays in its run (0.5.2) — LLM calls made on a
ThreadPoolExecutororThreadafter the response has been sent keep the trace and user of the request that started them. Before 0.5.2 each became its own orphan trace with no user.
What's New in v0.2.0
- Web framework auto-instrumentation — FastAPI, Flask, and Django are auto-detected and instrumented. All LLM calls within one HTTP request share a single
trace_id(operation_Id), so you can count agent "runs" withCOUNT(DISTINCT trace_id). - Noise span filtering —
http send/http send bodyspans from web frameworks are silently dropped before they leave the process. They never reach your collector. - Health check exclusion — Routes like
/health,/healthz,/ready,/alive,/pingare excluded from tracing entirely. - Graceful shutdown —
atexithandler flushes all pending spans when the process exits, so you never lose the last batch. - Lighter install — Removed unnecessary dependencies from the core install.
Full Example
Here's a real agent that summarizes documents using Claude:
1. The Agent Code
# document_summarizer.py
import anthropic
from sigil_telemetry import init
# Initialize telemetry — call this ONCE at startup
init()
# Your normal agent code — no changes needed
client = anthropic.Anthropic()
response = client.messages.create(
model="claude-sonnet-4-20250514",
max_tokens=1024,
messages=[
{"role": "user", "content": "Summarize this document: ..."}
]
)
print(response.content[0].text)
2. What Gets Captured (Per LLM Call)
Every time client.messages.create() runs, a span is automatically created with:
| Field | Example Value | Description |
|---|---|---|
operation_Id |
a1b2c3d4e5f6... |
Trace ID — groups all LLM calls in a single agent run |
sigil.agent.id |
doc-summarizer |
Which agent made the call |
sigil.agent.version |
0.1.0 |
Agent version |
sigil.agent.frameworks |
Anthropic,FastAPI |
Which SDKs and frameworks were detected |
sigil.user.id |
jane.doe@example.com |
Who triggered this run (auto-captured) |
gen_ai.system |
anthropic |
LLM provider |
gen_ai.request.model |
claude-sonnet-4-20250514 |
Model used |
gen_ai.usage.input_tokens |
1250 |
Tokens sent |
gen_ai.usage.output_tokens |
340 |
Tokens received |
duration |
2.3s |
How long the call took |
status |
OK or ERROR |
Whether the call succeeded |
sigil.environment |
production |
Environment |
sigil.agent.division |
Sales |
Business division (if set) |
sigil.agent.risk_classification |
low |
Risk level (if set) |
If the agent makes multiple LLM calls in one run (e.g., calls Claude then GPT-4), all calls share the same operation_Id so you can see the full trace.
3. How Trace Grouping Works
API agents (FastAPI/Flask/Django): The web framework instrumentor creates a root span per HTTP request. All LLM calls within that request automatically become child spans sharing the same trace_id. You don't need to do anything — init() handles it.
Worker agents (scheduled jobs, listeners): Wrap your main() function in a custom span. All LLM calls within one job share the same trace_id.
In both cases: COUNT(DISTINCT trace_id) = number of agent runs.
4. Where the Data Goes
Agent makes LLM call
│
▼
sigil-telemetry auto-captures it as an OpenTelemetry span
(noise spans like "http send" are filtered out here)
│
▼
Span is batched and sent via OTLP to:
→ Your configured collector endpoint
│
▼
Collector forwards to:
→ Your observability backend (Jaeger, Zipkin, Datadog, etc.)
User Identity Capture
v0.3.0 automatically captures who triggered each agent run. No code changes needed.
How it works:
| Auth Method | How Identity Is Captured |
|---|---|
| Azure AD / SSO (Easy Auth) | Reads X-MS-CLIENT-PRINCIPAL-NAME header automatically |
| Azure AD / SSO (in-app JWT) | Decodes Bearer token, extracts preferred_username → upn → email → name → oid |
| Worker agents (no HTTP) | Reads SIGIL_USER_ID env var |
The captured user ID is attached as sigil.user.id on every request span. All LLM calls within that request inherit the user context through the shared trace.
Disable user capture:
SIGIL_CAPTURE_USER=false
Or in code:
init(SigilConfig(capture_user=False))
Supported SDKs
Use [all] to install everything. Only the SDKs your agent actually uses get activated.
| SDK | Install Extra | What It Covers |
|---|---|---|
| Anthropic | [anthropic] |
Anthropic API |
| OpenAI | [openai] |
OpenAI API (including compatible endpoints) |
| LangChain | [langchain] |
LangChain, LangGraph, any LangChain-wrapped model |
| CrewAI | [crewai] |
CrewAI multi-agent framework |
| LlamaIndex | [llamaindex] |
LlamaIndex agents and pipelines |
| Vertex AI | [vertexai] |
Google Vertex AI, Gemini models |
| Mistral AI | [mistral] |
Mistral API |
| AWS Bedrock | [bedrock] |
Claude, Llama, Titan via AWS |
| LiteLLM | [litellm] |
Unified proxy across 100+ LLM providers |
Anything else — raw HTTP, an SDK without an instrumentor, a self-hosted or gateway endpoint — is recorded by transport capture with no extra install: model, tokens, prompt, answer, latency and errors (no SDK-level detail such as tool calls). Those spans carry sigil.capture.source = transport.
Not covered: agents that are not written in Python, low-code platforms, models running inside the process (transformers, llama-cpp), Batch APIs (usage arrives hours later in a file), and gateways whose responses don't carry token usage (the call is recorded without tokens when the host is a known model host).
Web Framework Auto-Instrumentation
These are included in [all] and auto-detected by init():
| Framework | Install Extra | What It Does |
|---|---|---|
| FastAPI | [fastapi] |
Creates root span per HTTP request — all LLM calls in that request share one trace_id |
| Flask | [flask] |
Same trace grouping for Flask apps |
| Django | [django] |
Same trace grouping for Django apps |
| Celery | [celery] |
One trace per task, linked to the code that queued it |
Health check routes (/health, /healthz, /ready, /alive, /ping, /startup, /liveness, /readiness) are automatically excluded from tracing.
Configuration
| Env Variable | Default | Description |
|---|---|---|
SIGIL_AGENT_ID |
— | Required. Your agent's unique ID |
SIGIL_AGENT_VERSION |
0.1.0 |
Track deployments |
SIGIL_COLLECTOR_URL |
— | Required. Your collector endpoint URL |
SIGIL_ENVIRONMENT |
production |
production, staging, development |
SIGIL_CONSOLE_EXPORT |
false |
Print spans to console for debugging |
SIGIL_DIVISION |
— | Business division (e.g., Sales, Engineering) |
SIGIL_RISK_CLASSIFICATION |
— | Agent risk level (low, medium, high) |
SIGIL_HOURS_SAVED |
— | Estimated hours saved per run |
SIGIL_CAPTURE_USER |
true |
Set false to disable automatic user identity capture |
SIGIL_USER_ID |
— | Static user ID for worker agents with no HTTP context |
SIGIL_PROPAGATE_CONTEXT |
true |
Set false to stop background threads and processes inheriting the request's trace and user |
SIGIL_CAPTURE_CONTENT |
true |
Set false to stop recording prompts and answers |
SIGIL_CAPTURE_TRANSPORT |
true |
Set false to record only calls made through an instrumented SDK |
SIGIL_MAX_CONTENT_CHARS |
8000 |
Longest string attribute sent. Can be lowered, never raised past 8000 (Application Insights cuts or drops a property over 8192) |
Or pass config in code:
from sigil_telemetry import init, SigilConfig
init(SigilConfig(
agent_id="my-agent",
environment="development",
console_export=True,
capture_user=True
))
Custom Spans
Track things beyond LLM calls (document parsing, tool use, etc.):
from sigil_telemetry import get_tracer, record_error
tracer = get_tracer()
with tracer.start_as_current_span("parse-contract") as span:
span.set_attribute("document.pages", 42)
try:
result = parse_pdf(file)
except Exception as e:
record_error(span, e)
raise
Metadata
Release files for sigil-telemetry 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sigil_telemetry-0.6.0.tar.gz | 64.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sigil_telemetry-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 129.8 kB
Release files / sigil_telemetry-0.6.0.tar.gz
| Download URL | sigil_telemetry-0.6.0.tar.gz |
|---|---|
| Size | 64.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
281abb5a2b687cac358491ac8bdec76eed42639f8f8a5e0caf8bc771189a9a00
|
|
BLAKE2b-256 checksum How to use checksums |
c88b7e274509c449af63471a26f241a02b0dd9dc845ff10d668b24341fcecb39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.0
|
Release files / sigil_telemetry-0.6.0-py3-none-any.whl
| Download URL | sigil_telemetry-0.6.0-py3-none-any.whl |
|---|---|
| Size | 64.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c19769a6f8a44f910d17f1343c3a6e09e860a90f92440dec67a5b70acb7a0c91
|
|
BLAKE2b-256 checksum How to use checksums |
3bd06e6bc0dc74aed4636d1ebb1cc898acddd74930e1e0dddeace1a09b2ec6cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.0
|
Security for sigil-telemetry 0.6.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.