[bot] Add Replicate Python SDK native integration for run, stream, and predictions execution instrumentation (345,748 weekly downloads)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
從 py/src/braintrust/integrations/ 下現有的整合、py/src/braintrust/wrappers/ 下的 wrapper,以及 py/src/braintrust/auto.py、integrations/init.py、versioning.py、py/noxfile.py 和 pyproject.toml 中的註冊點開始。先了解現有 provider integration 如何處理 run、stream、async 和 prediction API,再定義 Replicate integration。完成內容應涵蓋列出的執行介面、測試、註冊,以及提議的 span 欄位和指標。
由索引模型根據 Issue 內容生成。
描述
Summary
The Replicate Python SDK (replicate) is the official Python client for Replicate, a platform for running AI models (LLMs, image generation, video, audio, and more) in the cloud. Its replicate.run() and replicate.predictions.create() APIs are the primary execution surfaces. The latest release is v1.0.7 (May 27, 2026). This repository has zero native instrumentation for any replicate SDK execution surface — no integration directory, no wrapper, no patcher, no auto_instrument() support.
Braintrust documents a gateway/proxy-based integration with Replicate where users route Replicate calls through the Braintrust gateway using an OpenAI-compatible client. This approach does not cover users of the native replicate Python SDK, which has its own distinct API (replicate.run("owner/model", input={...})). The replicate SDK is not an openai.OpenAI subclass and cannot be wrapped with wrap_openai().
The same pattern exists for other providers in this repo: Mistral, OpenRouter, xAI, Groq, and Together AI all have OpenAI-compatible endpoints, yet received dedicated native integrations because users following official provider documentation and pip install <provider> get zero Braintrust tracing from the OpenAI wrapper alone.
What needs to be instrumented
The replicate package (v1.0.7) exposes these execution surfaces, none of which are instrumented:
Model execution (highest priority)
| API | Description | Return type |
|---|---|---|
replicate.run(model, input, ...) |
Synchronously run a model and return the complete output | Any (model-specific: str, list, FileOutput, ...) |
replicate.stream(model, input, ...) |
Stream model output as server-sent events — primarily for LLM token streaming | Iterator[ServerSentEvent] |
replicate.run() accepts any Replicate model identifier (e.g., "meta/meta-llama-3-8b-instruct", "stability-ai/sdxl") and an input dict with model-specific parameters. The model identifier encodes the provider and model name — useful for span metadata.
LLM streaming: For language models, replicate.run() returns an iterator yielding text tokens. replicate.stream() provides SSE-based streaming for the same use case.
Async execution
| API | Description | Return type |
|---|---|---|
await replicate.async_run(model, input, ...) |
Async equivalent of replicate.run() |
Any |
Background predictions
| API | Description | Return type |
|---|---|---|
replicate.predictions.create(model, input, ...) |
Create a prediction without waiting for it to complete | Prediction |
await replicate.predictions.async_create(model, input, ...) |
Async prediction creation | Prediction |
prediction.wait() |
Wait for a prediction to complete | Prediction |
Prediction objects expose .status, .output, .logs, .metrics (includes predict_time), .urls (cancel, get, stream webhooks).
Implementation notes
Generic execution model: Unlike OpenAI or Anthropic where model names map to a known schema, Replicate model inputs and outputs are model-specific. The integration should log the model identifier (owner/model or owner/model:version), the input dict, and the output value. Token count extraction is only possible for models that return usage metadata in their response or logs.
Model identifier: Replicate model identifiers like "meta/meta-llama-3-8b-instruct" or "stability-ai/stable-diffusion-3" encode the model type. The span should capture model (full identifier) and provider: "replicate" in metadata.
Output types: LLM models return iterators of text tokens; image models return FileOutput objects; other models may return strings, numbers, lists, or dicts. The integration should handle all cases, collecting token text for LLM outputs and logging output metadata (type, size if file) for others.
Streaming LLM output: replicate.run() for LLM models returns a generator. The span should be created before iteration starts and finalized (with full output text) when iteration completes. replicate.stream() follows the same pattern with SSE events.
predict_time metric: Prediction.metrics["predict_time"] provides server-side inference time in seconds — a useful span metric.
Client pattern: The module-level functions (replicate.run()) delegate to a default Client instance. Patching Client.run, Client.stream, and Client.async_run covers both usage patterns.
Authentication: Uses REPLICATE_API_TOKEN env var or explicit api_token kwarg. VCR cassettes need Authorization: Token <key> header sanitization.
Proposed span shape
| Span field | Content |
|---|---|
| input | model identifier, input dict |
| output | collected text output (LLM), null or file metadata (image/video) |
| metadata | provider: "replicate", model (full identifier), version if specified |
| metrics | predict_time from Prediction.metrics, time_to_first_token (streaming LLMs) |
No coverage in any instrumentation layer
- No integration directory (
py/src/braintrust/integrations/replicate/) - No wrapper function (e.g.
wrap_replicate()) - No patcher in any existing integration
- No nox test session (
test_replicate) - No version entry in
py/src/braintrust/integrations/versioning.py - No mention in
py/src/braintrust/integrations/__init__.py
A grep for replicate across py/src/braintrust/ returns zero matches.
Braintrust docs status
unclear — The Braintrust Replicate integration page documents a gateway/proxy approach using an OpenAI client pointed at the Braintrust gateway. This covers users who access Replicate through the OpenAI-compatible gateway endpoint but does not cover native replicate SDK users who call replicate.run() directly. There is no auto_instrument() reference and no wrap_replicate() function documented.
Upstream references
- replicate on PyPI: https://pypi.org/project/replicate/ (v1.0.7, May 27, 2026)
- replicate Python SDK on GitHub: https://github.com/replicate/replicate-python
- Replicate Python quickstart: https://replicate.com/docs/get-started/python
- Replicate API reference: https://replicate.com/docs/reference/http
- Braintrust Replicate docs (gateway approach): https://www.braintrust.dev/docs/integrations/ai-providers/replicate
Local repo files inspected
py/src/braintrust/integrations/— noreplicate/directory exists onmainpy/src/braintrust/wrappers/— no Replicate wrapperpy/noxfile.py— notest_replicatesessionpy/src/braintrust/integrations/__init__.py— Replicate not listed in integration registrypy/src/braintrust/integrations/versioning.py— no Replicate version matrixpy/pyproject.toml[tool.braintrust.matrix]— no Replicate entrypy/src/braintrust/auto.py— Replicate not listed inauto_instrument()parameters- Full repo grep for
replicateacrosspy/src/braintrust/— zero matches
- 主要語言
- Python
- 星號
- 22
- 分支
- 24
- 平均合併
- 14 小時 49 分鐘
- 30 天內合併 PR
- 126
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
braintrustdata/braintrust-sdk-python 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 77/100
braintrustdata/braintrust-sdk-python#962 ·
維護者通常 1 天內回覆
-
Temporal: add `workflow.Info.original_execution_run_id` to workflow span metadata可能已有人在做 @Ehsan-hash 於 1 天前認領。 未關閉feature python
難度 2/5 1-3 小時 新手友好度 76/100
braintrustdata/braintrust-sdk-python#868 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 20/100
braintrustdata/braintrust-sdk-python#957 ·
維護者通常 1 天內回覆
-
python
難度 5/5 一週以上 新手友好度 35/100
braintrustdata/braintrust-sdk-python#956 ·
維護者通常 1 天內回覆
-
python
braintrustdata/braintrust-sdk-python#839 ·
維護者通常 1 天內回覆
查看 braintrustdata/braintrust-sdk-python 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 64/100
aws-samples/sample-per-model-bedrock#295 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 76/100
pyrevitlabs/pyRevit#3792 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 69/100
zephyrproject-rtos/reqmgmt#177 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
polarsource/polar#15580 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 85/100
521xueweihan/HelloGitHub#4011 ·