--- title: Turn Databricks telemetry into actionable decisions with... description: The Databricks Workspace extension for Dynatrace unifies telemetry from across the Databricks platform into a single correlated view. It covers job and Spark... canonical: https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Turn Databricks telemetry into actionable decisions with Dynatrace | daily.dev og:description: The Databricks Workspace extension for Dynatrace unifies telemetry from across the Databricks platform into a single correlated view. It covers job and Spark... og:url: https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt og:image: https://api.daily.dev/og/posts/T6VR2eIbt.png og:image:alt: Turn Databricks telemetry into actionable decisions with Dynatrace og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Turn Databricks telemetry into actionable decisions with Dynatrace **[Dynatrace](https://daily.dev/sources/dynatrace)** · 6 min read · 1 upvotes · 0 comments ## Summary The Databricks Workspace extension for Dynatrace unifies telemetry from across the Databricks platform into a single correlated view. It covers job and Spark reliability (distributed traces, task-level metrics, duration breakdowns), cost and capacity optimization (billing data enriched with workload metadata, right-sizing recommendations based on real utilization percentiles), AI-serving observability (request latency, token usage, requester breakdowns for chargeback), and audit log investigation (filtering by IP, service, user, and status code). Six bundled dashboards — workspace overview, job runs, cluster resource usage, cost management, AI gateway/model serving, and audit logs — provide immediate visibility without custom setup. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What metrics does the Dynatrace Databricks Workspace extension collect for job monitoring? The extension collects job success rate, run count, queue/setup/execution/cleanup durations, active and completed run visibility, task-level distributed traces per job run, and Spark-level metrics including failed tasks, stage throughput, shuffle pressure, and executor health. The duration breakdown lets teams pinpoint whether a slowdown originates in the queue, during setup, or mid-execution without re-running the entire job. _Teams troubleshooting Databricks job failures track these signals alongside the rest of their stack on daily.dev._ ### How can I identify which Databricks workloads are causing cost spikes? The Dynatrace Databricks Workspace extension ingests billing system table data and enriches it with workload metadata, letting you trace a cost spike to a specific job, cluster, SQL warehouse, notebook, model serving endpoint, instance pool, app, or pipeline. The Cluster Resource Utilization dashboard flags over-provisioned clusters with concrete recommendations derived from actual CPU and memory utilization percentiles. _Engineers making Databricks right-sizing decisions find cost optimization discussions like this on daily.dev._ ## Similar posts on daily.dev - [Monitor Databricks with Datadog](https://daily.dev/posts/monitor-databricks-with-datadog-giqfytj4u) · Datadog · 0 upvotes · 0 comments - [Databricks’ native monitoring resources](https://daily.dev/posts/databricks-native-monitoring-resources-rwbjvjawj) · Datadog · 0 upvotes · 0 comments - [Monitor Databricks with Grafana Cloud for instant visibility into your workloads](https://daily.dev/posts/monitor-databricks-with-grafana-cloud-for-instant-visibility-into-your-workloads-fmsak5z0j) · Grafana Labs · 0 upvotes · 0 comments - [Data in context: How Dynatrace solves the OpenTelemetry analytics challenge](https://daily.dev/posts/data-in-context-how-dynatrace-solves-the-opentelemetry-analytics-challenge-rvkxvqqde) · Dynatrace · 0 upvotes · 0 comments - [Collaborative Analytics on Databricks](https://daily.dev/posts/collaborative-analytics-on-databricks-wqmlkuwc9) · databricks · 0 upvotes · 0 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#observability](https://daily.dev/tags/observability), [#databricks](https://daily.dev/tags/databricks), [#finops](https://daily.dev/tags/finops) [View this post on daily.dev](https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Turn Databricks telemetry into actionable decisions with Dynatrace","url":"https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt"},"datePublished":"2026-08-11T12:45:38.454Z","dateModified":"2026-09-13T21:33:45.653Z","description":"The Databricks Workspace extension for Dynatrace unifies telemetry from across the Databricks platform into a single correlated view. It covers job and Spark...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/084da6d5acba698a834560a30cd5055d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/084da6d5acba698a834560a30cd5055d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Dynatrace","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Dynatrace","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3ca5a9897e9748f4a39fa9736389609e","url":"https://daily.dev/sources/dynatrace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devops,observability,databricks,finops","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Dynatrace","item":"https://daily.dev/sources/dynatrace"},{"@type":"ListItem","position":3,"name":"Turn Databricks telemetry into actionable decisions with Dynatrace"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/turn-databricks-telemetry-into-actionable-decisions-with-dynatrace-t6vr2eibt#faq","mainEntity":[{"@type":"Question","name":"What metrics does the Dynatrace Databricks Workspace extension collect for job monitoring?","acceptedAnswer":{"@type":"Answer","text":"The extension collects job success rate, run count, queue/setup/execution/cleanup durations, active and completed run visibility, task-level distributed traces per job run, and Spark-level metrics including failed tasks, stage throughput, shuffle pressure, and executor health. The duration breakdown lets teams pinpoint whether a slowdown originates in the queue, during setup, or mid-execution without re-running the entire job. Teams troubleshooting Databricks job failures track these signals alongside the rest of their stack on daily.dev."}},{"@type":"Question","name":"How can I identify which Databricks workloads are causing cost spikes?","acceptedAnswer":{"@type":"Answer","text":"The Dynatrace Databricks Workspace extension ingests billing system table data and enriches it with workload metadata, letting you trace a cost spike to a specific job, cluster, SQL warehouse, notebook, model serving endpoint, instance pool, app, or pipeline. The Cluster Resource Utilization dashboard flags over-provisioned clusters with concrete recommendations derived from actual CPU and memory utilization percentiles. Engineers making Databricks right-sizing decisions find cost optimization discussions like this on daily.dev."}}]} ```