telemetry.dev

Use Python 3.10 or newer. Install the OpenAI integration:

pip install telemetry-dev-openai

Use the same API keys as the TypeScript example. Save this as trace.py:

import telemetry_dev
from openai import OpenAI
from telemetry_dev_openai import wrap_openai

telemetry_dev.init(service_name="my-ai-app")
client = wrap_openai(OpenAI())

try:
    response = client.chat.completions.create(
        model="gpt-4o-mini",
        messages=[{"role": "user", "content": "What is OpenTelemetry?"}],
    )
    print(response.choices[0].message.content)
finally:
    telemetry_dev.shutdown()

Run the request:

python trace.py

The Release workflow uses Release Please to propose version bumps on main. Merging a release PR lets Release Please create component releases such as sdk-v0.1.3 or python-v0.2.3. Each published release builds and publishes only its matching package. Build jobs have no publishing credentials; separate publish jobs use registry OIDC trusted publishing, not long-lived npm or PyPI tokens.

The manifest retains versions already published from the original repository. bootstrap-sha points to the initial SDK import so that import's feat commit does not trigger new versions. Do not create releases to republish these baseline versions: wait for subsequent releasable changes. No new version is required merely to transfer publishing to this repository.

The workflow is restored, but publishing is not fully configured until the following handoff is complete:

• Provide the repository Actions secret RELEASE_PLEASE_TOKEN, authorized for telemetry-dev/telemetry with contents, issues, and pull-request write permissions. The original repository's secret cannot be read or copied from GitHub; its owner must supply or replace it. The workflow deliberately fails when this secret is missing. Do not substitute GITHUB_TOKEN: releases created with it do not trigger the downstream release workflow.
• Configure every npm package's GitHub Actions trusted publisher for owner telemetry-dev, repository telemetry, and workflow filename release.yml, without an environment name. npm publishing runs on GitHub-hosted runners and includes provenance for this public repository.
• Configure every PyPI project's GitHub Actions trusted publisher for owner telemetry-dev, repository telemetry, and workflow filename release.yml, and environment pypi. The repository's pypi environment permits branch main for retries and tags matching python*-v*; it has no required reviewers. These branch/tag restrictions are not a manual approval gate.
• Require successful CI before merging release PRs. Verify all trusted-publisher settings and the secret before expecting an end-to-end publish to succeed.

Run the release safety suite locally with Bash, Git, jq, Python 3, tar, and OpenSSL; the registry commands in these tests are mocked and publish nothing:

bash .github/scripts/release_test.sh
shellcheck .github/scripts/*.sh
actionlint

To retry an existing published release, run the Release workflow from main and set release_tag to that release's full tag. This is a real publication attempt, not a dry run. The tag must be an ancestor of the selected main commit. Every configured SDK directory, shared build scripts, lockfiles, release configuration, and root build configuration must be unchanged from the tag; only packageManager may differ within root package.json. Workflow-only recovery changes are allowed. Source-changing fixes need a new release, not a retry of an old version.

Artifact names and versions are checked before upload. npm retries skip an existing version only when its SHA-512 integrity matches the local tarball, and publication waits for published @telemetry-dev/* dependencies and peer dependencies to satisfy their declared ranges. PyPI retries use uv publish --check-url to check existing distributions. An integrity mismatch must be investigated, not bypassed or overwritten.