
Dbr Logs Marketplace
Pull Databricks job logs into Claude Code so you can debug failed runs and pipeline issues without switching to the Databricks UI alone.
Overview
dbr-logs-marketplace is a plugin marketplace for the Operate phase that adds a Claude Code plugin to fetch and analyze Databricks job logs.
What is this marketplace?
- dbr-logs plugin fetches Databricks job logs from within Claude Code
- Supports analyze-style workflows on job output for faster incident triage
- Single-plugin marketplace (dbr-logs v1.0.0) from Zencity
- Focused integration—not a general data lake explorer
- Marketplace lists 1 plugin (dbr-logs)
- Plugin version 1.0.0 in marketplace manifest
Community signal: 2 GitHub stars.
What problem does it solve?
When a Databricks job fails, hopping between the workspace UI and your coding agent slows root-cause analysis.
Who is it for?
Solo builders and small teams on Databricks who debug jobs from Claude Code and want log context in the same thread as code changes.
Skip if: Teams with no Databricks footprint, or those needing full cluster metrics and APM instead of job log retrieval.
What do I get? / Deliverables
After install, you request job logs inside Claude Code and work through failures with the agent using the fetched execution output.
- Installed dbr-logs plugin (v1.0.0)
- Retrieved Databricks job log text inside the agent session
- Agent-assisted interpretation steps toward fix or rerun
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Log fetch and analysis belong to Operate when jobs already run in production or staging, not during initial idea validation. monitoring is the right shelf for a plugin specialized in retrieving and interpreting Databricks job execution logs on demand.
How it compares
Databricks job-log integration plugin, not a general MCP database browser or agent orchestration pack.
Common Questions / FAQ
Who is Dbr Logs Marketplace for?
It is for Claude Code users who run Databricks jobs and want log fetch and analysis inside the agent workflow.
When should I use Dbr Logs Marketplace?
Use it during operate and monitoring when jobs fail, retry oddly, or you need the agent to read driver and executor output without manual export.
How do I add Dbr Logs Marketplace to my agent?
Register Dbr Logs Marketplace in Claude Code, install the dbr-logs plugin, configure Databricks authentication per the plugin docs, then invoke log fetch from your session.