<?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 Universal Forwarders not forwarding windows performance monitor inputs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarders-not-forwarding-windows-performance-monitor/m-p/153231#M31167</link>
    <description>&lt;P&gt;We are experiencing issues where some of our systems which appear to be configured properly will not forward certain windows performance monitor counters. The forwarders are controlled by a deployment server, and appear to be contacting the deployment server correctly, and forwarding windows event log events properly, but some or all performance monitor inputs do not get forwarded.&lt;/P&gt;

&lt;P&gt;Example of perfmon input in inputs.conf:&lt;/P&gt;

&lt;P&gt;[perfmon://Network Interface]&lt;BR /&gt;
_rcvbuf = 1572864&lt;BR /&gt;
counters = Bytes Received/sec;Bytes Sent/sec&lt;BR /&gt;
disabled = 0&lt;BR /&gt;
evt_dc_name =&lt;BR /&gt;
evt_dns_name =&lt;BR /&gt;
evt_resolve_ad_obj = 0&lt;BR /&gt;
host = $decideOnStartup&lt;BR /&gt;
index = perfmon&lt;BR /&gt;
instances = *&lt;BR /&gt;
interval = 20&lt;BR /&gt;
mode = multikv&lt;BR /&gt;
object = Network Interface&lt;/P&gt;

&lt;P&gt;One of the error messages we see in the splunkd.log after enabling DEBUG is:&lt;/P&gt;

&lt;P&gt;DEBUG ExecProcessor - Ran script: &lt;CODE&gt;"D:\Program Files\SplunkUniversalForwarder\bin\splunk-perfmon.exe"&lt;/CODE&gt;, took 6.345292 seconds to run, 0 bytes read, exited with code -1&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 17:08:34 GMT</pubDate>
    <dc:creator>sgarvin55</dc:creator>
    <dc:date>2020-09-28T17:08:34Z</dc:date>
    <item>
      <title>Universal Forwarders not forwarding windows performance monitor inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarders-not-forwarding-windows-performance-monitor/m-p/153231#M31167</link>
      <description>&lt;P&gt;We are experiencing issues where some of our systems which appear to be configured properly will not forward certain windows performance monitor counters. The forwarders are controlled by a deployment server, and appear to be contacting the deployment server correctly, and forwarding windows event log events properly, but some or all performance monitor inputs do not get forwarded.&lt;/P&gt;

&lt;P&gt;Example of perfmon input in inputs.conf:&lt;/P&gt;

&lt;P&gt;[perfmon://Network Interface]&lt;BR /&gt;
_rcvbuf = 1572864&lt;BR /&gt;
counters = Bytes Received/sec;Bytes Sent/sec&lt;BR /&gt;
disabled = 0&lt;BR /&gt;
evt_dc_name =&lt;BR /&gt;
evt_dns_name =&lt;BR /&gt;
evt_resolve_ad_obj = 0&lt;BR /&gt;
host = $decideOnStartup&lt;BR /&gt;
index = perfmon&lt;BR /&gt;
instances = *&lt;BR /&gt;
interval = 20&lt;BR /&gt;
mode = multikv&lt;BR /&gt;
object = Network Interface&lt;/P&gt;

&lt;P&gt;One of the error messages we see in the splunkd.log after enabling DEBUG is:&lt;/P&gt;

&lt;P&gt;DEBUG ExecProcessor - Ran script: &lt;CODE&gt;"D:\Program Files\SplunkUniversalForwarder\bin\splunk-perfmon.exe"&lt;/CODE&gt;, took 6.345292 seconds to run, 0 bytes read, exited with code -1&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:08:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarders-not-forwarding-windows-performance-monitor/m-p/153231#M31167</guid>
      <dc:creator>sgarvin55</dc:creator>
      <dc:date>2020-09-28T17:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarders not forwarding windows performance monitor inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarders-not-forwarding-windows-performance-monitor/m-p/153232#M31168</link>
      <description>&lt;P&gt;Once the customer got in touch with Microsoft, he was able to narrow it down to the "Dfsr" performance counter using exctrlst.exe (see: &lt;A href="http://blogs.technet.com/b/askperf/archive/2010/03/05/two-minute-drill-disabled-performance-counters-and-exctrlst-exe.aspx"&gt;http://blogs.technet.com/b/askperf/archive/2010/03/05/two-minute-drill-disabled-performance-counters-and-exctrlst-exe.aspx&lt;/A&gt; ). Once he disabled that counter all of their normal counters returned, and are now being forwarded correctly.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2014 21:11:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarders-not-forwarding-windows-performance-monitor/m-p/153232#M31168</guid>
      <dc:creator>sgarvin55</dc:creator>
      <dc:date>2014-07-22T21:11:49Z</dc:date>
    </item>
  </channel>
</rss>

