What’s the difference between Databricks’s Overwatch and System Tables tools?
<p>Databricks recently released <a href="https://docs.databricks.com/en/administration-guide/system-tables/index.html#enable-system-tables" rel="noopener ugc nofollow" target="_blank">System Tables</a>, to help users understand and monitor their usage. They also had the older and more skunk works project called <a href="https://databrickslabs.github.io/overwatch/" rel="noopener ugc nofollow" target="_blank">Overwatch</a>, which also provides usage and infrastructure information. So what’s the difference between the two? When should I use either one? Let’s dive in!</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/0*HMbvwVsQt_29PbMb" style="height:467px; width:700px" /></p>
<p>Image from: <a href="https://www.pexels.com/@olly/" rel="noopener ugc nofollow" target="_blank">Andrea Piacquadio</a></p>
<h2><strong>Introduction</strong></h2>
<p>Databricks as a whole is a complex ecosystem from both technical compute intricacies to confusing pricing structures. As a user, you likely have questions such as: What are my spark jobs doing? How high is my utilization and is it efficient? Who are the other users on my account and what are their compute costs? Which tables are they accessing?</p>
<p><a href="https://blog.det.life/whats-the-difference-between-databricks-s-overwatch-and-system-tables-tools-f9d0cd75a2f2"><strong>Learn More</strong></a></p>