[bot] Instrument Baseten Performance Client (87,159 weekly downloads)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- python
- Ambito
- observability
Direzione di ricerca
Start with the existing integrations under py/src/braintrust/integrations/ and the matrix in py/pyproject.toml to see how a wrapper is registered, then check py/noxfile.py for the session pattern. The issue lists five sync/async PerformanceClient entrypoints that need spans, so decide which ones to cover first. Done means a traced test session that runs against the package, but the scope and approach need maintainer input first.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
baseten-performance-client (import name baseten_performance_client) is Baseten's dedicated high-throughput Python client for embeddings, reranking, and classification inference against Baseten-hosted models. It is a Rust-backed (pyo3/reqwest/tokio) client distinct from both the general-purpose baseten management SDK and from calling Baseten endpoints through an OpenAI-compatible interface. This repository has zero instrumentation for it — no integration directory, wrapper, nox session, or matrix entry, and not even an incidental mention anywhere under py/.
This is a distinct execution surface from Braintrust's existing Baseten support: Braintrust currently only documents Baseten as a gateway-routed model provider for chat completions (see docs status below) — it does not cover this package's embeddings/reranking/classification execution API at all. It is also distinct from already-instrumented embedding/rerank libraries (cohere rerank, voyageai — itself still an open gap in #482) since it talks to Baseten-hosted deployments specifically via its own PerformanceClient class.
What is missing
The PerformanceClient class exposes paired sync/async execution entrypoints, none of which produce a Braintrust span today:
PerformanceClient.embed()/async_embed()— embedding execution against Baseten Embedding Inference deploymentsPerformanceClient.rerank()/async_rerank()— document reranking executionPerformanceClient.classify()/async_classify()— classification executionPerformanceClient.batch_system_one()/async_batch_system_one()— batched "System One" decision executionPerformanceClient.batch_post()/async_batch_post()— generic batched JSON request execution (e.g. against Engine-Builder-LLM completion endpoints)
All of these are high-concurrency batch execution calls (default max_concurrent_requests=256, configurable retries/hedging/timeouts via RequestProcessingPreference) that are the primary way applications drive bulk embedding/rerank/classification workloads through Baseten — currently entirely invisible to Braintrust tracing.
Weekly downloads
Weekly downloads: 87,159 (fetched 2026-11-02; https://pypistats.org/api/packages/baseten_performance_client/recent)
Braintrust docs status
not_found — checked:
- https://docs.braintrust.dev/integrations/ai-providers/baseten.md — scoped entirely to using Baseten as a model provider through Braintrust's gateway (
https://gateway.braintrust.dev/v1via the standard OpenAI SDK) for chat completions; does not mentionbaseten-performance-client, embeddings, reranking, or classification anywhere. - https://docs.braintrust.dev/guides/tracing/integrations — full tracing-integrations, agent-framework, eval-framework, and testing-framework lists checked; no mention of Baseten in any form.
Upstream sources
- GitHub: https://github.com/basetenlabs/truss/tree/main/baseten-performance-client
- PyPI: https://pypi.org/project/baseten-performance-client/ (current version 0.1.16, bumped ~2026-10-24 per release history: https://github.com/riseproject-dev/python-wheels/pull/3577)
- Docs: https://docs.baseten.co/reference/sdk/performance-client/overview
Local repo files inspected
py/src/braintrust/integrations/— nobaseten/directory, no file matchingbaseten*anywherepy/src/braintrust/wrappers/— no Baseten wrapperpy/pyproject.toml[tool.braintrust.matrix]— nobasetenentrypy/noxfile.py— notest_basetensession- Repo-wide case-insensitive grep for
basetenunderpy/— zero matches of any kind (not even incidental)
- Lingua principale
- Python
- Stelle
- 22
- Fork
- 30
- Merge medio
- 9h
- PR unite (30g)
- 128
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di braintrustdata/braintrust-sdk-python
-
Temporal: add `workflow.Info.original_execution_run_id` to workflow span metadataForse già presa @Mohith26 l’ha presa 4 giorni fa. Apertafeature python
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
braintrustdata/braintrust-sdk-python#868 ·
I maintainer di solito rispondono entro 1 giorno
-
python
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
braintrustdata/braintrust-sdk-python#1063 ·
I maintainer di solito rispondono entro 1 giorno
-
new-integration python
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
braintrustdata/braintrust-sdk-python#999 ·
I maintainer di solito rispondono entro 1 giorno
-
python
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
braintrustdata/braintrust-sdk-python#957 ·
I maintainer di solito rispondono entro 1 giorno
-
python
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
braintrustdata/braintrust-sdk-python#956 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di braintrustdata/braintrust-sdk-python
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
aws-samples/sample-per-model-bedrock#795 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno
-
Pretalx reports older version to be the latest release than what is actually installed and availableAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
micropython/micropython#19906 ·
I maintainer di solito rispondono entro 1 giorno