Gartner Market Guide for IT Infrastructure Monitoring Tools
GET THE GUIDE
LIVE WEBINAR: 2/27, 1 p.m. CSTGoogle and Zenoss will bring contemporary applications of state-of-the-art AI and machine learning technologies to life.
Zenoss is the only enterprise monitoring solution certified Nutanix Ready - Integrated.
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
This ZenPack is developed by the Zenoss user community and supported via our online forums. Zenoss, Inc. does not provide direct support for this ZenPack.
The Windows SNMP Service Monitor ZenPack allows Zenoss to monitor Windows Services via SNMP. It automatically links to the /Server/Windows device class. After installing the pack you can simply remodel devices in /Server/Windows and Zenoss will discover any services running on them.
Make sure that you lock the services to prevent them from being removed during a remodel while a service is down. Modeling will only pick up services that are running.
During installation and removal the ZenPack rebuilds device relations for all devices within the /Server/Windows device class. Depending on the number of devices that you have in that class, it can take a long time. You will notice some errors in the UI while the relations are being rebuilt, which is normal. Please be patient and allow it to complete. After the relations have been rebuilt Zenoss should be restarted. Make sure that the zenwinsrvsnmp daemon is running after the restart is performed.
Note that you need to remodel your devices for the above to take effect.
Keep in mind that zWinServiceSNMPIgnoreNames is constantly in use. If you put the same service name in both zWinServiceSNMPIgnoreNames and zWinServiceSNMPMonitorNames it will be ignored.
Generally changes to monitoring status are immediately pushed to collector daemons, but sometimes if the daemon is too busy the daemon misses the change. In those cases the monitoring status doesn't get picked up by the daemon until the next reconfig cycle, which can take a while. If you notice that you're often still getting windows service down notifications shortly after you've toggled monitoring off on a windows service, you can add the following transform to the /Status/WinServiceSNMP event class to resolve this (this transform will only work on Zenoss 4.2.x and later).
# drop events for unmonitored winservicesnmp components
if component.monitor == False: evt._action = 'drop'
View the discussion thread.
This ZenPack is developed and supported by the Zenoss User Community. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Community ZenPacks.