<?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 configure proper timestamp recognition to fix syslog date parsing? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132751#M27271</link>
    <description>&lt;P&gt;Hi.&lt;BR /&gt;
Check the timestamp recognition.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/Data/Configuretimestamprecognition"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/Data/Configuretimestamprecognition&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Bye.&lt;/P&gt;</description>
    <pubDate>Sun, 23 Nov 2014 23:06:55 GMT</pubDate>
    <dc:creator>changux</dc:creator>
    <dc:date>2014-11-23T23:06:55Z</dc:date>
    <item>
      <title>How to configure proper timestamp recognition to fix syslog date parsing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132750#M27270</link>
      <description>&lt;P&gt;We have a firewall sending events to a Splunk indexer via syslog, so we have a section of our inputs.conf file like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcp://&amp;lt;port over which syslog data is sent&amp;gt;]
connection_host = dns
host = &amp;lt;name of firewall&amp;gt;
index = firewall
sourcetype = syslog
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The trouble is that the firewall's date and time format is a bit strange:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;nn&amp;gt;YYYY:MM:DD-HH:mm:ss ...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;where &lt;CODE&gt;nn&lt;/CODE&gt; is a two or three digit number, &lt;CODE&gt;YYYY&lt;/CODE&gt; is the year with century, &lt;CODE&gt;MM&lt;/CODE&gt; is a two-digit month, &lt;CODE&gt;DD&lt;/CODE&gt; is a two-digit day, &lt;CODE&gt;HH&lt;/CODE&gt; is a two-digit hour, &lt;CODE&gt;mm&lt;/CODE&gt; is a two-digit minute and &lt;CODE&gt;ss&lt;/CODE&gt; is a two-digit second.  About half the time, Splunk gets the day wrong (perhaps it thinks that the &lt;CODE&gt;-&lt;/CODE&gt; between the day and the hour is a subtraction?).  There are also events that don't start with `` and don't include a date and time.&lt;/P&gt;

&lt;P&gt;In order to fix the date parsing, I know I need to create an &lt;CODE&gt;inputs.conf&lt;/CODE&gt; file, but I'm not clear on exactly what I should be putting into it, given that not all lines start with ``.  Any suggestions?&lt;/P&gt;

&lt;P&gt;Can anything be done to correct all of the data (about a year's worth) that has had the dates parsed incorrectly?&lt;/P&gt;

&lt;P&gt;Thanks for any suggestions!&lt;/P&gt;</description>
      <pubDate>Sun, 23 Nov 2014 22:53:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132750#M27270</guid>
      <dc:creator>kenniskoldewyn</dc:creator>
      <dc:date>2014-11-23T22:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure proper timestamp recognition to fix syslog date parsing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132751#M27271</link>
      <description>&lt;P&gt;Hi.&lt;BR /&gt;
Check the timestamp recognition.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/Data/Configuretimestamprecognition"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/Data/Configuretimestamprecognition&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Bye.&lt;/P&gt;</description>
      <pubDate>Sun, 23 Nov 2014 23:06:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132751#M27271</guid>
      <dc:creator>changux</dc:creator>
      <dc:date>2014-11-23T23:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure proper timestamp recognition to fix syslog date parsing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132752#M27272</link>
      <description>&lt;P&gt;I added the following section to props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host::&amp;lt;name of the firewall&amp;gt;]
TIME_PREFIX = &amp;lt;\d+&amp;gt;
TIME_FORMAT = %Y:%m:%d-%H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;but that didn't help.  Any other ideas?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2014 16:05:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132752#M27272</guid>
      <dc:creator>kenniskoldewyn</dc:creator>
      <dc:date>2014-11-25T16:05:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure proper timestamp recognition to fix syslog date parsing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132753#M27273</link>
      <description>&lt;P&gt;Corrections to the above: "I know I need to create an &lt;CODE&gt;inputs.conf&lt;/CODE&gt; file" should be "I know I need to create a &lt;CODE&gt;props.conf&lt;/CODE&gt; file", and "given that not all lines start with `&lt;CODE&gt;" should be "given that not all lines start with&lt;/CODE&gt;&lt;DL&gt;&lt;DD&gt;`".&lt;BR /&gt;
&lt;/DD&gt;&lt;/DL&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2014 16:10:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132753#M27273</guid>
      <dc:creator>kenniskoldewyn</dc:creator>
      <dc:date>2014-11-25T16:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure proper timestamp recognition to fix syslog date parsing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132754#M27274</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX=^\&amp;lt;\d+\&amp;gt;|^
TIME_FORMAT = %Y:%m:%d-%H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Try this&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2014 16:38:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132754#M27274</guid>
      <dc:creator>theouhuios</dc:creator>
      <dc:date>2014-11-25T16:38:53Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure proper timestamp recognition to fix syslog date parsing?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132755#M27275</link>
      <description>&lt;P&gt;Nope, still doesn't work.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2014 18:47:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-proper-timestamp-recognition-to-fix-syslog-date/m-p/132755#M27275</guid>
      <dc:creator>kenniskoldewyn</dc:creator>
      <dc:date>2014-11-26T18:47:14Z</dc:date>
    </item>
  </channel>
</rss>

