<?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 Re: Heavy query in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325823#M2992</link>
    <description>&lt;P&gt;Sorry but this query doesn't extract any results&lt;/P&gt;</description>
    <pubDate>Wed, 12 Apr 2017 14:54:14 GMT</pubDate>
    <dc:creator>spillo491</dc:creator>
    <dc:date>2017-04-12T14:54:14Z</dc:date>
    <item>
      <title>Heavy query</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325821#M2990</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;I have a problem with this query executed on 3 months&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="app" host="sl0920*" source="/home/java/jboss-eap-6.2/app/log/teller-web.log" OR source="/home/java/jboss-eap-6.2/app/log/desktop-web.log" priority="FATAL" category="AUDIT*" message="{Invoking*" | eval date = strftime(_time, "%Y-%m-%d") | stats count as Contatore by message,correlationId,date | where Contatore &amp;gt; 1 | eval tot = Contatore/2 | chart sum(tot) as tot by date
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Is it possible rewrite the same query with a query with better performances please ?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 12:34:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325821#M2990</guid>
      <dc:creator>spillo491</dc:creator>
      <dc:date>2017-04-12T12:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy query</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325822#M2991</link>
      <description>&lt;P&gt;I don't see anything obviously bad about the code.  When possible, you want to avoid reformatting data at the event level before the data is summarized, and a numeric field (or epoch time field) is more efficient for summary than a display field, but you at least need to &lt;CODE&gt;bin&lt;/CODE&gt; the &lt;CODE&gt;_time&lt;/CODE&gt; at the &lt;CODE&gt;1d&lt;/CODE&gt; level, so we can't avoid a reformat completely.  &lt;/P&gt;

&lt;P&gt;Try this, and see what happens.  There might be a marginal improvement.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index="app" host="sl0920*" (source="/home/java/jboss-eap-6.2/app/log/teller-web.log" OR source="/home/java/jboss-eap-6.2/app/log/desktop-web.log") priority="FATAL" category="AUDIT*" message="{Invoking*" 
| table _time, message, correlationId
| bin _time as date  span=1d
| stats count as Contatore by message, correlationId, date 
| where Contatore &amp;gt; 1 
| eval tot = Contatore/2
| eval date = strftime(_time, "%Y-%m-%d")  
| chart sum(tot) as tot by date
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm tempted to try a &lt;CODE&gt;timechart&lt;/CODE&gt; version, but without your data, I have no way of knowing if it would get better results. &lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 14:24:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325822#M2991</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-04-12T14:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy query</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325823#M2992</link>
      <description>&lt;P&gt;Sorry but this query doesn't extract any results&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 14:54:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325823#M2992</guid>
      <dc:creator>spillo491</dc:creator>
      <dc:date>2017-04-12T14:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy query</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325824#M2993</link>
      <description>&lt;P&gt;@spillo491... do you get any result when you run 1st 4 lines of DalJeanis' code?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 15:31:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325824#M2993</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-04-12T15:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy query</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325825#M2994</link>
      <description>&lt;P&gt;On a different thought... If you have too many events to be handled in 30 days... You can actually try summary index.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 15:32:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325825#M2994</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-04-12T15:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy query</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325826#M2995</link>
      <description>&lt;P&gt;Yes, I get results !&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2017 06:40:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Heavy-query/m-p/325826#M2995</guid>
      <dc:creator>spillo491</dc:creator>
      <dc:date>2017-04-13T06:40:58Z</dc:date>
    </item>
  </channel>
</rss>

