<?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 Ideas for effective use of having 65 parsers in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Ideas-for-effective-use-of-having-65-parsers/m-p/579010#M10984</link>
    <description>&lt;P&gt;I have a dashboard with 65 panels (all are parsers). It is taking a while to load. I am having 4 base searches to use across the 65 panels, still I am facing some lag in loading the entire dashboard.&amp;nbsp;&lt;/P&gt;&lt;P&gt;For a better viewability, I categorized the panels based on their utility and showing them in tabs using CSS.&lt;/P&gt;&lt;P&gt;For for performance perspective, I dont find any other option other then using Base Search, but it isn't helping me either.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please provide effective ideas for improving the performance without recuding the number of panels involved.&lt;/P&gt;</description>
    <pubDate>Tue, 21 Dec 2021 12:02:38 GMT</pubDate>
    <dc:creator>Naren26</dc:creator>
    <dc:date>2021-12-21T12:02:38Z</dc:date>
    <item>
      <title>Ideas for effective use of having 65 parsers</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Ideas-for-effective-use-of-having-65-parsers/m-p/579010#M10984</link>
      <description>&lt;P&gt;I have a dashboard with 65 panels (all are parsers). It is taking a while to load. I am having 4 base searches to use across the 65 panels, still I am facing some lag in loading the entire dashboard.&amp;nbsp;&lt;/P&gt;&lt;P&gt;For a better viewability, I categorized the panels based on their utility and showing them in tabs using CSS.&lt;/P&gt;&lt;P&gt;For for performance perspective, I dont find any other option other then using Base Search, but it isn't helping me either.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please provide effective ideas for improving the performance without recuding the number of panels involved.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 12:02:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Ideas-for-effective-use-of-having-65-parsers/m-p/579010#M10984</guid>
      <dc:creator>Naren26</dc:creator>
      <dc:date>2021-12-21T12:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Ideas for effective use of having 65 parsers</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Ideas-for-effective-use-of-having-65-parsers/m-p/579018#M10985</link>
      <description>&lt;P&gt;65 panels is a lot for anyone to have to monitor.&amp;nbsp; If you won't reduce the number of panels then consider splitting the dashboard into several separate dashboards (one per tab, perhaps).&lt;/P&gt;&lt;P&gt;Consider moving some of the searches to scheduled searches and have the dashboard use the &lt;FONT face="courier new,courier"&gt;loadjob&lt;/FONT&gt; command to invoke the search.&amp;nbsp; The search will run outside the dashboard and the results will be saved until someone runs the dashboard then the latest results will be retrieved and shown.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 13:45:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Ideas-for-effective-use-of-having-65-parsers/m-p/579018#M10985</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-12-21T13:45:09Z</dc:date>
    </item>
  </channel>
</rss>

