<?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 Splunk Performance Problems in Dashboard in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283659#M2644</link>
    <description>&lt;P&gt;Hi everyone, I'm new to Splunk and I developed a Dashboard which has 19 panels, the Dashboard it's done using post-process with a Base Search and specific queries for every Panel. I'm experiencing serious performance problems with this Dashboard, the Dashboard's Panels, when selecting 4 hours interval (for example), took about 20 minutes to finish. Can anyone help me with this? maybe it's a better way to do the Base Search or the Dashboard.&lt;/P&gt;

&lt;P&gt;I'm getting logs from a F5 equipment, specifically http logs, which are indexed by Splunk, and the Base Search and all the queries are done from this logs.&lt;BR /&gt;
The indexed rate is about 270 KB/s.&lt;/P&gt;

&lt;P&gt;I'm also working with tokens which are update with some drilldowns and I'm using some java scripting for some drilldowns.&lt;/P&gt;

&lt;P&gt;I pasted the Base Search and one of the Panel configuration.&lt;/P&gt;

&lt;P&gt;Thanks in advance,&lt;BR /&gt;
Marcelo&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;query&amp;gt;sourcetype=f5logs [search sourcetype=f5logs | iplocation src_ip | search Country=$country_tok$ | table src_ip] node=$nodes_tok$ http_status=$http_status_tok$ cookie=$cookie_tok$ http_user_agent=$ua_tok$ http_uri=$http_uri_tok$ src_ip=$ip_tok$ http_method=$http_method_tok$ ClassC=$classC_tok$ BlockReason=$block_reason_tok$ requestVcookie=$vcookie_tok$ http_uri_query=$uri_query_tok$ | fields _time, node, http_status, cookie, http_user_agent, requestVheader, http_uri, src_ip, http_method , ClassC, requestVcookie, http_uri_query, BlockReason&amp;lt;/query&amp;gt;
&amp;lt;earliest&amp;gt;$time_tok.earliest$&amp;lt;/earliest&amp;gt;
&amp;lt;latest&amp;gt;$time_tok.latest$&amp;lt;/latest&amp;gt;




&amp;lt;panel&amp;gt;
  &amp;lt;chart&amp;gt;
    &amp;lt;title&amp;gt;Http status by time&amp;lt;/title&amp;gt;
    &amp;lt;search base="baseSearch" id="subsearch1"&amp;gt;
      &amp;lt;query&amp;gt;
        timechart sum(count) by http_status
      &amp;lt;/query&amp;gt;
    &amp;lt;/search&amp;gt;
    &amp;lt;selection&amp;gt;
      &amp;lt;set token="selection_earliest_tok"&amp;gt;$start$&amp;lt;/set&amp;gt;
      &amp;lt;set token="selection_latest_tok"&amp;gt;$end$&amp;lt;/set&amp;gt;
    &amp;lt;/selection&amp;gt;
    &amp;lt;drilldown&amp;gt;
      &amp;lt;set token="http_status_tok"&amp;gt;$click.name2$&amp;lt;/set&amp;gt;
    &amp;lt;/drilldown&amp;gt;
    &amp;lt;option name="charting.chart.stackMode"&amp;gt;stacked&amp;lt;/option&amp;gt;
    &amp;lt;option name="refresh.display"&amp;gt;preview&amp;lt;/option&amp;gt;
  &amp;lt;/chart&amp;gt;
  &amp;lt;html&amp;gt;
          &amp;lt;input id="btn1" class="btnModalInfo" data-toggle="modal" data-target="#desc1" type="button" value="Detail"/&amp;gt;

  &amp;lt;!-- Modal --&amp;gt;
  &amp;lt;div class="modal fade" id="desc1" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true"&amp;gt;
      &amp;lt;div class="modal-dialog modal-lg" role="document"&amp;gt;
        &amp;lt;div class="modal-content"&amp;gt;
          &amp;lt;div class="modal-header"&amp;gt;
            &amp;lt;h4 class="modal-title" id="myModalLabel"&amp;gt;
              Http status detail view&amp;lt;/h4&amp;gt;
            &amp;lt;/div&amp;gt;
            &amp;lt;div class="modal-body"&amp;gt;
              &amp;lt;div id="table1"&amp;gt;&amp;lt;/div&amp;gt;

            &amp;lt;/div&amp;gt;
            &amp;lt;div class="modal-footer"&amp;gt;
              &amp;lt;button type="button" class="btn btn-default" data-dismiss="modal"&amp;gt;Close&amp;lt;/button&amp;gt;
            &amp;lt;/div&amp;gt;
          &amp;lt;/div&amp;gt;
        &amp;lt;/div&amp;gt;
  &amp;lt;/div&amp;gt;
