<?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 Base Searches for Dashboards using Splunk Metrics in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Base-Searches-for-Dashboards-using-Splunk-Metrics/m-p/466415#M80344</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;My team recently got metric data into Splunk and I created several dashboards with various drop down tokens for metric names as well as host.  My next step was to try and create a logical base search with post processing searches to reduce the amount of concurrent searches running within the panels.  I've been having a heck of a time getting a proper base search to work when it struck me:&lt;/P&gt;

&lt;P&gt;These metric searches on the panels almost always complete in 1 second and there aren't too many metric points being generated per day.  Are base searches even worth it for this type of data?  I know that base searches is a best practice for dashboards, but these panels still load almost instantly even when concurrent dashboards are being run. Trying to get some potential insight before I go down rabbit holes again to get a base search and post processing searches to work.&lt;/P&gt;

&lt;P&gt;Appreciate any feedback &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 03 Apr 2020 13:27:26 GMT</pubDate>
    <dc:creator>splunkninga2</dc:creator>
    <dc:date>2020-04-03T13:27:26Z</dc:date>
    <item>
      <title>Base Searches for Dashboards using Splunk Metrics</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Base-Searches-for-Dashboards-using-Splunk-Metrics/m-p/466415#M80344</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;My team recently got metric data into Splunk and I created several dashboards with various drop down tokens for metric names as well as host.  My next step was to try and create a logical base search with post processing searches to reduce the amount of concurrent searches running within the panels.  I've been having a heck of a time getting a proper base search to work when it struck me:&lt;/P&gt;

&lt;P&gt;These metric searches on the panels almost always complete in 1 second and there aren't too many metric points being generated per day.  Are base searches even worth it for this type of data?  I know that base searches is a best practice for dashboards, but these panels still load almost instantly even when concurrent dashboards are being run. Trying to get some potential insight before I go down rabbit holes again to get a base search and post processing searches to work.&lt;/P&gt;

&lt;P&gt;Appreciate any feedback &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2020 13:27:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Base-Searches-for-Dashboards-using-Splunk-Metrics/m-p/466415#M80344</guid>
      <dc:creator>splunkninga2</dc:creator>
      <dc:date>2020-04-03T13:27:26Z</dc:date>
    </item>
  </channel>
</rss>

