Hey, I'm very new to Zenoss. My task recently at work has been to upgrade the current Zenoss system (2.5 on a literally unknown linux distro).
I have created a New VM on an ESXi Host, installed CentOS 6.4, and was easily able to configure it and run the auto deploy script provided on the Zenoss Install Wiki. I was very pleased with these results.
The old system just did ping tests on a listed amount of servers. The goal was to increase monitoring using more of the capabilities Zenoss offers. Heres the info I can provide, i hope its enough let me know if more info is requred:
Class = /Server/Windows/WMI
Modeler Plugins selected:
zenoss.wmi.CpuMap,zenoss.wmi.FileSystemMap,zenoss.wmi.IpInterfaceMap,zenoss.wmi.MemoryMap,zenoss.wmi.ProcessMap
Model Device Output:
2013-07-31 15:06:53,009 INFO zen.ZenModeler: Connecting to localhost:8789
2013-07-31 15:06:53,014 INFO zen.ZenModeler: Connected to ZenHub
2013-07-31 15:06:53,158 INFO zen.ZenModeler: Collecting for device FileServer.domain.local
2013-07-31 15:06:53,352 INFO zen.ZenModeler: WMI collector method for device FileServer.domain.local
2013-07-31 15:06:53,353 INFO zen.ZenModeler: plugins: zenoss.wmi.CpuMap, zenoss.wmi.FileSystemMap, zenoss.wmi.IpInterfaceMap, zenoss.wmi.MemoryMap, zenoss.wmi.ProcessMap
2013-07-31 15:06:53,355 INFO zen.ZenModeler: No Python plugins found for FileServer.domain.local
2013-07-31 15:06:53,356 INFO zen.ZenModeler: No command plugins found for dathomir.cudgc.local
2013-07-31 15:06:53,357 INFO zen.ZenModeler: SNMP monitoring off for FileServer.domain.local
2013-07-31 15:06:53,357 INFO zen.ZenModeler: No portscan plugins found for FileServer.domain.local
2013-07-31 15:06:59,614 INFO zen.ZenModeler: processing zenoss.wmi.CpuMap (Cache) for device FileServer.domain.local
2013-07-31 15:06:59,616 INFO zen.ZenModeler: processing zenoss.wmi.CpuMap (CPU) for device FileServer.domain.local
2013-07-31 15:06:59,618 INFO zen.ZenModeler: Collecting filesystems for device FileServer.domain.local
2013-07-31 15:06:59,619 INFO zen.ZenModeler: Collecting interfaces for device FileServer.domain.local
2013-07-31 15:06:59,621 INFO zen.ZenModeler: processing zenoss.wmi.MemoryMap for device FileServer.domain.local
2013-07-31 15:06:59,622 WARNING zen.ZenModeler: WMI process discovery is currently not supported
2013-07-31 15:07:00,511 INFO zen.ZenModeler: Changes in configuration applied
2013-07-31 15:07:00,512 INFO zen.ZenModeler: Scan time: 7.35 seconds
2013-07-31 15:07:00,514 INFO zen.ZenModeler: Daemon ZenModeler shutting down
Default Monitoring templates selected:
Device_WMI (/Server/Windows)
Error:
Resource: FileServer
Component: zen.winperf.PerfRpc
Event Class: /Status/Wmi
Status: New
Message: Bad Counter(s) - 5 bad counter(s) for device 172.16.xxx.xx
Event Management...
agent zenwinperf
component zen.winperf.PerfRpc
dedupid dathomir.cudgc.local|zen.winperf.PerfRpc|/Status/Wmi|bad_wmi_counter_consolidation_event|3
eventClass /Status/Wmi
eventClassKey
eventClassMapping
eventGroup
eventKey bad_wmi_counter_consolidation_event
eventState New
evid 000c298f-1444-bb75-11e2-fa1ce8cf3ca4
facility
message Bad Counter(s) - 5 bad counter(s) for device 172.16.xxx.xx
ntevid
priority
severity 3
summary Bad Counter(s) - 5 bad counter(s) for device 172.16.xxx.xx
Device State...
DeviceClass /Server/Windows/WMI
DeviceGroups
DevicePriority Normal
Location
Systems
device FileServer
ipAddress 172.16.xxx.xx
monitor localhost
prodState Production
Event Data...
clearid
count 3
firstTime 2013-07-31 15:08:03
lastTime 2013-07-31 15:08:03
ownerid
stateChange 2013-07-31 15:08:03
Event Details...
details \LogicalDisk(\\?\Volume{97bf102a-8671-11e2-a005-806e6f6e6963})\Disk Read Bytes/sec,
\LogicalDisk(\\?\Volume{97bf102a-8671-11e2-a005-806e6f6e6963})\% Disk Read Time,
\LogicalDisk(\\?\Volume{97bf102a-8671-11e2-a005-806e6f6e6963})\Disk Write Bytes/sec,
\LogicalDisk(\\?\Volume{97bf102a-8671-11e2-a005-806e6f6e6963})\% Disk Write Time,
\LogicalDisk(\\?\Volume{97bf102a-8671-11e2-a005-806e6f6e6963})\Free Megabytes
explanation These WMI performance counter(s) are being queried, but the specific performance counter(s) are not on the remote system
manager Zenoss
resolution Stop monitoring the component or fix and/or remove the performance counter name from the monitoring template. 'typeperf -q' on the remote system will show available counters
zenoss.device.device_class /Server/Windows/WMI
zenoss.device.ip_address 172.16.20.44
zenoss.device.priority 3
zenoss.device.production_state 1000
I found this fourm post, thread/16187 and attempted the trnsform script provided, but that did not resolve the Issue, i still get this error in my events on Zenoss. I can see all the info I would like to see via the WMI modeliing I just really would like not to see this error. I am able to see what the disk usuage is for each disk on the device so i'm not sure what exactly its complainnig about and i can't for the life of my find where in Zenoss I would disable this monitoring request.. Thoughts?
Oh and the Server being monitored via WMI is Windows Server 2008 R2.
