Perfmon plugin throws error

[ghost]

I installed the Perfmon plugin. With the default metrics everything works fine. I modify the perfmon_totals_counters.txt with the custom metrics below and modify the yml file.

When looking at the logs i get the following error c:\Program Files\perfmon_plugin_standalone>perfmon_plugin_standalone.exe Using Counters File: c:/Program Files/perfmon_plugin_standalone/config/perfmon_totals_counters.txt Memory/Available Mbytes[ms] : 7891.000000 Processor(_Total)/% Processor Time[ms] : 43.458636 LogicalDisk(_Total)/% Free Space[ms] : 10.595000 [2014-01-16 14:44:00 UTC] ERROR: Error occurred in poll cycle: undefined method `split' for nil:NilClass [2014-01-16 14:44:00 UTC] WARN: Component with name "MIADSI07" and guid "com.mtnsat.plugin.ics" had no metrics

* perfmon_totals_counters.txt * \Processor(_Total)\% Processor Time \Memory\Available Mbytes \LogicalDisk(_Total)\% Free Space

* newrelic_plugin.yml *

Please make sure to update the license_key information with the license key for your New Relic

account.

newrelic:

Update with your New Relic account license key:

license_key: 'xxxxxx'

Set to '1' for verbose output, remove for normal output.

All output goes to stdout/stderr.

verbose: 1

Proxy configuration

Uncomment and set if using a proxy:

proxy:

address: yourproxyhost

port: 8080

user: youruser

password: yourpass

To collect a customized set of Perfmon counters (BOTH steps are REQUIRED):

(1) Uncomment "guid" and set to your own GUID

(2) Uncomment "countersfile" and set to the list of perfmon counters you wish to collect

guid: com.mtnsat.plugin.ics countersfile: perfmon_totals_counters.txt

Agent Configuration:

agents:

perfmon:

local: yes hostname: MIADSI03

Set "debug: true" to see metrics in stdout instead of sent to New Relic"

debug: true

Set "testrun: true" to use input from local text/html files. Only parses input once, then quits.

testrun: false

[kohner86]

I'm having the same issue as well after I started using a custom set of performance counters.

[kohner86]

Looks like I was able to fix the error by setting up a new installation. The error seems to pop up when the perf counters being collected are edited after having run it before.