Skip to content

docs(observability): add end-to-end Databricks Zerobus quickstart - #1729

Merged
yassin-berriai merged 8 commits into
mainfrom
litellm_zerobus_docs
Sep 25, 2026
Merged

yassin-berriai merged 8 commits into
mainfrom
litellm_zerobus_docs

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds a complete quickstart for connecting an existing cloud-deployed LiteLLM Gateway to Databricks Zerobus. Readers identify their workspace endpoints, create the Delta table, grant service principal access, configure the deployed gateway, send a request using a scoped virtual key, and verify its response ID in Databricks SQL.

Provides selectable Python, JavaScript, and cURL request examples using an HTTPS gateway base URL and a scoped virtual key. Uses existing model aliases, organization-configured Admin UI authentication, and deployment-managed secrets. YAML changes preserve the existing gateway configuration and apply to every replica. The guide assumes the integration is available and does not require readers to install or start a local gateway.

Includes a React architecture diagram following the production deployment guide's component styling, with the LiteLLM train and Databricks and model-provider brand marks. Six screenshots show the real Databricks and LiteLLM interfaces, including the SQL query returning the verified response ID, status, token counts, and cost. The OAuth secret is masked. Documents both YAML and Admin UI setup, the canonical 41-column schema with VARIANT fields, SQL reader permissions, privacy controls, buffering and retry limits, and actionable troubleshooting. The Admin UI currently registers successful events; YAML callbacks enable both successful and failed model-call logging.

Validation

Live requests against a Databricks model-serving endpoint were read back from the Unity Catalog table through the Databricks SQL Statements API. YAML configuration produced matching normal, failed, and streaming traces. The callback saved through the Admin UI produced matching normal and streaming traces, with the expected success-only subscription. Response IDs, token counts, costs, and the streaming flag were checked. The exact successful request was also queried in Databricks SQL Editor and captured for the verification step.

npm run build, the focused documentation structural check, the writing-style check, and git diff --check pass. The built page was reviewed in Chrome, including the embedded screenshots and switching among all three request tabs. Python, JavaScript, and shell examples pass syntax checks.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
litellm Ready Ready Preview Sep 25, 2026 10:24pm UTC

Request Review

…oubleshooting

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@yassin-berriai yassin-berriai changed the title docs(observability): add Databricks Zerobus trace logging callback docs(observability): add end-to-end Databricks Zerobus quickstart Sep 25, 2026
@yassin-berriai
yassin-berriai enabled auto-merge (squash) September 25, 2026 22:22
@yassin-berriai
yassin-berriai merged commit 577f8dd into main Sep 25, 2026
4 checks passed
@yassin-berriai
yassin-berriai deleted the litellm_zerobus_docs branch September 25, 2026 22:24

This branch was successfully deployed

1 active deployment
Preview — 24537d11 Deployed Sep 25, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant