<?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 How can I take the second timestamp in props.conf? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651432#M110638</link>
    <description>&lt;P&gt;how can i in the props.conf file tell Splunk to take the second timestamp as opposed to the first&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jul 2023 17:33:35 GMT</pubDate>
    <dc:creator>lorscardala985</dc:creator>
    <dc:date>2023-07-21T17:33:35Z</dc:date>
    <item>
      <title>How can I take the second timestamp in props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651432#M110638</link>
      <description>&lt;P&gt;how can i in the props.conf file tell Splunk to take the second timestamp as opposed to the first&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 17:33:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651432#M110638</guid>
      <dc:creator>lorscardala985</dc:creator>
      <dc:date>2023-07-21T17:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651434#M110639</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;this depends on your log file's content. Can you share it?&lt;/P&gt;&lt;P&gt;In common level you could add TIME_PREFIX on your props.conf to recognise correct place where your timestamp starts. See more from here&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.1.0/Data/Configuretimestamprecognition" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.1.0/Data/Configuretimestamprecognition&lt;/A&gt;&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 09:32:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651434#M110639</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-07-21T09:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651436#M110640</link>
      <description>&lt;P&gt;i have events with this timestamp&amp;nbsp;Sep 20 11:13:18 10.50.3.100 Sep 20 11:13:15 and i want to view only the second timestamp&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 09:43:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651436#M110640</guid>
      <dc:creator>lorscardala985</dc:creator>
      <dc:date>2023-07-21T09:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651441#M110641</link>
      <description>&lt;P&gt;In this case you could try something like&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;^(\w+[\s:\.]+){9}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;on your TIME_PREFIX. &amp;nbsp;I assume that 1st timestamp field is first characters on your log entry. If not then ^ should be fixed to match where this starts.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 09:49:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-take-the-second-timestamp-in-props-conf/m-p/651441#M110641</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-07-21T09:49:23Z</dc:date>
    </item>
  </channel>
</rss>

