<?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 Why is some data source indexed one hour in the future? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/593906#M103877</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Some data source is indexed one hour in the future (probably since TZ shift =&amp;gt; twice a year hour change in France !! this time +0100hour).&lt;/P&gt;
&lt;P&gt;We were on gmt+1, now we're on gmt+2.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I don't know where the problem is.&lt;BR /&gt;- checked the server ntp =&amp;gt; ok, gmt+2 updated&lt;BR /&gt;- checked the data source file =&amp;gt; ok&lt;BR /&gt;- tried to reproduced in dev env on a mono-instance : issue not reproducted !&lt;/P&gt;
&lt;P&gt;- this is the only data source with the issue&lt;/P&gt;
&lt;P&gt;My prod env is distributed (SHC, Indexer Cluster and multiple forwarders)&lt;/P&gt;
&lt;P&gt;- data is a jsonl file.&lt;/P&gt;
&lt;P&gt;I'm soo lost !!&lt;/P&gt;
&lt;P&gt;Thank you for your help !!&lt;/P&gt;
&lt;P&gt;Ema&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;on the indexer cluster :&lt;/P&gt;
&lt;P&gt;[mysourcetype]&lt;BR /&gt;NO_BINARY_CHECK = true&lt;BR /&gt;SHOULD_LINEMERGE = false&lt;BR /&gt;TIME_PREFIX= "dte":"&lt;BR /&gt;TIME_FORMAT = %d/%m/%Y %H:%M:%S&lt;BR /&gt;TRUNCATE = 0&lt;BR /&gt;MAX_DAYS_AGO = 4000&lt;BR /&gt;category = Structured&lt;BR /&gt;disabled = false&lt;BR /&gt;pulldown_type = true&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;data sample :&lt;/P&gt;
&lt;P&gt;{"idj":"3108824152","dce":"IDN","fce":"IDN2","ace":"176","dte":"08/04/2022 14:44:31","org":"GN","dmc":"2","idu":"211151","csu":"00082827","lsu":"CROSS BDOHRIJ GHBGD14 ","ctx":"Identifiant:PN-003042021007790-ARD-PPM-70732201#Procédure de référence:CIAHTDT CENTRAL DE CNJAEN-2021-007790#Type personne:Physique#Qualité personne:Mise en cause#Nom:XXX#Prénom:yyy#Lieu de naissance:CAEN#Date de naissance:05/01/1991#","idd":"PN-0030428541021007790-ARD-PPM-7074532201","ise":"N","cts":[{"idj":"3108824152","nom":"XXX","pre":"yyy","jne":"5","mne":"1","ane":"1981","lne":"CAEN","cot":"","not":"","qot":"","nuo":"","ctt":"","gtt":"","qtt":"","ntt":""}]}&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This data is indexed at&amp;nbsp; 08/04/2022 15:44:31 for 08/04/2022 14:44:31 !&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Apr 2022 17:35:25 GMT</pubDate>
    <dc:creator>emallinger</dc:creator>
    <dc:date>2022-04-15T17:35:25Z</dc:date>
    <item>
      <title>Why is some data source indexed one hour in the future?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/593906#M103877</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Some data source is indexed one hour in the future (probably since TZ shift =&amp;gt; twice a year hour change in France !! this time +0100hour).&lt;/P&gt;
&lt;P&gt;We were on gmt+1, now we're on gmt+2.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I don't know where the problem is.&lt;BR /&gt;- checked the server ntp =&amp;gt; ok, gmt+2 updated&lt;BR /&gt;- checked the data source file =&amp;gt; ok&lt;BR /&gt;- tried to reproduced in dev env on a mono-instance : issue not reproducted !&lt;/P&gt;
&lt;P&gt;- this is the only data source with the issue&lt;/P&gt;
&lt;P&gt;My prod env is distributed (SHC, Indexer Cluster and multiple forwarders)&lt;/P&gt;
&lt;P&gt;- data is a jsonl file.&lt;/P&gt;
&lt;P&gt;I'm soo lost !!&lt;/P&gt;
&lt;P&gt;Thank you for your help !!&lt;/P&gt;
&lt;P&gt;Ema&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;on the indexer cluster :&lt;/P&gt;
&lt;P&gt;[mysourcetype]&lt;BR /&gt;NO_BINARY_CHECK = true&lt;BR /&gt;SHOULD_LINEMERGE = false&lt;BR /&gt;TIME_PREFIX= "dte":"&lt;BR /&gt;TIME_FORMAT = %d/%m/%Y %H:%M:%S&lt;BR /&gt;TRUNCATE = 0&lt;BR /&gt;MAX_DAYS_AGO = 4000&lt;BR /&gt;category = Structured&lt;BR /&gt;disabled = false&lt;BR /&gt;pulldown_type = true&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;data sample :&lt;/P&gt;
&lt;P&gt;{"idj":"3108824152","dce":"IDN","fce":"IDN2","ace":"176","dte":"08/04/2022 14:44:31","org":"GN","dmc":"2","idu":"211151","csu":"00082827","lsu":"CROSS BDOHRIJ GHBGD14 ","ctx":"Identifiant:PN-003042021007790-ARD-PPM-70732201#Procédure de référence:CIAHTDT CENTRAL DE CNJAEN-2021-007790#Type personne:Physique#Qualité personne:Mise en cause#Nom:XXX#Prénom:yyy#Lieu de naissance:CAEN#Date de naissance:05/01/1991#","idd":"PN-0030428541021007790-ARD-PPM-7074532201","ise":"N","cts":[{"idj":"3108824152","nom":"XXX","pre":"yyy","jne":"5","mne":"1","ane":"1981","lne":"CAEN","cot":"","not":"","qot":"","nuo":"","ctt":"","gtt":"","qtt":"","ntt":""}]}&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This data is indexed at&amp;nbsp; 08/04/2022 15:44:31 for 08/04/2022 14:44:31 !&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 17:35:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/593906#M103877</guid>
      <dc:creator>emallinger</dc:creator>
      <dc:date>2022-04-15T17:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: Some data source is indexed one hour in the future</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/593909#M103878</link>
      <description>&lt;P&gt;Your source doesn't report the timezone so the indexer/hf, since no tz is defined for the sourcetype, interprets with its local timezone.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 15:46:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/593909#M103878</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-04-15T15:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: Some data source is indexed one hour in the future</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/594213#M103888</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, but source and indexer are in the same time zone, at the same hour.&lt;/P&gt;&lt;P&gt;So why the difference ?&lt;/P&gt;&lt;P&gt;Thanks for your suggestions,&lt;/P&gt;&lt;P&gt;Ema&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 08:27:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-some-data-source-indexed-one-hour-in-the-future/m-p/594213#M103888</guid>
      <dc:creator>emallinger</dc:creator>
      <dc:date>2022-04-19T08:27:13Z</dc:date>
    </item>
  </channel>
</rss>

