I know this is probably not what you want to hear but zenoss's built in process monitoring is deeply broken and buggy but I will try to inform you of things I have noticed about how it works because I can't say much for sure.
Windows uses three separate oids for processes(with the default windows snmp client atleast). It must match this, which is not necessarly the same as what windows task manager says it is. 1.3.6.1.2.1.25.4.2.1.4 # path 1.3.6.1.2.1.25.4.2.1.2 # command 1.3.6.1.2.1.25.4.2.1.5 # arguments You should not have to add it manually, it should show up after you add it to /processes in the classes menu. That said, I gave up on this and used nagios plugin I wrote instead and setup thresholds so I may be a little dated on my info. However using thresholds/templates actually works and allows you to use graphs, and escalation counts, and actually target specific devices instead of the whole tree. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25772#25772 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
