I'm pulling together a (semi-comprehensive) comparison of the impact of monitoring via WMI versus SNMP.
The upshot for those who are impatient: WMI monitoring (whether WMI polling or WMI via SAM) has a measurable - but manageable - impact on both the target device and the poller.
That said, if you are considering converting your monitoring of Windows devices from SNMP to WMI, what are you gaining? What are you losing?
Here's the start of my list. Please add your own in the comments below. Note that this is an off-the-top-of-my-head list. Coherency comes later.
SNMP Monitoring (as compared to WMI)
WMI Monitoring (as compared to SNMP)
OK guys, there's the start of my list. What did I miss?
This is very timely for us. We are actually putting together this discussion now with Server 2012 stating it will have degraded SNMP and I can only assume after 2012 it will only get worse.
We are really having to dot our i's and cross our t's, because as I have stated in previous posts, our Data Security is run like the TSA and their concept of security is if you tell everyone "no" you have secured the environment.
WMI is much slower than SNMP. With Server 2012 WMI is even slower than it used to be. I generally always use SNMP when possible and use WMI as my 2nd option when necessary because of the speed. Also, WMI tends to be more "buggy", I have never really had problems with SNMP as it's much more reliable.
Nice list though, I look to what others have to say!
I concur with I prefer SNMP. Now that being said I will make some nodes WMI based when I upgrade to 5.5 because of the ability to poll mount points. It's really a shame however that there can't be a blended approach. I mean it's completely possible to build a SAM poller for a WMI query on an SNMP node but if the node is WMI based it's not possible to do any SNMP monitoring unless like the other user said it used to be SNMP at one point.
Totally agree.... SNMP is faster and when you have 15,000 elements its much nicer to the CPU and polling intervals.
We use WMI for our almost 700 applications and if there are alot of components it can sometimes timeout.
I say use SNMP for basic monitoring and WMI for the detailed items like applications....
" I mean it's completely possible to build a SAM poller for a WMI query on an SNMP node but if the node is WMI based it's not possible to do any SNMP monitoring unless like the other user said it used to be SNMP at one point."
Mike, would that mean that if we were monitoring the same node via SNMP, and changed it to WMI - we can still monitor it via SNMP?
This is something I ran into a while back in regards to WMI having an issue. WMI utilizes reverse lookup for confirmation so an invalid reverse lookup can cause WMI to fail.
I prefer SNMP and also wouldn't like to lose all of my historical data by converting a node from SNMP to WMI or vice versa. Since most all of my nodes were setup via SNMP I will stay the course barring any tremendous WMI improvement gains that would peak my interest again.
As a DoD admin SNMPv2 is now prohibited from being used. We are being forced to use WMI to poll all our Windows servers. Interface statistics are available via WMI directly. Why can't NPM pull interface statistics using WMI? Any hope for the capability to be added in the future?
From what I've seen, WMI *does* pull interface stats. However, I have both NPM and SAM and it's possible some of what I'm seeing is coming from SAM rather than native NPM.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.