<?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 Re: Databricks: Report on SQL queries that are being executed in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27954#M19792</link>
    <description>&lt;P&gt;@Werner Stinckens​&amp;nbsp;is right, the API is the way to go -- for now! We want to make this a better experience for you e.g. giving you a system table you can query directly without having to extract the data with an API and re-ingest it.&lt;/P&gt;</description>
    <pubDate>Sat, 19 Feb 2022 08:39:30 GMT</pubDate>
    <dc:creator>BilalAslamDbrx</dc:creator>
    <dc:date>2022-02-19T08:39:30Z</dc:date>
    <item>
      <title>Databricks: Report on SQL queries that are being executed</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27951#M19789</link>
      <description>&lt;P&gt;We have a SQL workspace with a cluster running that services a number of self service reports against a range of datasets. We want to be able to analyse and report on the queries our self service users are executing so we can get better visibility of who is using the data platform, and what/how the tables are being used. Ideally this would be using databricks SQL workspace to do this reporting rather than using another tool.&lt;/P&gt;&lt;P&gt;All this information is available in the UI in the Query history, but this is not in a form we can easily analyse or create graphs against&lt;/P&gt;&lt;P&gt;We know there is an API to pull the query history from the UI, however it does seem convoluted to query the API to fetch data about our cluster so we can ingest into our cluster so we can query it&lt;/P&gt;&lt;P&gt;What is the best way to get query history information information into a hive table so we can query, analyse and graph it?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 05:09:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27951#M19789</guid>
      <dc:creator>enichante</dc:creator>
      <dc:date>2022-02-16T05:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks: Report on SQL queries that are being executed</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27952#M19790</link>
      <description>&lt;P&gt;The API is the way to go.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 06:48:53 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27952#M19790</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2022-02-16T06:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks: Report on SQL queries that are being executed</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27953#M19791</link>
      <description>&lt;P&gt;Agree with @Werner Stinckens​&amp;nbsp;. We built a lake pipeline to feed that data via the API into lake storage (so we could keep more query history and combine that history "across" workspaces.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 15:44:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27953#M19791</guid>
      <dc:creator>Chris_Grabiel</dc:creator>
      <dc:date>2022-02-16T15:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks: Report on SQL queries that are being executed</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27954#M19792</link>
      <description>&lt;P&gt;@Werner Stinckens​&amp;nbsp;is right, the API is the way to go -- for now! We want to make this a better experience for you e.g. giving you a system table you can query directly without having to extract the data with an API and re-ingest it.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Feb 2022 08:39:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27954#M19792</guid>
      <dc:creator>BilalAslamDbrx</dc:creator>
      <dc:date>2022-02-19T08:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks: Report on SQL queries that are being executed</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27955#M19793</link>
      <description>&lt;P&gt;Looks like the people have spoken: &lt;B&gt;API&lt;/B&gt; is your best option! (thanks @Werner Stinckens​&amp;nbsp; @Chris Grabiel​&amp;nbsp; and @Bilal Aslam​&amp;nbsp;!) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@eni chante​&amp;nbsp;Let us know if you have questions about the API! If not, please mark one of the replies above as the "best answer"! That way we know the case is closed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;.....but also we would &lt;I&gt;love&lt;/I&gt; to know what creative solutions you came up with via our API. Feel free to reply below, share the knowledge! Talk soon.  &lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 22:34:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-report-on-sql-queries-that-are-being-executed/m-p/27955#M19793</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-02-22T22:34:46Z</dc:date>
    </item>
  </channel>
</rss>

