Skip to main content

pytracer-autogen

pyTracer adapter for AutoGen (0.4+). AutoGen instruments agents, tool calls, and model calls with OpenTelemetry using the GenAI semantic conventions. This adapter plugs a pyTracer exporter into an OpenTelemetry tracer provider, so those spans are captured as pyTracer spans with no @op in the agent code.

AutoGen emits its GenAI model and tool spans through the global OpenTelemetry provider, so register pyTracer globally with install() before building the runtime. Configure pyTracer first, so the exporter records into your transport:

import pytracer_sdk as pytracer
from pytracer_autogen import install
from autogen_core import SingleThreadedAgentRuntime

pytracer.configure(
    pytracer.HTTPTransport("https://gateway.internal", api_key="YOUR_KEY"),
    service_name="my-agent", branch="main", commit="abc123",
)

install()  # register pyTracer as the global OpenTelemetry provider
runtime = SingleThreadedAgentRuntime()

Passing a provider only to the runtime (SingleThreadedAgentRuntime(tracer_provider=pytracer_tracer_provider())) sees just the runtime's internal messaging spans, which the exporter drops as noise, so install() is the setup that captures the actual model and tool calls.

Because it keys off standard GenAI attributes (gen_ai.operation.name, gen_ai.tool.name, gen_ai.agent.name, gen_ai.usage.*), the same exporter captures spans from any GenAI-instrumented library, not only AutoGen.

Versions: what is captured depends on the AutoGen version emitting GenAI spans. Some versions emit no model-call span or tool result; pyTracer records what the framework reports, so upgrade AutoGen (or add the relevant GenAI instrumentation) if model calls or tool outputs are missing.

Replay

This adapter captures runs. Replaying a captured run currently requires @op instrumentation, because the replay engine intercepts @op calls; replay through the adapter itself is on the roadmap. Attempting to replay an adapter-only trace is flagged (the run has recordings but hits no @op seam) rather than silently running live. See the main README for the replay workflow.

Metadata

Release files for pytracer-autogen 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pytracer-autogen 0.1.3
File Size Uploaded Provenance
pytracer_autogen-0.1.3.tar.gz 6.5 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for pytracer-autogen 0.1.3
File Interpreter ABI Platform
pytracer_autogen-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 12.0 kB

Release files / pytracer_autogen-0.1.3.tar.gz

Download URL pytracer_autogen-0.1.3.tar.gz
Size 6.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9f6112243df191b69f02a3da716a148909ffdc1cdfb625b18c7af9608282ff02
BLAKE2b-256 checksum
How to use checksums
ec6309f18e39f13e50db97624479aa4c9ec488a05a75507134392c1c9bb1555d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 24, 2026.

Transparency log

Release files / pytracer_autogen-0.1.3-py3-none-any.whl

Download URL pytracer_autogen-0.1.3-py3-none-any.whl
Size 5.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ce041679ef0334c49bf37e617718449102737692c6a3d74cdac0295bd15d088b
BLAKE2b-256 checksum
How to use checksums
56dca46ac7d8c478a1e250f354f9d545ade7bfbc5eb1f2aba073ba857a33ad7d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 24, 2026.

Transparency log

Security for pytracer-autogen 0.1.3

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for pytracer_autogen-0.1.3.tar.gz

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 Oct 24, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page