opentelemetry-instrumentation-bedrock
OpenTelemetry Bedrock instrumentation
Decision gist · record as of 2026-08-14
Yes, if you use Bedrock with Boto3 and have an OpenTelemetry deployment in place. The package is actively maintained, has no known vulnerabilities, and low install friction. Be aware that it logs sensitive prompt/completion data by default—set TRACELOOP_TRACE_CONTENT=false if privacy is a concern.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; Boto3 and an OpenTelemetry exporter must be configured separately to send traces.
- Low friction install with four runtime dependencies, all from the OpenTelemetry ecosystem.
- Active maintenance with a recent release (4 days old) and a well-established repository.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows use in commercial and proprietary projects with minimal restrictions.
last release 2026-08-10 (4 days) · last repo commit 2026-08-10 · 7,377 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 7,113,843 downloads/mo, #1,784 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-bedrock
from opentelemetry.instrumentation.bedrock import BedrockInstrumentor
BedrockInstrumentor().instrument()- Whether the instrumentation works with all Bedrock model types or only a subset
- Performance overhead of tracing on high-volume Bedrock API calls
- Compatibility with different OpenTelemetry exporters and backends
What it is and what it does
This package integrates OpenTelemetry tracing into AWS Bedrock API calls made via Boto3, automatically capturing request and response data as distributed trace spans. It lets you observe what prompts and completions flow through your LLM application, making it easier to debug issues and evaluate output quality.
By default, the instrumentation logs full prompt and completion text to span attributes, which provides visibility but may expose sensitive user data. You can disable this logging by setting the TRACELOOP_TRACE_CONTENT environment variable to false to reduce trace size or protect privacy. The package depends on the OpenTelemetry API, instrumentation framework, and semantic conventions libraries.
Use it for
- Debug LLM application behavior by inspecting actual prompts and completions sent to Bedrock models.
- Monitor Bedrock API usage patterns and latency across your distributed system using OpenTelemetry exporters.
- Evaluate output quality by correlating trace data with application metrics and user feedback.
- Audit sensitive data flow in production by selectively disabling content logging while keeping call metadata.
- Integrate Bedrock observability into existing OpenTelemetry deployments without additional instrumentation code.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you use Bedrock with Boto3 and have an OpenTelemetry deployment in place.
The package is actively maintained, has no known vulnerabilities, and low install friction. Be aware that it logs sensitive prompt/completion data by default—set TRACELOOP_TRACE_CONTENT=false if privacy is a concern.
Install
opentelemetry-instrumentation-bedrock on PyPI
Before you install
Low friction install with four runtime dependencies, all from the OpenTelemetry ecosystem. Active maintenance with a recent release (4 days old) and a well-established repository.
Requires Python 3.10 or later; Boto3 and an OpenTelemetry exporter must be configured separately to send traces.
License in practice
Apache-2.0 permissive license allows use in commercial and proprietary projects with minimal restrictions.
Quickstart
pip install opentelemetry-instrumentation-bedrock
from opentelemetry.instrumentation.bedrock import BedrockInstrumentor
BedrockInstrumentor().instrument()Verify before relying
- Whether the instrumentation works with all Bedrock model types or only a subset
- Performance overhead of tracing on high-volume Bedrock API calls
- Compatibility with different OpenTelemetry exporters and backends
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release <4,>=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesopentelemetry-apiopentelemetry-instrumentationopentelemetry-semantic-conventions-aiopentelemetry-semantic-conventions |
| Maintenance | Actively maintained 4 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 7,113,843 / month, #1,784 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: opentelemetry_instrumentation_bedrock-0.62.3-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “bedrock tracing”
- opentelemetry-instrumentation-bedrockAdds distributed tracing to AWS Bedrock API calls made through Boto3,…
- openinference-instrumentation-bedrockAutomatically instruments AWS Bedrock API calls (invoke_model,…
- opentelemetry-instrumentation-botocoreAdds distributed tracing to AWS SDK calls made through botocore and…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also opentelemetry-instrumentation-langchain · opentelemetry-instrumentation-sagemaker · opentelemetry-instrumentation-mcp · opentelemetry-instrumentation-boto · opentelemetry-instrumentation-transformers · opentelemetry-instrumentation-ollama · opentelemetry-instrumentation-groq · aiobotocore-otel · aws-bedrock-token-generator · lumigo-core