<?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: How to turn off splunkd during certain hours in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372409#M3210</link>
    <description>&lt;P&gt;ssievert - Loved your response, and your time is much appreciated. I will pass this along to my customer. Thank you!!&lt;/P&gt;</description>
    <pubDate>Tue, 03 Oct 2017 13:47:28 GMT</pubDate>
    <dc:creator>rholm01</dc:creator>
    <dc:date>2017-10-03T13:47:28Z</dc:date>
    <item>
      <title>How to turn off splunkd during certain hours</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372405#M3206</link>
      <description>&lt;P&gt;I have a customer who wants to have the splunk forwarder turned off during certain critical processing time. &lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2017 22:35:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372405#M3206</guid>
      <dc:creator>rholm01</dc:creator>
      <dc:date>2017-10-02T22:35:53Z</dc:date>
    </item>
    <item>
      <title>Re: How to turn off splunkd during certain hours</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372406#M3207</link>
      <description>&lt;P&gt;Do you want Splunk to stop forwarding during this time, or stop collecting logs during this time? If you stop Splunk, and then start it up at a later time, it will "catchup" on the data that was missing.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 00:23:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372406#M3207</guid>
      <dc:creator>sduff_splunk</dc:creator>
      <dc:date>2017-10-03T00:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to turn off splunkd during certain hours</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372407#M3208</link>
      <description>&lt;P&gt;You have to write a cronjob to do this. &lt;BR /&gt;
To turn off splunk  at certain time, you have to write a small script which will include splunk stop and start commands &lt;BR /&gt;
or two separate cronjobs. &lt;/P&gt;

&lt;P&gt;&lt;A href="https://tecadmin.net/crontab-in-linux-with-20-examples-of-cron-schedule/"&gt;https://tecadmin.net/crontab-in-linux-with-20-examples-of-cron-schedule/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Schedule a cron to execute on every Sunday at 5 PM.&lt;BR /&gt;
This type of cron are useful for doing weekly tasks, like log rotation etc.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#to start splunk again at 5pm sunday
0 17 * * 7 /opt/splunk/bin/splunk stop

#to start splunk again at 6pm
0 18 * * 7 /opt/splunk/bin/splunk start
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 03 Oct 2017 00:52:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372407#M3208</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2017-10-03T00:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to turn off splunkd during certain hours</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372408#M3209</link>
      <description>&lt;P&gt;Wait, what? They want to have log collection/forwarding turned off during critical processing times? Seems a bit counter-intuitive to me. I would want to know if that critical processing caused any error messages as quickly as possible. What is your customer's concern? Are they worried the forwarder (a universal forwarder, I assume?) will delay their critical processes by 'stealing' too much CPU/memory?&lt;BR /&gt;
Are their servers running at a CPU utilization well beyond 75% or so during those times?&lt;BR /&gt;
Did they experience impact caused by the forwarder?&lt;BR /&gt;
Those are the kinds of questions I would ask, because - ideally - you do not want to stop the forwarder for extended periods of time, especially on a system that creates a lot of log files that potentially roll quickly during higher utilization periods.&lt;/P&gt;

&lt;P&gt;If they can't be convinced to not do that kind of thing, cron is your friend. &lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 06:30:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372408#M3209</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2017-10-03T06:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to turn off splunkd during certain hours</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372409#M3210</link>
      <description>&lt;P&gt;ssievert - Loved your response, and your time is much appreciated. I will pass this along to my customer. Thank you!!&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 13:47:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-turn-off-splunkd-during-certain-hours/m-p/372409#M3210</guid>
      <dc:creator>rholm01</dc:creator>
      <dc:date>2017-10-03T13:47:28Z</dc:date>
    </item>
  </channel>
</rss>

