OpenTelemetry Bedrock Instrumentation
This library allows tracing any of AWS Bedrock's models prompts and completions sent with Boto3 to Bedrock.
Installation
pip install opentelemetry-instrumentation-bedrock
Example usage
from opentelemetry.instrumentation.bedrock import BedrockInstrumentor
BedrockInstrumentor().instrument()
Privacy
By default, this instrumentation logs prompts, completions, and embeddings to span attributes. This gives you a clear visibility into how your LLM application is working, and can make it easy to debug and evaluate the quality of the outputs.
However, you may want to disable this logging for privacy reasons, as they may contain highly sensitive data from your users. You may also simply want to reduce the size of your traces.
To disable logging, set the TRACELOOP_TRACE_CONTENT environment variable to false.
TRACELOOP_TRACE_CONTENT=false
Release files for opentelemetry-instrumentation-bedrock 0.63.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 | Actions |
|---|---|---|---|---|
| opentelemetry_instrumentation_bedrock-0.63.0.tar.gz | 253.3 kB | With provenance | Details for opentelemetry_instrumentation_bedrock-0.63.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| opentelemetry_instrumentation_bedrock-0.63.0-py3-none-any.whl | Python 3 | none | any | Details for opentelemetry_instrumentation_bedrock-0.63.0-py3-none-any.whl |
Total release size: 280.9 kB
Release files / opentelemetry_instrumentation_bedrock-0.63.0.tar.gz
| Download URL | opentelemetry_instrumentation_bedrock-0.63.0.tar.gz |
|---|---|
| Size | 253.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7209ee3ff63f710a0c914467bc63c35dae68ecee938b0fe16f979d70205e570
|
|
BLAKE2b-256 checksum How to use checksums |
71f80470c837482845f8bbc105b5287e37bf0ca8e04386cdb16e89320cfe8084
|
| 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 Nov 5, 2026.
Transparency logRelease files / opentelemetry_instrumentation_bedrock-0.63.0-py3-none-any.whl
| Download URL | opentelemetry_instrumentation_bedrock-0.63.0-py3-none-any.whl |
|---|---|
| Size | 27.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d4f643024bc7e26a4a693dacff08768a6a968a2c5145222aa2215a8813b38d9
|
|
BLAKE2b-256 checksum How to use checksums |
31d87ee2bdc93ab32a9b0d0dda42a132c9d69335cdb4840cd239c0903b8fccfa
|
| 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 Nov 5, 2026.
Transparency logSecurity for opentelemetry-instrumentation-bedrock 0.63.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for opentelemetry_instrumentation_bedrock-0.63.0.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 Nov 5, 2026.
Transparency logA 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.
