<?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: Multiple time formats in same data source in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199252#M57685</link>
    <description>&lt;P&gt;It would probably be better if you could get the applications to write to individual log files. By giving an  explicit &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; that only matches a subset of the events, the others will not parse correctly. &lt;/P&gt;

&lt;P&gt;Also, there seems to be no time element in some of the logs, just a date. Perhaps &lt;CODE&gt;DATETIME_CONFIG = current&lt;/CODE&gt; in props.conf could work for you?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.3/Data/Configuretimestamprecognition"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.3/Data/Configuretimestamprecognition&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
    <pubDate>Tue, 02 Sep 2014 13:49:13 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2014-09-02T13:49:13Z</dc:date>
    <item>
      <title>Multiple time formats in same data source</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199251#M57684</link>
      <description>&lt;P&gt;I have a data source I am trying to ingest into Splunk. It is a txt file that is written to by multiple systems. My problem is that each system writing to the file has it's own date format. I have worked out two of the three data sources which have a two digit year The third data source has a four digit year.&lt;/P&gt;

&lt;P&gt;Below is what we are currently using in props.conf and a sample of the data.&lt;/P&gt;

&lt;P&gt;TIME_FORMAT =%m/%d/%y&lt;BR /&gt;
TIME_PREFIX=NODE\w{2}\s+;&lt;/P&gt;

&lt;P&gt;INTVCICS;08/29/2014 ;23:30 ;1B90;T100 ;1 ;0 ;0 ;0 ;0.608 ;2.659 ;0.000 ;0.000 ;0.000 ;VENDORS ;XXXXX&lt;BR /&gt;
NODEPR  ;08/27/14 ;1D81;ECM_storeDocumentToCI_MF ;Extract Message-Code/Decode ;0.002 ;0.001 ;103 ;XXXXXXXX ;ComputeNode ;XXXXXXX&lt;BR /&gt;
NODENP  ;08/29/14 ;1B90;5:58 ;CM_retrieveClaimHistoryDtlCMS_MF ;SOAP Reply ;0.001 ;0.001 ;25 ;XXXXXXXX ;SOAPReplyNode ;XXXXXXX&lt;/P&gt;

&lt;P&gt;Thank you,&lt;BR /&gt;
Don&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:27:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199251#M57684</guid>
      <dc:creator>DonDandrea</dc:creator>
      <dc:date>2020-09-28T17:27:36Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple time formats in same data source</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199252#M57685</link>
      <description>&lt;P&gt;It would probably be better if you could get the applications to write to individual log files. By giving an  explicit &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; that only matches a subset of the events, the others will not parse correctly. &lt;/P&gt;

&lt;P&gt;Also, there seems to be no time element in some of the logs, just a date. Perhaps &lt;CODE&gt;DATETIME_CONFIG = current&lt;/CODE&gt; in props.conf could work for you?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.3/Data/Configuretimestamprecognition"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.3/Data/Configuretimestamprecognition&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2014 13:49:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199252#M57685</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-09-02T13:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple time formats in same data source</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199253#M57686</link>
      <description>&lt;P&gt;We reformatted the output data from the source so all event use a two digit year. Once that was complete I was still having a problem with some events having a time and others did not. I simply configured Splunk to index by date and ignore time. Then I created an extract in props.conf for each of the event types. Now I can use eval with striptime in my search parameters and replace the date/time stamp of the events. This now allows use of date and time ranges and timechart.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2014 12:45:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-time-formats-in-same-data-source/m-p/199253#M57686</guid>
      <dc:creator>DonDandrea</dc:creator>
      <dc:date>2014-09-18T12:45:00Z</dc:date>
    </item>
  </channel>
</rss>

