<?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 Calling Splunk API to run a query and generate a report 3 hours after it is called? in Other Usage</title>
    <link>https://community.splunk.com/t5/Other-Usage/Calling-Splunk-API-to-run-a-query-and-generate-a-report-3-hours/m-p/641144#M222</link>
    <description>&lt;P&gt;Hi All,&lt;BR /&gt;&lt;BR /&gt;There is a requirement where a temporary cluster has to trigger Splunk API to run a command and generate a report. This cluster will have to trigger Splunk API right before it gets terminated. However, the Splunk API after called should only run 3 hours after its triggered and once the report is generated, the report should be sent via email and the process should be ended(Only once and not recurring every 3 hours).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;This is because there is one log as part of that command which gets pushed 3 hours after the temporary cluster is terminated.(The data is not real-time).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I only have this option to automate because the call should be made by a cluster which is ready for termination only.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;So how can I schedule a search to run&amp;nbsp; 3 hours after its triggered to generate an report as an email?&amp;nbsp;&lt;BR /&gt;Please let me know if there are any better options to achieve this.&lt;BR /&gt;&lt;BR /&gt;Much awaiting for the suggestions. Thanks in Advance.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Apr 2023 14:57:44 GMT</pubDate>
    <dc:creator>Siri9996</dc:creator>
    <dc:date>2023-04-24T14:57:44Z</dc:date>
    <item>
      <title>Calling Splunk API to run a query and generate a report 3 hours after it is called?</title>
      <link>https://community.splunk.com/t5/Other-Usage/Calling-Splunk-API-to-run-a-query-and-generate-a-report-3-hours/m-p/641144#M222</link>
      <description>&lt;P&gt;Hi All,&lt;BR /&gt;&lt;BR /&gt;There is a requirement where a temporary cluster has to trigger Splunk API to run a command and generate a report. This cluster will have to trigger Splunk API right before it gets terminated. However, the Splunk API after called should only run 3 hours after its triggered and once the report is generated, the report should be sent via email and the process should be ended(Only once and not recurring every 3 hours).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;This is because there is one log as part of that command which gets pushed 3 hours after the temporary cluster is terminated.(The data is not real-time).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I only have this option to automate because the call should be made by a cluster which is ready for termination only.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;So how can I schedule a search to run&amp;nbsp; 3 hours after its triggered to generate an report as an email?&amp;nbsp;&lt;BR /&gt;Please let me know if there are any better options to achieve this.&lt;BR /&gt;&lt;BR /&gt;Much awaiting for the suggestions. Thanks in Advance.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 14:57:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Other-Usage/Calling-Splunk-API-to-run-a-query-and-generate-a-report-3-hours/m-p/641144#M222</guid>
      <dc:creator>Siri9996</dc:creator>
      <dc:date>2023-04-24T14:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Calling Splunk API to run a query and generate a report 3 hours after it is called?</title>
      <link>https://community.splunk.com/t5/Other-Usage/Calling-Splunk-API-to-run-a-query-and-generate-a-report-3-hours/m-p/641152#M223</link>
      <description>&lt;P&gt;If I understand you correctly, you want to make splunk wait 3 hours before executing some search.&lt;/P&gt;&lt;P&gt;Natively Splunk doesn't have a "delay" functionality.&lt;/P&gt;&lt;P&gt;You could try to "emulate" a counter by setting a value in a lookup and decrement it with a scheduled search and have an "optional execution" search implemented in another scheduled search.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 15:33:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Other-Usage/Calling-Splunk-API-to-run-a-query-and-generate-a-report-3-hours/m-p/641152#M223</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-04-24T15:33:59Z</dc:date>
    </item>
  </channel>
</rss>

