Skip to main content

respan-instrumentation-sagemaker

Observe the three native SageMaker Runtime boto3 operations: InvokeEndpoint, InvokeEndpointWithResponseStream and InvokeEndpointAsync. Current boto3/botocore 1.43.108 and the declared 1.34.0 floor are verified against released companions. Install and activate with an existing Respan or OTel provider:

from respan_instrumentation_sagemaker import SageMakerInstrumentor

instrumentor = SageMakerInstrumentor()
instrumentor.activate()
# Call the normal boto3 SageMaker Runtime client and read/close its returned body.
instrumentor.deactivate()

Native StreamingBody and EventStream instances, response dictionaries, bytes, iteration, context-manager return values, close behavior and exceptions are preserved. The adapter reads no response body in advance; it observes caller consumption through owned instance hooks. Normal bodies finish at EOF/full read or close; streams retain consumed fragments and native partial data when an error follows. Unconsumed bodies do not claim a completed result.

Known native JSON retains complete histories, schemas, tool IDs/arguments, false/zero and dense/sparse vectors. Fragmented JSON/NDJSON/SSE application data is assembled from actual consumed PayloadPart bytes. Native embedding records map to embedding spans; unknown ML payloads remain tasks. Async submission preserves its actual response fields without inventing an inference result or submission state. Current session/routing response fields and native request selectors are retained in scoped metadata. Endpoint names are not fabricated model names; source model, usage, cache/reasoning and explicit totals are mapped only when present. Native configured OTel attribute limits can bound convenience indexed attributes; complete canonical bodies are written last.

capture_content=False, canonical content-disabled context, supported legacy flags, TRACELOOP_TRACE_CONTENT=false or RESPAN_TRACE_CONTENT=false omit owned content and error messages. Ambient/supplied, initial, active/finished ancestor, unknown local parent and runtime context exits are bounded irreversibly. Sampling and instrumentation suppression precede content inspection. Unknown conversion hooks/iterators and opaque request streams are not read solely for tracing. Credential values are redacted while schemas and valid encoded JSON retain their structure.

Observer faults preserve native outcomes and release owned hooks/contexts. Shared activation/configuration and foreign wrappers/processors retain their ownership. The released SDK/constants and AI semantic-convention floors are verified by installed native tests and a wheel built from the sdist. The companion examples default to controlled local SDK transports; hosted permissions and arbitrary custom model protocols are separate checks. Stored backend projections require exact same-run inspection and are not repaired with ingestion aliases.

Metadata

Release files for respan-instrumentation-sagemaker 0.2.0

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

Source distribution (sdist)

Source distribution for respan-instrumentation-sagemaker 0.2.0
File Size Uploaded Provenance Actions
respan_instrumentation_sagemaker-0.2.0.tar.gz 14.3 kB With provenance Details for respan_instrumentation_sagemaker-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for respan-instrumentation-sagemaker 0.2.0
File Interpreter ABI Platform Actions
respan_instrumentation_sagemaker-0.2.0-py3-none-any.whl Python 3 none any Details for respan_instrumentation_sagemaker-0.2.0-py3-none-any.whl

Total release size: 31.1 kB

Release files / respan_instrumentation_sagemaker-0.2.0.tar.gz

Download URL respan_instrumentation_sagemaker-0.2.0.tar.gz
Size 14.3 kB
Tags Source
SHA-256 checksum
How to use checksums
b7d4a20d9d7284ce3484aa1416f73df7cc97f1288a97f4640a08eae8665f6fc9
BLAKE2b-256 checksum
How to use checksums
cd6c0522ec2edf93eac963962da4c9a3e25b689d530310abd2774539c68b15bf
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 Oct 13, 2026.

Transparency log

Release files / respan_instrumentation_sagemaker-0.2.0-py3-none-any.whl

Download URL respan_instrumentation_sagemaker-0.2.0-py3-none-any.whl
Size 16.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fb650b7fb964819337b593e9ae6d34033512609ca80c8021dcf221d3a32e019d
BLAKE2b-256 checksum
How to use checksums
1590808f46502fd29e2cfe505892c8305a5971d50cf88803f8f960926eeea3a6
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 Oct 13, 2026.

Transparency log

Security for respan-instrumentation-sagemaker 0.2.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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for respan_instrumentation_sagemaker-0.2.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 Oct 13, 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