<?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 Event logs from Snare not organized like Windows Universal Forwarder does? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Event-logs-from-Snare-not-organized-like-Windows-Universal/m-p/80971#M16698</link>
    <description>&lt;P&gt;I have been using the Snare agent to send my Windows Event logs to syslog-ng then off to Splunk with the Linux Universal forwarder. Everything is working great but the event logs that show up in Splunk are not organized how the regular Windows Universal forwarder sends them. With the setup I have now the entire event log is all squished together, with the Windows universal forwarder it puts everything on its own line in a very organized and easy to read fashion. I also noticed that the universal forwarder gets rid of the paragraph long informational junk that is with certain event logs.&lt;/P&gt;

&lt;P&gt;Is there anyway to fix this? I assume this is more of a Snare issue but other people must have had this problem before.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Oct 2012 05:50:42 GMT</pubDate>
    <dc:creator>johns3</dc:creator>
    <dc:date>2012-10-05T05:50:42Z</dc:date>
    <item>
      <title>Event logs from Snare not organized like Windows Universal Forwarder does?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Event-logs-from-Snare-not-organized-like-Windows-Universal/m-p/80971#M16698</link>
      <description>&lt;P&gt;I have been using the Snare agent to send my Windows Event logs to syslog-ng then off to Splunk with the Linux Universal forwarder. Everything is working great but the event logs that show up in Splunk are not organized how the regular Windows Universal forwarder sends them. With the setup I have now the entire event log is all squished together, with the Windows universal forwarder it puts everything on its own line in a very organized and easy to read fashion. I also noticed that the universal forwarder gets rid of the paragraph long informational junk that is with certain event logs.&lt;/P&gt;

&lt;P&gt;Is there anyway to fix this? I assume this is more of a Snare issue but other people must have had this problem before.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Oct 2012 05:50:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Event-logs-from-Snare-not-organized-like-Windows-Universal/m-p/80971#M16698</guid>
      <dc:creator>johns3</dc:creator>
      <dc:date>2012-10-05T05:50:42Z</dc:date>
    </item>
    <item>
      <title>Re: Event logs from Snare not organized like Windows Universal Forwarder does?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Event-logs-from-Snare-not-organized-like-Windows-Universal/m-p/80972#M16699</link>
      <description>&lt;P&gt;No, this is how Snare formats its logs. It cannot use newlines in its messages because that would violate the syslog standard. I've found no way of reliably finding points in these messages where you can exchange certain whitespace characters for newlines.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Oct 2012 06:50:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Event-logs-from-Snare-not-organized-like-Windows-Universal/m-p/80972#M16699</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-10-05T06:50:53Z</dc:date>
    </item>
  </channel>
</rss>

