<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Data Vizualization on BearlyChilly</title>
    <link>https://bearlychilly.com/tags/data-vizualization/</link>
    <description>Recent content in Data Vizualization on BearlyChilly</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 25 Aug 2023 11:27:03 +0000</lastBuildDate>
    <atom:link href="https://bearlychilly.com/tags/data-vizualization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Use Splunk Base Searches in Classic XML Dashboard</title>
      <link>https://bearlychilly.com/notes/splunk---how-to-use-splunk-base-searches-in-classic-xml-dashboard/</link>
      <pubDate>Fri, 25 Aug 2023 11:27:03 +0000</pubDate>
      <guid>https://bearlychilly.com/notes/splunk---how-to-use-splunk-base-searches-in-classic-xml-dashboard/</guid>
      <description>&lt;h2 id=&#34;why-base-searches&#34;&gt;Why Base Searches?&lt;/h2&gt;
&lt;p&gt;Even when constructing a simple dashboard, you might have multiple panels that independently run their own searches within the dashboard. Splunk executes these searches separately, retrieves the results, and then displays the visualizations. This process could potentially cause the dashboard to take longer to load, as each panel completes its search individually. If these panels are based on the same initial data, utilizing a base search becomes advantageous. With a base search, the search runs once when the dashboard loads, passing its results to the panels. The panels then carry out post-processing before presenting the visualizations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