&amp;lt;/html&amp;gt;
&amp;lt;/panel&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 09 Feb 2017 19:54:47 GMT</pubDate>
    <dc:creator>mpepem</dc:creator>
    <dc:date>2017-02-09T19:54:47Z</dc:date>
    <item>
      <title>Splunk Performance Problems in Dashboard</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283659#M2644</link>
      <description>&lt;P&gt;Hi everyone, I'm new to Splunk and I developed a Dashboard which has 19 panels, the Dashboard it's done using post-process with a Base Search and specific queries for every Panel. I'm experiencing serious performance problems with this Dashboard, the Dashboard's Panels, when selecting 4 hours interval (for example), took about 20 minutes to finish. Can anyone help me with this? maybe it's a better way to do the Base Search or the Dashboard.&lt;/P&gt;

&lt;P&gt;I'm getting logs from a F5 equipment, specifically http logs, which are indexed by Splunk, and the Base Search and all the queries are done from this logs.&lt;BR /&gt;
The indexed rate is about 270 KB/s.&lt;/P&gt;

&lt;P&gt;I'm also working with tokens which are update with some drilldowns and I'm using some java scripting for some drilldowns.&lt;/P&gt;

&lt;P&gt;I pasted the Base Search and one of the Panel configuration.&lt;/P&gt;

&lt;P&gt;Thanks in advance,&lt;BR /&gt;
Marcelo&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;query&amp;gt;sourcetype=f5logs [search sourcetype=f5logs | iplocation src_ip | search Country=$country_tok$ | table src_ip] node=$nodes_tok$ http_status=$http_status_tok$ cookie=$cookie_tok$ http_user_agent=$ua_tok$ http_uri=$http_uri_tok$ src_ip=$ip_tok$ http_method=$http_method_tok$ ClassC=$classC_tok$ BlockReason=$block_reason_tok$ requestVcookie=$vcookie_tok$ http_uri_query=$uri_query_tok$ | fields _time, node, http_status, cookie, http_user_agent, requestVheader, http_uri, src_ip, http_method , ClassC, requestVcookie, http_uri_query, BlockReason&amp;lt;/query&amp;gt;
&amp;lt;earliest&amp;gt;$time_tok.earliest$&amp;lt;/earliest&amp;gt;
&amp;lt;latest&amp;gt;$time_tok.latest$&amp;lt;/latest&amp;gt;




