<?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 Performance issue with the Databricks Add-on for Splunk 1.4.2 in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/performance-issue-with-the-databricks-add-on-for-splunk-1-4-2/m-p/129776#M10608</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;We are currently using the add-on for&amp;nbsp;&lt;SPAN class=""&gt;Databricks&amp;nbsp;in our on-prem Splunk Enterprise environment. The connection goes directly to the cloud without a proxy. Unfortunately, the add-on is very slow and we lose about 20 seconds with every query. We see that most of the time is lost internally in Splunk when the query has left our search head, then we also have the response from&amp;nbsp;&lt;SPAN class=""&gt;Databricks&amp;nbsp;within a second.&lt;BR /&gt;&lt;SPAN&gt;We only use the datbricksquery function.&lt;BR /&gt;Can everyone help me?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 26 Aug 2025 09:33:54 GMT</pubDate>
    <dc:creator>FalkEngelbrecht</dc:creator>
    <dc:date>2025-08-26T09:33:54Z</dc:date>
    <item>
      <title>Performance issue with the Databricks Add-on for Splunk 1.4.2</title>
      <link>https://community.databricks.com/t5/get-started-discussions/performance-issue-with-the-databricks-add-on-for-splunk-1-4-2/m-p/129776#M10608</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;We are currently using the add-on for&amp;nbsp;&lt;SPAN class=""&gt;Databricks&amp;nbsp;in our on-prem Splunk Enterprise environment. The connection goes directly to the cloud without a proxy. Unfortunately, the add-on is very slow and we lose about 20 seconds with every query. We see that most of the time is lost internally in Splunk when the query has left our search head, then we also have the response from&amp;nbsp;&lt;SPAN class=""&gt;Databricks&amp;nbsp;within a second.&lt;BR /&gt;&lt;SPAN&gt;We only use the datbricksquery function.&lt;BR /&gt;Can everyone help me?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 26 Aug 2025 09:33:54 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/performance-issue-with-the-databricks-add-on-for-splunk-1-4-2/m-p/129776#M10608</guid>
      <dc:creator>FalkEngelbrecht</dc:creator>
      <dc:date>2025-08-26T09:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue with the Databricks Add-on for Splunk 1.4.2</title>
      <link>https://community.databricks.com/t5/get-started-discussions/performance-issue-with-the-databricks-add-on-for-splunk-1-4-2/m-p/129957#M10626</link>
      <description>&lt;P&gt;It’s likely not Databricks but the Splunk add-on causing the delay. The databricksquery command in version 1.4.2 has known performance issues — most of the lag is inside Splunk while parsing results. Try upgrading to the latest add-on (1.5.x+), monitor search head resources, and if you need faster results, consider running scheduled jobs in Databricks and ingesting them into Splunk instead of live queries.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 03:21:51 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/performance-issue-with-the-databricks-add-on-for-splunk-1-4-2/m-p/129957#M10626</guid>
      <dc:creator>siennafaleiro</dc:creator>
      <dc:date>2025-08-28T03:21:51Z</dc:date>
    </item>
  </channel>
</rss>

