<?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: saved searches in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293237#M5442</link>
    <description>&lt;P&gt;I'll agree that you could run the savedsearch command, however, it will run the entire saved search when the dashboard is ran, instead of pulling in the results from the report. as stated above, it is a huge amount of data, and could take a while. I'd recommend extending the life of the job under the savedsearches.conf for ongoing runs of this report.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Jan 2018 13:04:59 GMT</pubDate>
    <dc:creator>cmerriman</dc:creator>
    <dc:date>2018-01-10T13:04:59Z</dc:date>
    <item>
      <title>saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293233#M5438</link>
      <description>&lt;P&gt;I have schedule report"AAA" which runs once in a month ( pulls huge number of records for last 6 months) &lt;/P&gt;

&lt;P&gt;I have another dashboard where I have one panel showing "AAA" data. &lt;/P&gt;

&lt;P&gt;my code is :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;      &amp;lt;query&amp;gt;| loadjob savedsearch="username:search:Domain_Controllers_Status_In_Splunk"&amp;lt;/query&amp;gt;

    &amp;lt;/search&amp;gt;

    It use work fine till last month, and now I don't see any data pull in Dashboard panel. Although the schedule reports works fine. 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any idea how long the saved searches are accessible is there ant time frame like a week or some time is set, I am assuming if the saved is not getting expired. &lt;/P&gt;

&lt;P&gt;Any suggestion.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 06:37:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293233#M5438</guid>
      <dc:creator>raomu</dc:creator>
      <dc:date>2018-01-10T06:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293234#M5439</link>
      <description>&lt;P&gt;You cas specify and increase job lifetime period &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Extendjoblifetimes"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Search/Extendjoblifetimes&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 12:48:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293234#M5439</guid>
      <dc:creator>andrey2007</dc:creator>
      <dc:date>2018-01-10T12:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293235#M5440</link>
      <description>&lt;P&gt;hey &lt;/P&gt;

&lt;P&gt;you can definitely extend the job life time as mentioned in this doc &lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.6.3/Search/Extendjoblifetimes"&gt;https://docs.splunk.com/Documentation/Splunk/6.6.3/Search/Extendjoblifetimes&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;but what i would suggest is try this search command &lt;CODE&gt;savedsearch&lt;/CODE&gt; and use this is dashboard instead of &lt;CODE&gt;loadjob&lt;/CODE&gt;&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.3/SearchReference/Savedsearch"&gt;https://docs.splunk.com/Documentation/SplunkCloud/6.6.3/SearchReference/Savedsearch&lt;/A&gt;&lt;BR /&gt;
&lt;CODE&gt;| savedsearch your_report_name&lt;/CODE&gt;&lt;BR /&gt;
let me know if this helps you!&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 12:56:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293235#M5440</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-10T12:56:00Z</dc:date>
    </item>
    <item>
      <title>Re: saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293236#M5441</link>
      <description>&lt;P&gt;run this and look at the dateExpire field that is calculated. that should give you an idea. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|rest /services/search/jobs|search  isSavedSearch=1 delegate="scheduler" label="Domain Controllers Status In Splunk"|fields author label earliestTime latestTime runDuration isDone isFailed isSaved sid ttl published|eval publishedepoch=strptime(published,"%Y-%m-%dT%H:%M:%S.%3N%:z")|eval dateExpire=strftime(publishedepoch+ttl,"%Y-%m-%dT%H:%M:%S")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;the ttl is the time to live. you can change the settings in savedsearches.conf under dispatch.ttl&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.0.1/Admin/Savedsearchesconf#dispatch_search_options"&gt;https://docs.splunk.com/Documentation/Splunk/7.0.1/Admin/Savedsearchesconf#dispatch_search_options&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 13:02:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293236#M5441</guid>
      <dc:creator>cmerriman</dc:creator>
      <dc:date>2018-01-10T13:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293237#M5442</link>
      <description>&lt;P&gt;I'll agree that you could run the savedsearch command, however, it will run the entire saved search when the dashboard is ran, instead of pulling in the results from the report. as stated above, it is a huge amount of data, and could take a while. I'd recommend extending the life of the job under the savedsearches.conf for ongoing runs of this report.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 13:04:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293237#M5442</guid>
      <dc:creator>cmerriman</dc:creator>
      <dc:date>2018-01-10T13:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293238#M5443</link>
      <description>&lt;P&gt;here i am assuming that saved search is accelerated &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 13:13:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293238#M5443</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-10T13:13:58Z</dc:date>
    </item>
    <item>
      <title>Re: saved searches</title>
      <link>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293239#M5444</link>
      <description>&lt;P&gt;Thanks, I am able to find the expire date/Time.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2018 21:37:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/saved-searches/m-p/293239#M5444</guid>
      <dc:creator>raomu</dc:creator>
      <dc:date>2018-01-10T21:37:35Z</dc:date>
    </item>
  </channel>
</rss>

