<?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: Lower Memory usage in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402233#M5777</link>
    <description>&lt;P&gt;Give this try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=Nitro_server=xs_json Model="*v10*" FirmwareVersion = * earliest=-48h 
| fields hdr.nitro "Mac_Address" FirmwareVersion
| dedup "Mac_Address" 
| eval nitro_loc=tonumber('hdr.nitro') as nitro_loc 
| search nitro_loc="*"
| lookup nitro_loc.csv nitro_loc OUTPUT TimeZone
| stats count by FirmwareVersion TimeZone
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;changes done&lt;BR /&gt;
1) Moved filters to base search wherever possible&lt;BR /&gt;
2) Added fields command to only keep the fields that'll be used in search.&lt;BR /&gt;
3) Moved dedup earlier in the search so that subsequent operations are happening on only required events&lt;BR /&gt;
4) Instead of formatting lookup table column nitro_loc (which will require join), formatted search data field to be number and did regular lookup.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Aug 2018 21:04:01 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2018-08-14T21:04:01Z</dc:date>
    <item>
      <title>Lower Memory usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402229#M5773</link>
      <description>&lt;P&gt;I have a query that is being blocked from retrieving all relevant data due to policy to keep queries under 500mb, is there anyway I could optimize this query?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=Nitro_server=xs_json earliest=-48h 
| rename hdr.nitro as nitro_loc 
| join type=inner 
    [ inputlookup nitro_loc.csv 
    | search TimeZone="C" OR "CDT" 
    | eval nitro_loc=case(len(STORE)==4,STORE,len(STORE)==3,"0".STORE,len(STORE)==2,"00".STORE,len(STORE)==1,"000".STORE) ] 
| search Model="*v10*" nitro_loc="*" FirmwareVersion = * 
| dedup "Mac_Address" 
| stats count by FirmwareVersion TimeZone
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any suggestions would be appreciated! &lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 20:01:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402229#M5773</guid>
      <dc:creator>JoshuaJohn</dc:creator>
      <dc:date>2018-08-14T20:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: Lower Memory usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402230#M5774</link>
      <description>&lt;P&gt;Generally try to avoid &lt;CODE&gt;join&lt;/CODE&gt; whenever possible. Have you explored just using &lt;CODE&gt;nitro_loc.csv&lt;/CODE&gt; as a regular lookup using the &lt;CODE&gt;lookup&lt;/CODE&gt; command here?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 20:45:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402230#M5774</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2018-08-14T20:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: Lower Memory usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402231#M5775</link>
      <description>&lt;P&gt;What all fields are you getting from lookup nitro_loc.csv? On what field you're doing the join? &lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 20:45:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402231#M5775</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2018-08-14T20:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: Lower Memory usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402232#M5776</link>
      <description>&lt;P&gt;I am doing the join on nitro_loc which is a 4 digit number, and I am trying to get timezone out of the csv.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 20:51:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402232#M5776</guid>
      <dc:creator>JoshuaJohn</dc:creator>
      <dc:date>2018-08-14T20:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: Lower Memory usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402233#M5777</link>
      <description>&lt;P&gt;Give this try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=Nitro_server=xs_json Model="*v10*" FirmwareVersion = * earliest=-48h 
| fields hdr.nitro "Mac_Address" FirmwareVersion
| dedup "Mac_Address" 
| eval nitro_loc=tonumber('hdr.nitro') as nitro_loc 
| search nitro_loc="*"
| lookup nitro_loc.csv nitro_loc OUTPUT TimeZone
| stats count by FirmwareVersion TimeZone
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;changes done&lt;BR /&gt;
1) Moved filters to base search wherever possible&lt;BR /&gt;
2) Added fields command to only keep the fields that'll be used in search.&lt;BR /&gt;
3) Moved dedup earlier in the search so that subsequent operations are happening on only required events&lt;BR /&gt;
4) Instead of formatting lookup table column nitro_loc (which will require join), formatted search data field to be number and did regular lookup.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 21:04:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Lower-Memory-usage/m-p/402233#M5777</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2018-08-14T21:04:01Z</dc:date>
    </item>
  </channel>
</rss>

