werafetish.blogg.se - Solarwinds network performance monitor vs prtg

CON will not work across a NAT-ed WAN connection (VPN, etc).

Work around: per-server config can nail down WMI to just a couple of ports.

CON significantly more firewall ports required.

PRO Account settings used by SAM automatically.

Work-around: If the machine has EVER been an SNMP polled device, the snmp info is retained and custom pollers can be used (at least until the SNMP RO string changes).

CON WMI-only devices cannot use custom pollers (UnDP).

PRO Extremely efficient use of CPU, RAM and bandwidth (on both target and poller).

Work-around: set up UnDP for hrSystemUptime.

CON Uses SNMP service start time for uptime metrics, rather than actual server reboot time.

CON Changing SNMP string requires enterprise-wide changes.

PRO No single point of failure for access.

PRO Fewer ports for enterprise firewall rules (translates to an easier time getting security to agree to variances).

CON Requires additional non-default configuration actions (enabling snmp agent, setting RO string, etc).

CON Challenges configuring earlier versions of Windows (NT, W2k).

CON Cannot monitor Windows Volume Mount points.Note that this is an off-the-top-of-my-head list. Please add your own in the comments below. That said, if you are considering converting your monitoring of Windows devices from SNMP to WMI, what are you gaining? What are you losing? 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. I'm pulling together a (semi-comprehensive) comparison of the impact of monitoring via WMI versus SNMP.