<?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 Performance Tuning or Other Hints for Windows Event Forwarding in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Performance-Tuning-or-Other-Hints-for-Windows-Event-Forwarding/m-p/572678#M101342</link>
    <description>&lt;P&gt;We have been using WEF as our collection point for a while.&amp;nbsp; We started out small but have expanded the range of events over time.&amp;nbsp;&amp;nbsp; We have ~5,000 hosts forwarding to a single collector.&lt;/P&gt;&lt;P&gt;The collector is busy, but seems to be healthy based on conventional Windows indicators.&lt;/P&gt;&lt;P&gt;However,&amp;nbsp; we have some data loss between the centralized event and Splunk (cloud).&amp;nbsp;&amp;nbsp; Logs show up in the WEF collection log but never make it to the index.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First,&amp;nbsp;&amp;nbsp; are there any performance tuning suggestions you can offer UF on a WEF collector?&lt;/P&gt;&lt;P&gt;Second,&amp;nbsp; can you think of any way to check on processing of a single event once it goes into the UF and heads to the indexer?&lt;/P&gt;</description>
    <pubDate>Wed, 27 Oct 2021 15:28:16 GMT</pubDate>
    <dc:creator>hughkelley</dc:creator>
    <dc:date>2021-10-27T15:28:16Z</dc:date>
    <item>
      <title>Performance Tuning or Other Hints for Windows Event Forwarding</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Performance-Tuning-or-Other-Hints-for-Windows-Event-Forwarding/m-p/572678#M101342</link>
      <description>&lt;P&gt;We have been using WEF as our collection point for a while.&amp;nbsp; We started out small but have expanded the range of events over time.&amp;nbsp;&amp;nbsp; We have ~5,000 hosts forwarding to a single collector.&lt;/P&gt;&lt;P&gt;The collector is busy, but seems to be healthy based on conventional Windows indicators.&lt;/P&gt;&lt;P&gt;However,&amp;nbsp; we have some data loss between the centralized event and Splunk (cloud).&amp;nbsp;&amp;nbsp; Logs show up in the WEF collection log but never make it to the index.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First,&amp;nbsp;&amp;nbsp; are there any performance tuning suggestions you can offer UF on a WEF collector?&lt;/P&gt;&lt;P&gt;Second,&amp;nbsp; can you think of any way to check on processing of a single event once it goes into the UF and heads to the indexer?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Oct 2021 15:28:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Performance-Tuning-or-Other-Hints-for-Windows-Event-Forwarding/m-p/572678#M101342</guid>
      <dc:creator>hughkelley</dc:creator>
      <dc:date>2021-10-27T15:28:16Z</dc:date>
    </item>
  </channel>
</rss>

