<?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 to modify syslog source type to handle rfc3339 timestamp? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-modify-syslog-source-type-to-handle-rfc3339-timestamp/m-p/483064#M82756</link>
    <description>&lt;P&gt;We pass messages with rsyslog using the rfc3339 time format. It has microseconds, and it has a timestamp. But noticed a few issues:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;The time zone is not parsed out of the message. If I remove the microseconds from the timestamp, it would work fine.&lt;/LI&gt;
&lt;LI&gt;The host does not get parsed out. Seems to be a problem with the syslog-host transform which does not like the timezone. Dropping the timezone fixes this problem but I would rather keep it.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;What would be the best way to proceed?&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Modify the syslog source type?&lt;/LI&gt;
&lt;LI&gt;Create a new source type?&lt;/LI&gt;
&lt;LI&gt;Report the issue and hope for a fix?&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Sat, 25 Apr 2020 15:45:30 GMT</pubDate>
    <dc:creator>chutz</dc:creator>
    <dc:date>2020-04-25T15:45:30Z</dc:date>
    <item>
      <title>How to modify syslog source type to handle rfc3339 timestamp?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-modify-syslog-source-type-to-handle-rfc3339-timestamp/m-p/483064#M82756</link>
      <description>&lt;P&gt;We pass messages with rsyslog using the rfc3339 time format. It has microseconds, and it has a timestamp. But noticed a few issues:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;The time zone is not parsed out of the message. If I remove the microseconds from the timestamp, it would work fine.&lt;/LI&gt;
&lt;LI&gt;The host does not get parsed out. Seems to be a problem with the syslog-host transform which does not like the timezone. Dropping the timezone fixes this problem but I would rather keep it.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;What would be the best way to proceed?&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Modify the syslog source type?&lt;/LI&gt;
&lt;LI&gt;Create a new source type?&lt;/LI&gt;
&lt;LI&gt;Report the issue and hope for a fix?&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Sat, 25 Apr 2020 15:45:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-modify-syslog-source-type-to-handle-rfc3339-timestamp/m-p/483064#M82756</guid>
      <dc:creator>chutz</dc:creator>
      <dc:date>2020-04-25T15:45:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify syslog source type to handle rfc3339 timestamp?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-modify-syslog-source-type-to-handle-rfc3339-timestamp/m-p/483065#M82757</link>
      <description>&lt;P&gt;The best approach (IMO) is to create a new sourcetype that parses the data.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Apr 2020 16:37:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-modify-syslog-source-type-to-handle-rfc3339-timestamp/m-p/483065#M82757</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-04-25T16:37:02Z</dc:date>
    </item>
  </channel>
</rss>

