respan-instrumentation-pinecone
Respan instrumentation for Pinecone data, control-plane, and inference operations, including the synchronous, asynchronous, and gRPC clients.
pip install respan-ai respan-instrumentation-pinecone pinecone
from pinecone import Pinecone
from respan import Respan
from respan_instrumentation_pinecone import PineconeInstrumentor
respan = Respan(instrumentations=[PineconeInstrumentor()])
index = Pinecone().index(name="documents")
print(index.query(vector=[0.1, 0.2], top_k=3))
respan.flush()
Supported SDKs and operations
The adapter supports Pinecone 5.1 through 10.x. The legacy sync vector client
remains instrumented. Pinecone 10 adds document upsert, batch upsert, search,
fetch, update, delete, and listing for both sync and async clients. Listing
preserves the SDK paginator, including pages(), to_list(), and pagination
tokens. Each fetched page produces a span; creating a paginator does not issue
a request or emit a completed request span.
Document responses preserve fields from Pinecone's msgspec structs and document
models in canonical entity output. Existing content capture limits and redaction
still apply. Set PineconeInstrumentor(capture_content=False) to omit inputs and
outputs. Error spans keep the service status while the original exception is
raised to the caller.
Compatibility tests use the released SDK against a local HTTP fixture. A live Pinecone service requires an existing index and provider credentials.
Async vector, namespace, and bulk-import iterators remain lazy, record one span per consumed iterator, and finalize on early close or errors. Control-plane index listing retains its native paginator. Existing gRPC patch targets remain; this compatibility suite validates HTTP clients and does not exercise a gRPC service.
See the Python Pinecone examples for complete deterministic scenarios.
Metadata
Release files for respan-instrumentation-pinecone 0.2.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 |
|---|---|---|---|---|
| respan_instrumentation_pinecone-0.2.0.tar.gz | 10.6 kB | With provenance | Details for respan_instrumentation_pinecone-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| respan_instrumentation_pinecone-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for respan_instrumentation_pinecone-0.2.0-py3-none-any.whl |
Total release size: 22.7 kB
Release files / respan_instrumentation_pinecone-0.2.0.tar.gz
| Download URL | respan_instrumentation_pinecone-0.2.0.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86a4c186ade132b3c5e049e550355d2e6776970501e6791eab7c098d938d73d3
|
|
BLAKE2b-256 checksum How to use checksums |
fbd92d69947345032684d9ac37b33a382d58df51e3d9de5182a7013146595e9b
|
| 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 logRelease files / respan_instrumentation_pinecone-0.2.0-py3-none-any.whl
| Download URL | respan_instrumentation_pinecone-0.2.0-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a83e4f0b158ee7038d76d397c15855e4f0221073e444b31dd04187577eee7a8
|
|
BLAKE2b-256 checksum How to use checksums |
a3060b45cd8a8f2bedf7a03da59056e91d057208cf979238b84bea1174350214
|
| 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 logSecurity for respan-instrumentation-pinecone 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.
Attestation for respan_instrumentation_pinecone-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 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.