<?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 Why is splunk-winevtlog.exe crash, low thruput, high cpu and other incorrect eventcode filtering not working? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/605180#M105204</link>
    <description>&lt;P&gt;splunk-winevtlog.exe crash, low thruput,&amp;nbsp;high cpu&amp;nbsp; utilization and eventcode filtering not working as expected with 8.1.x/8.2.x/9.0&lt;/P&gt;</description>
    <pubDate>Mon, 11 Jul 2022 21:11:21 GMT</pubDate>
    <dc:creator>hrawat</dc:creator>
    <dc:date>2022-07-11T21:11:21Z</dc:date>
    <item>
      <title>Why is splunk-winevtlog.exe crash, low thruput, high cpu and other incorrect eventcode filtering not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/605180#M105204</link>
      <description>&lt;P&gt;splunk-winevtlog.exe crash, low thruput,&amp;nbsp;high cpu&amp;nbsp; utilization and eventcode filtering not working as expected with 8.1.x/8.2.x/9.0&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2022 21:11:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/605180#M105204</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2022-07-11T21:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Why is splunk-winevtlog.exe crash, low thruput and other incorrect eventcode filtering not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/605182#M105205</link>
      <description>&lt;P&gt;If you have&amp;nbsp; filtering enabled that will filter more than one event e.g as follows, there is a known issue found with all 8.1.x/8.2.x and 9.0. Next 9.0.1 will have the fix. 8.0.x is not impacted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;whitelist1 = EventCode="299|342|394|500|501|528|624|627|628|629|630|644|672|4608|4610|4611|4614|4616|4622|4624|4625|4634|4647|4648|4662|4670|4720|4723|4724|4725|4726|4728|4729|4731|4732|4734|4735|4738|4740|4741|4742|4743|4756|4757|4767|4768|4769|4771|4776|4778|4779|4781|4800|4801|4904|4905|4907|4946|4947|4948|5136|5137|5140|5141"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Jul 2022 20:41:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/605182#M105205</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2022-07-11T20:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: Why is splunk-winevtlog.exe crash, low thruput and other incorrect eventcode filtering not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/632371#M108327</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am interested to know more if there is tactical remediation to this issue affecting 8.2.X? before upgrading to version 9.0&lt;/P&gt;&lt;P&gt;We are seeing very high CPU utilisation in our AWS EC2 instances, which has meant we have to restart the Splunk universal forwarder.&lt;/P&gt;&lt;P&gt;Appreciate if Splunk have a remediation for this.&lt;/P&gt;&lt;P&gt;Many thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2023 14:20:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-splunk-winevtlog-exe-crash-low-thruput-high-cpu-and-other/m-p/632371#M108327</guid>
      <dc:creator>Thundercat88</dc:creator>
      <dc:date>2023-02-27T14:20:00Z</dc:date>
    </item>
  </channel>
</rss>

