Skip to main content

tallwright-otel

Cloud Proof from OpenTelemetry: a span processor that hands the Python SDK the generative-AI spans your tracing already has. Any instrumentation that follows the OpenTelemetry semantic conventions for generative AI feeds it, whatever framework it instruments.

It is a thin adapter on tallwright-cloud: it decides when to hand the client an event and what content to hand it, and nothing else (the adapter contract).

Use it

import os

from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.sampling import ALWAYS_ON
from tallwright_cloud import Tallwright
from tallwright_otel import install

client = Tallwright(os.environ["TALLWRIGHT_INGEST"], os.environ["TALLWRIGHT_KEY"], "./tallwright-evidence")
provider = TracerProvider(sampler=ALWAYS_ON)
install(provider, client)
trace.set_tracer_provider(provider)

Then turn on your instrumentation's content capture (the conventions make arguments, results and messages opt-in), and at the end of a run call client.flush().

What becomes a record

  • An execute_tool span: the tool's name, its call id and its arguments, as an action with the tool's name as its action_type; then what it returned, or the type of its error, as context.
  • A chat, text_completion or generate_content span: the model, its system instructions and the input messages, as context the agent received.

Each record carries the moment the span gives (timestamp: its start, or its end for an outcome), and its content names the trace and the span, so a record and the trace it came from can be found from each other. Reasoning parts are left out and named in omitted_parts; named credential keys are replaced, with each path in withheld_argument_keys or withheld_result_keys. What a span did not carry is named in absent, never guessed.

What it cannot do, by construction

  • It never stops an action. A span reaches a processor when it ends, after the tool ran. This adapter records actions afterwards, is best effort only, and offers no fail-closed mode. A deployment that must not act unrecorded uses a framework adapter: tallwright-langgraph, tallwright-openai-agents or tallwright-mcp.
  • It sees only sampled spans. A span that was not sampled reaches no processor, so install refuses a provider whose sampler can drop one; the SDK's default, which follows an unsampled parent from another service, is refused too. Sample in your collector instead.
  • It records what the spans carry, as the instrumentation set it. An instrumentation that leaves a call untraced, or content capture left off, leaves that out of the record. The conventions themselves are still in development.
  • A failure is logged by its type, never with content, and tracing goes on.

License

Copyright 2026 David Jöbstl. Licensed under the Apache License, Version 2.0: the package carries the license text and the NOTICE.

Metadata

Release files for tallwright-otel 0.1.0

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

Built distribution (wheel)

Table of built distributions (wheels) for tallwright-otel 0.1.0
File Interpreter ABI Platform Actions
tallwright_otel-0.1.0-py3-none-any.whl Python 3 none any Details for tallwright_otel-0.1.0-py3-none-any.whl

Release files / tallwright_otel-0.1.0-py3-none-any.whl

Download URL tallwright_otel-0.1.0-py3-none-any.whl
Size 11.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0e56052a8589dd39fe7c31b2bc3fafa6c5245f92e31a5a911c4731efbe1770ad
BLAKE2b-256 checksum
How to use checksums
d6fb04f4b9b8ebaf9cde4ed88c0a3a52caa0de75be47189e679b24fdfc3ee337
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 Nov 16, 2026.

Transparency log

Security for tallwright-otel 0.1.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.

Full provenance

1 file in this release has been uploaded with provenance metadata.

Attestation for tallwright_otel-0.1.0-py3-none-any.whl

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 Nov 16, 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

1 release file Full provenance

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