&amp;lt;panel&amp;gt;
  &amp;lt;chart&amp;gt;
    &amp;lt;title&amp;gt;Http status by time&amp;lt;/title&amp;gt;
    &amp;lt;search base="baseSearch" id="subsearch1"&amp;gt;
      &amp;lt;query&amp;gt;
        timechart sum(count) by http_status
      &amp;lt;/query&amp;gt;
    &amp;lt;/search&amp;gt;
    &amp;lt;selection&amp;gt;
      &amp;lt;set token="selection_earliest_tok"&amp;gt;$start$&amp;lt;/set&amp;gt;
      &amp;lt;set token="selection_latest_tok"&amp;gt;$end$&amp;lt;/set&amp;gt;
    &amp;lt;/selection&amp;gt;
    &amp;lt;drilldown&amp;gt;
      &amp;lt;set token="http_status_tok"&amp;gt;$click.name2$&amp;lt;/set&amp;gt;
    &amp;lt;/drilldown&amp;gt;
    &amp;lt;option name="charting.chart.stackMode"&amp;gt;stacked&amp;lt;/option&amp;gt;
    &amp;lt;option name="refresh.display"&amp;gt;preview&amp;lt;/option&amp;gt;
  &amp;lt;/chart&amp;gt;
  &amp;lt;html&amp;gt;
          &amp;lt;input id="btn1" class="btnModalInfo" data-toggle="modal" data-target="#desc1" type="button" value="Detail"/&amp;gt;

  &amp;lt;!-- Modal --&amp;gt;
  &amp;lt;div class="modal fade" id="desc1" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true"&amp;gt;
      &amp;lt;div class="modal-dialog modal-lg" role="document"&amp;gt;
        &amp;lt;div class="modal-content"&amp;gt;
          &amp;lt;div class="modal-header"&amp;gt;
            &amp;lt;h4 class="modal-title" id="myModalLabel"&amp;gt;
              Http status detail view&amp;lt;/h4&amp;gt;
            &amp;lt;/div&amp;gt;
            &amp;lt;div class="modal-body"&amp;gt;
              &amp;lt;div id="table1"&amp;gt;&amp;lt;/div&amp;gt;

            &amp;lt;/div&amp;gt;
            &amp;lt;div class="modal-footer"&amp;gt;
              &amp;lt;button type="button" class="btn btn-default" data-dismiss="modal"&amp;gt;Close&amp;lt;/button&amp;gt;
            &amp;lt;/div&amp;gt;
          &amp;lt;/div&amp;gt;
        &amp;lt;/div&amp;gt;
  &amp;lt;/div&amp;gt;
&amp;lt;/html&amp;gt;
&amp;lt;/panel&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 09 Feb 2017 19:54:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283659#M2644</guid>
      <dc:creator>mpepem</dc:creator>
      <dc:date>2017-02-09T19:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Performance Problems in Dashboard</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283660#M2645</link>
      <description>&lt;P&gt;It's not recommended to use a base search without statistics involved - stats\timechart\chart&lt;BR /&gt;
The reason is the first search causes a Splunk job to retrieve &lt;STRONG&gt;all&lt;/STRONG&gt; raw data from these events, while the second one only need few fields.&lt;/P&gt;

&lt;P&gt;I recommend to use timechart in the first base search,, if that helps sum subsearches (as Splunk calls them: post-process)&lt;BR /&gt;
If only one post process search can use that, consider running the searches directly in each panel without that base search.&lt;/P&gt;

&lt;P&gt;Maybe an accelerated report or a summary index could help more to achieve better performance.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 22:35:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283660#M2645</guid>
      <dc:creator>ehudb</dc:creator>
      <dc:date>2017-02-09T22:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Performance Problems in Dashboard</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283661#M2646</link>
      <description>&lt;P&gt;Thanks ehudb for your answer, I'll try it and keep you update.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 13:59:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283661#M2646</guid>
      <dc:creator>mpepem</dc:creator>
      <dc:date>2017-02-10T13:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Performance Problems in Dashboard</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283662#M2647</link>
      <description>&lt;P&gt;I have another question about what you've said because I could do the same Base Search but using "stats count by" instead of using "fields", do you think that will be better to use and will experience a better performance? &lt;/P&gt;

&lt;P&gt;Before asking here and moving to "fields" I had used "stats" in that Base Search and the performance was more-less the same.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Marcelo&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 15:20:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Performance-Problems-in-Dashboard/m-p/283662#M2647</guid>
      <dc:creator>mpepem</dc:creator>
      <dc:date>2017-02-10T15:20:06Z</dc:date>
    </item>
  </channel>
</rss>

