<?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: Universal Forwarder problem in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489694#M8776</link>
    <description>&lt;P&gt;Hi @aalaa,&lt;/P&gt;

&lt;P&gt;do you configured a scripted input or a file monitoring? in other words: do you have a script scheduled on Unix that writes results in a file and then Splunk read the file or do you manage the script execution in Splunk (scripted input)?&lt;/P&gt;

&lt;P&gt;Anyway in both cases the question is: what's the frequency of execution of the script? &lt;/P&gt;

&lt;P&gt;If you're using a scripted input, the results are immediately forwarderd to Indexers, so the delay is the frequency of schedulation.&lt;/P&gt;

&lt;P&gt;if the script  writes results in a file, Splunk reads it with a delay of up to thirty seconds, so the delay is still the frequency of schedulation.&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
    <pubDate>Mon, 25 Nov 2019 11:56:08 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2019-11-25T11:56:08Z</dc:date>
    <item>
      <title>Universal Forwarder problem</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489693#M8775</link>
      <description>&lt;P&gt;Hello , &lt;BR /&gt;
I have a universal forwarder installed on an oracle server. &lt;BR /&gt;
I configure this universal forwrader to monitor a script file (splunkhome \ bin \ script) that gives the enabled oracle services , but the problem that I receive the list of services activated after 20 munites that I activated or I disabled a service.&lt;BR /&gt;
the goal is to create a real-time alert on the HS to notify that a service is currently enabled.&lt;/P&gt;

&lt;P&gt;Any help please ? &lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 11:09:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489693#M8775</guid>
      <dc:creator>aalaa</dc:creator>
      <dc:date>2019-11-25T11:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder problem</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489694#M8776</link>
      <description>&lt;P&gt;Hi @aalaa,&lt;/P&gt;

&lt;P&gt;do you configured a scripted input or a file monitoring? in other words: do you have a script scheduled on Unix that writes results in a file and then Splunk read the file or do you manage the script execution in Splunk (scripted input)?&lt;/P&gt;

&lt;P&gt;Anyway in both cases the question is: what's the frequency of execution of the script? &lt;/P&gt;

&lt;P&gt;If you're using a scripted input, the results are immediately forwarderd to Indexers, so the delay is the frequency of schedulation.&lt;/P&gt;

&lt;P&gt;if the script  writes results in a file, Splunk reads it with a delay of up to thirty seconds, so the delay is still the frequency of schedulation.&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 11:56:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489694#M8776</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-11-25T11:56:08Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder problem</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489695#M8777</link>
      <description>&lt;P&gt;Thank you Giuseppe for your response , &lt;/P&gt;

&lt;P&gt;I configured the script to writes in a file and i configure the file monitoring ,&lt;BR /&gt;
how can i know the frequency of the script ? &lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 12:12:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489695#M8777</guid>
      <dc:creator>aalaa</dc:creator>
      <dc:date>2019-11-25T12:12:06Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder problem</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489696#M8778</link>
      <description>&lt;P&gt;Hi @aalaa,&lt;BR /&gt;
if you scheduled it using Unix scheduler you have to use cron (e.g.: */5 * * * * means every 5 minutes).&lt;/P&gt;

&lt;P&gt;If you used Splunk inputs, see at &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/admin/inputsconf"&gt;https://docs.splunk.com/Documentation/Splunk/latest/admin/inputsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;interval = [&amp;lt;decimal&amp;gt;|&amp;lt;cron schedule&amp;gt;]
* How often, in seconds, to run the specified command, or a valid "cron"       schedule.
* If you specify the interval as a number, it may have a fractional       component; for example, 3.14
* To specify a cron schedule, use the following format:
  * "&amp;lt;minute&amp;gt; &amp;lt;hour&amp;gt; &amp;lt;day of month&amp;gt; &amp;lt;month&amp;gt; &amp;lt;day of week&amp;gt;"
  * Cron special characters are acceptable. You can use combinations of "*", ",", "/", and "-" to specify wildcards, separate values, specify ranges of values, and step values.
* The cron implementation for data inputs does not currently support names of months or days.
* The special value 0 forces this scripted input to be run continuously.
  As soon as the script exits, the input restarts it.
* The special value -1 causes the scripted input to run once on start-up.
* NOTE: when you specify a cron schedule, the input does not run the script on start-up.
* Default: 60.0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 13:37:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Universal-Forwarder-problem/m-p/489696#M8778</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-11-25T13:37:25Z</dc:date>
    </item>
  </channel>
</rss>

