<?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: Syslog vs Forwarders in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491902#M84075</link>
    <description>&lt;P&gt;You will always need a syslog server but there are many good reasons to go with &lt;CODE&gt;syslog-ng&lt;/CODE&gt;.  I would not make this change unless you frequently need to adjust what is sent and you cannot admin directly.  With UFs/DS you can admin all of your splunk configurations by yourself &lt;/P&gt;</description>
    <pubDate>Thu, 21 Nov 2019 03:37:35 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-11-21T03:37:35Z</dc:date>
    <item>
      <title>Syslog vs Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491900#M84073</link>
      <description>&lt;P&gt;If I have an environment with an rsyslog collection server that is working just fine and collecting from thousands of endpoints, should I keep that or get rid of that and collect events using a UF on each endpoint?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 00:23:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491900#M84073</guid>
      <dc:creator>bpladna81</dc:creator>
      <dc:date>2019-11-21T00:23:40Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog vs Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491901#M84074</link>
      <description>&lt;P&gt;Hi bpladna81,&lt;/P&gt;

&lt;P&gt;Keep your rsyslog server for the syslog collection and install an universal forwarder on the same server to monitor the files the rsyslog server creates. Some good background information is available here &lt;A href="http://www.georgestarcher.com/splunk-success-with-syslog/"&gt;http://www.georgestarcher.com/splunk-success-with-syslog/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS &lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 01:38:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491901#M84074</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-11-21T01:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog vs Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491902#M84075</link>
      <description>&lt;P&gt;You will always need a syslog server but there are many good reasons to go with &lt;CODE&gt;syslog-ng&lt;/CODE&gt;.  I would not make this change unless you frequently need to adjust what is sent and you cannot admin directly.  With UFs/DS you can admin all of your splunk configurations by yourself &lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2019 03:37:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Syslog-vs-Forwarders/m-p/491902#M84075</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-11-21T03:37:35Z</dc:date>
    </item>
  </channel>
</rss>

