<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to create Databricks Jobs Monitoring in your custom Databricks App in MVP Articles</title>
    <link>https://community.databricks.com/t5/mvp-articles/how-to-create-databricks-jobs-monitoring-in-your-custom/m-p/158068#M205</link>
    <description>&lt;P&gt;&lt;SPAN&gt;If you run dozens of scheduled jobs on Databricks, you already know the two native options for catching failures — email/Teams alerts and the Monitoring dashboard — both let you down at scale. You forget to wire up alerts on new jobs, and the dashboard only shows the &lt;/SPAN&gt;&lt;SPAN class=""&gt;last five runs&lt;/SPAN&gt;&lt;SPAN&gt; across &lt;/SPAN&gt;&lt;SPAN class=""&gt;too many pages&lt;/SPAN&gt;&lt;SPAN&gt;. So I built a small &lt;/SPAN&gt;&lt;SPAN class=""&gt;Streamlit Databricks App&lt;/SPAN&gt;&lt;SPAN&gt; that talks to the &lt;/SPAN&gt;&lt;SPAN class=""&gt;Jobs API via the SDK&lt;/SPAN&gt;&lt;SPAN&gt;, pulls every job into a single view, and — the part I actually care about — &lt;/SPAN&gt;&lt;SPAN class=""&gt;normalizes every schedule into one timezone&lt;/SPAN&gt;&lt;SPAN&gt;. It runs &lt;/SPAN&gt;&lt;SPAN class=""&gt;for free locally&lt;/SPAN&gt;&lt;SPAN&gt; through the Databricks CLI (no cluster needed). The code is open source. Here's what it does and how to deploy it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;You're an active Databricks user with a few dozen scheduled jobs. By default there are exactly two ways to know when a job fails:&lt;/DIV&gt;&lt;OL class=""&gt;&lt;LI&gt;Set up&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;alerts&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(email / Teams) — per job.&lt;/LI&gt;&lt;LI&gt;Open the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Monitoring dashboard&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in Databricks.&lt;/LI&gt;&lt;/OL&gt;&lt;DIV class=""&gt;Both have the same failure mode at scale. You &lt;SPAN class=""&gt;forget&lt;/SPAN&gt; to configure alerts on some jobs, so failures go silent. And the native dashboard only displays the &lt;SPAN class=""&gt;last five runs&lt;/SPAN&gt;, spread across a &lt;SPAN class=""&gt;lot of pages&lt;/SPAN&gt; to click through. When you own dozens of jobs, that's not a control panel it's a maze.&lt;/DIV&gt;&lt;DIV class=""&gt;Databricks is like a construction kit: once you understand how it works, you can bolt on custom solutions to automate the boring parts. So I used a &lt;SPAN class=""&gt;Databricks App&lt;/SPAN&gt; to build a more usable dashboard.&lt;/DIV&gt;&lt;P&gt;&lt;A title="link to the post" href="https://medium.com/data-engineer-things/databricks-jobs-monitoring-in-your-custom-databricks-app-67c81014473f" target="_blank" rel="noopener"&gt;link to the post&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A title="link to the Repo in GitHub" href="https://github.com/protmaks/databricks_app_jobs_admin_streamlit" target="_blank" rel="noopener"&gt;link to the Repo in GitHub&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dtbr_jobsm.jpg" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/27451iF66ACA28DF1C9310/image-size/large?v=v2&amp;amp;px=999" role="button" title="dtbr_jobsm.jpg" alt="dtbr_jobsm.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jun 2026 17:04:45 GMT</pubDate>
    <dc:creator>protmaks</dc:creator>
    <dc:date>2026-06-01T17:04:45Z</dc:date>
    <item>
      <title>How to create Databricks Jobs Monitoring in your custom Databricks App</title>
      <link>https://community.databricks.com/t5/mvp-articles/how-to-create-databricks-jobs-monitoring-in-your-custom/m-p/158068#M205</link>
      <description>&lt;P&gt;&lt;SPAN&gt;If you run dozens of scheduled jobs on Databricks, you already know the two native options for catching failures — email/Teams alerts and the Monitoring dashboard — both let you down at scale. You forget to wire up alerts on new jobs, and the dashboard only shows the &lt;/SPAN&gt;&lt;SPAN class=""&gt;last five runs&lt;/SPAN&gt;&lt;SPAN&gt; across &lt;/SPAN&gt;&lt;SPAN class=""&gt;too many pages&lt;/SPAN&gt;&lt;SPAN&gt;. So I built a small &lt;/SPAN&gt;&lt;SPAN class=""&gt;Streamlit Databricks App&lt;/SPAN&gt;&lt;SPAN&gt; that talks to the &lt;/SPAN&gt;&lt;SPAN class=""&gt;Jobs API via the SDK&lt;/SPAN&gt;&lt;SPAN&gt;, pulls every job into a single view, and — the part I actually care about — &lt;/SPAN&gt;&lt;SPAN class=""&gt;normalizes every schedule into one timezone&lt;/SPAN&gt;&lt;SPAN&gt;. It runs &lt;/SPAN&gt;&lt;SPAN class=""&gt;for free locally&lt;/SPAN&gt;&lt;SPAN&gt; through the Databricks CLI (no cluster needed). The code is open source. Here's what it does and how to deploy it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;You're an active Databricks user with a few dozen scheduled jobs. By default there are exactly two ways to know when a job fails:&lt;/DIV&gt;&lt;OL class=""&gt;&lt;LI&gt;Set up&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;alerts&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(email / Teams) — per job.&lt;/LI&gt;&lt;LI&gt;Open the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Monitoring dashboard&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in Databricks.&lt;/LI&gt;&lt;/OL&gt;&lt;DIV class=""&gt;Both have the same failure mode at scale. You &lt;SPAN class=""&gt;forget&lt;/SPAN&gt; to configure alerts on some jobs, so failures go silent. And the native dashboard only displays the &lt;SPAN class=""&gt;last five runs&lt;/SPAN&gt;, spread across a &lt;SPAN class=""&gt;lot of pages&lt;/SPAN&gt; to click through. When you own dozens of jobs, that's not a control panel it's a maze.&lt;/DIV&gt;&lt;DIV class=""&gt;Databricks is like a construction kit: once you understand how it works, you can bolt on custom solutions to automate the boring parts. So I used a &lt;SPAN class=""&gt;Databricks App&lt;/SPAN&gt; to build a more usable dashboard.&lt;/DIV&gt;&lt;P&gt;&lt;A title="link to the post" href="https://medium.com/data-engineer-things/databricks-jobs-monitoring-in-your-custom-databricks-app-67c81014473f" target="_blank" rel="noopener"&gt;link to the post&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A title="link to the Repo in GitHub" href="https://github.com/protmaks/databricks_app_jobs_admin_streamlit" target="_blank" rel="noopener"&gt;link to the Repo in GitHub&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dtbr_jobsm.jpg" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/27451iF66ACA28DF1C9310/image-size/large?v=v2&amp;amp;px=999" role="button" title="dtbr_jobsm.jpg" alt="dtbr_jobsm.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2026 17:04:45 GMT</pubDate>
      <guid>https://community.databricks.com/t5/mvp-articles/how-to-create-databricks-jobs-monitoring-in-your-custom/m-p/158068#M205</guid>
      <dc:creator>protmaks</dc:creator>
      <dc:date>2026-06-01T17:04:45Z</dc:date>
    </item>
  </channel>
</rss>

