databricks-debug-bundle

Featured

Collect Databricks debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Databricks problems. Trigger with phrases like "databricks debug", "databricks support bundle", "collect databricks logs", "databricks diagnostic".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Databricks Debug Bundle ## Current State !`databricks --version 2>/dev/null || echo 'CLI not installed'` !`python3 -c "import databricks.sdk; print(f'SDK {databricks.sdk.__version__}')" 2>/dev/null || echo 'SDK not installed'` ## Overview Collect all diagnostic information needed for Databricks support tickets: environment info, cluster state, cluster events, job run details, Spark driver logs, and Delta table history. Produces a redacted tar.gz bundle safe to share with support. ## Prerequisites - Databricks CLI installed and configured - Access to cluster logs (admin or cluster owner) - Permission to access job run details ## Instructions ### Step 1: Create Debug Collection Script ```bash #!/bin/bash set -euo pipefail # databricks-debug-bundle.sh [cluster_id] [run_id] [table_name] BUNDLE_DIR="databricks-debug-$(date +%Y%m%d-%H%M%S)" mkdir -p "$BUNDLE_DIR" CLUSTER_ID="${1:-}" RUN_ID="${2:-}" TABLE_NAME="${3:-}" echo "=== Databricks Debug Bundle ===" | tee "$BUNDLE_DIR/summary.txt" echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE_DIR/summary.txt" echo "Workspace: ${DATABRICKS_HOST:-unset}" >> "$BUNDLE_DIR/summary.txt" ``` ### Step 2: Collect Environment Info ```bash { echo "" echo "--- Environment ---" echo "CLI: $(databricks --version 2>&1)" echo "SDK: $(pip show databricks-sdk 2>/dev/null | grep Version || echo 'not installed')" echo "Python: $(python3 --version 2>&1)" echo "OS: $(uname -srm)" echo "" echo "--- Current ...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

klaviyo-debug-bundle

Collect Klaviyo debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Klaviyo API problems. Trigger with phrases like "klaviyo debug", "klaviyo support bundle", "collect klaviyo logs", "klaviyo diagnostic", "klaviyo troubleshoot".

2,266 Updated today
jeremylongshore
AI & Automation Featured

brightdata-debug-bundle

Collect Bright Data debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Bright Data problems. Trigger with phrases like "brightdata debug", "brightdata support bundle", "collect brightdata logs", "brightdata diagnostic".

2,266 Updated today
jeremylongshore
AI & Automation Solid

clari-debug-bundle

Collect Clari API diagnostic info for support cases. Use when preparing a support ticket, collecting API response samples, or documenting integration issues. Trigger with phrases like "clari debug", "clari support bundle", "collect clari diagnostics", "clari troubleshoot".

2,266 Updated today
jeremylongshore
AI & Automation Featured

elevenlabs-debug-bundle

Collect ElevenLabs debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for ElevenLabs problems. Trigger: "elevenlabs debug", "elevenlabs support bundle", "collect elevenlabs logs", "elevenlabs diagnostic", "elevenlabs support ticket".

2,266 Updated today
jeremylongshore
AI & Automation Featured

replit-debug-bundle

Collect Replit diagnostic info for debugging deployments, workspace issues, and support tickets. Use when encountering persistent issues, preparing support tickets, or collecting system state for troubleshooting Replit problems. Trigger with phrases like "replit debug", "replit support bundle", "collect replit logs", "replit diagnostic", "replit troubleshoot".

2,266 Updated today
jeremylongshore