<?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 do I set the CRON job for scripted inputs so that the timezone is not UTC? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/634134#M108546</link>
    <description>&lt;P&gt;Hi. Just reading this one.. so your scripted input doesn't really belong to a user the way a knowledge object like a savedsearch AFAIK. So I would imagine the cron schedule is based on the timezone of the server it runs on.&lt;/P&gt;</description>
    <pubDate>Sun, 12 Mar 2023 04:17:57 GMT</pubDate>
    <dc:creator>burwell</dc:creator>
    <dc:date>2023-03-12T04:17:57Z</dc:date>
    <item>
      <title>How do I set the CRON job for scripted inputs so that the timezone is not UTC?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/546800#M91047</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have a scripted input with a CRON set to&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;50 5-23 * * *&lt;/STRONG&gt; so that it "sleeps" between the hours of midnight and 6AM.&amp;nbsp; I noticed, however, that the script is "sleeping" between the ours of 2AM and 8AM.&amp;nbsp; After investigating I discovered that the CRON was running with UTC time standard and not my time zone, which is currently CEST.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How do I set it to run in line with my timezone instead of the UTC time standard?&amp;nbsp; With other objects like saved searches the timezone is retrieved from the account that owns the object, but with scripted inputs I don't see this option.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 06:39:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/546800#M91047</guid>
      <dc:creator>andrewtrobec</dc:creator>
      <dc:date>2021-04-06T06:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: How do I set the CRON job for scripted inputs so that the timezone is not UTC?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/550938#M91476</link>
      <description>&lt;P&gt;For some of the users,&amp;nbsp; the server limits the cron use.&amp;nbsp; &lt;A title="WebCron" href="https://www.easycron.com/" target="_self"&gt;EasyCron&lt;/A&gt; is an option. To those who don't know how to use crontab, EasyCron is a great alternative &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 08 May 2021 08:43:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/550938#M91476</guid>
      <dc:creator>larry02</dc:creator>
      <dc:date>2021-05-08T08:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: How do I set the CRON job for scripted inputs so that the timezone is not UTC?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/634134#M108546</link>
      <description>&lt;P&gt;Hi. Just reading this one.. so your scripted input doesn't really belong to a user the way a knowledge object like a savedsearch AFAIK. So I would imagine the cron schedule is based on the timezone of the server it runs on.&lt;/P&gt;</description>
      <pubDate>Sun, 12 Mar 2023 04:17:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-set-the-CRON-job-for-scripted-inputs-so-that-the/m-p/634134#M108546</guid>
      <dc:creator>burwell</dc:creator>
      <dc:date>2023-03-12T04:17:57Z</dc:date>
    </item>
  </channel>
</rss>

