Contributor IIIWindows SNMP is slipping away
As you may have noticed Microsoft have stopped including the SNMP service by default on server builds and only supports SNMP v2 natively. In this ever increasing world of security exploits, SNMP v2 is seen as insecure and a liability to run on all but air gapped networks, so why is the ScienceLogic preferred way of monitoring Windows Services still using SNMP?
The SNMP Service monitoring allows you to monitor just the services of choice, unlike the blunderbuss PowerShell approach (where if the service is set to Automatic start-up and not running, it alerts).
A 2am called out for a clipboard service outage and some grumpy emails in my inbox, and I'm inclined to agree with the very grumpy DBA that it is not ideal.
Can we get some motion on sorting out the PowerShell monitoring, so that regardless of how we collect the service statuses we can alert consistently?
