<?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: Export to Syslog in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Export-to-Syslog/m-p/58474#M11495</link>
    <description>&lt;P&gt;Sure. You can have Splunk forward on anything it indexes via syslog format. Generally, you configure the &lt;EM&gt;indexers&lt;/EM&gt; to forward on syslog, not the forwarders. The thing to note is that Splunk's Windows Event Logs will have internal newline characters. It &lt;EM&gt;shouldn't&lt;/EM&gt; cause any problems with receiving syslog agents, depending what they do with it though. I would nevertheless have you test it against your preferred receiver to see if you like the results.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Forwarddatatothird-partysystems#Forward_syslog_data" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Forwarddatatothird-partysystems#Forward_syslog_data&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Mar 2011 12:22:40 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2011-03-14T12:22:40Z</dc:date>
    <item>
      <title>Export to Syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Export-to-Syslog/m-p/58473#M11494</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;Does anyone know if it's possible to take logs that have been grabbed from Windows WMI and indexed, and then forward them on to a syslog server?&lt;/P&gt;

&lt;P&gt;This is a requirement here that needs to be met before the Admins will consider the program... needless to say it's causing me some grief so I thought I'd put it out here and see if any guru's can point me in the right direction...&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;

&lt;P&gt;DB&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2011 11:41:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Export-to-Syslog/m-p/58473#M11494</guid>
      <dc:creator>Scarecrowddb</dc:creator>
      <dc:date>2011-03-14T11:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: Export to Syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Export-to-Syslog/m-p/58474#M11495</link>
      <description>&lt;P&gt;Sure. You can have Splunk forward on anything it indexes via syslog format. Generally, you configure the &lt;EM&gt;indexers&lt;/EM&gt; to forward on syslog, not the forwarders. The thing to note is that Splunk's Windows Event Logs will have internal newline characters. It &lt;EM&gt;shouldn't&lt;/EM&gt; cause any problems with receiving syslog agents, depending what they do with it though. I would nevertheless have you test it against your preferred receiver to see if you like the results.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Forwarddatatothird-partysystems#Forward_syslog_data" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Forwarddatatothird-partysystems#Forward_syslog_data&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2011 12:22:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Export-to-Syslog/m-p/58474#M11495</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-03-14T12:22:40Z</dc:date>
    </item>
  </channel>
</rss>

