• 0

WMI vs SNMP on Windows



Windows Server 2016, VM, but defined as standalone server in LogicMonitor.  One of the applications running on this server is Cisco Contact Server.
So OK, because it is a Windows machine I give it standard WMI credentials used for our Windows servers discovery.  Because the Cisco app uses SNMP v2c access I give it snmp.commnunity and snmp.version properties.
Discovery runs fine and everything is working OK but here's the issue.  A slight one but it is an issue nonetheless.... I end with multiple DataSources doing double monitoring for the same OS component.
I have 2 'CPU Cores' DS monitoring CPU.  One is using WMI and the other SNMP.  I have 'Interfaces-' DS listed twice.  I have 'Services-' and 'Windows Servivces'.  List continues.... I thought LM had a logic in place so only one of the protocols would be used (WMI vs SNMP).  What's the best practice to deal with this issue?

Link to comment
Share on other sites

1 answer to this question

Recommended Posts

  • 0

LogicMonitor doesn't prevent multiple protocols per device, many devices might use lots of different protocols, but instead LM uses "AppliesTo" conditions to determine what checks get applied. Some of them may have !windows() to they don't apply to Windows servers but like in this case, Windows or it's apps can support SNMP. I would just disable the duplicate checks at the device or group level.

  • Like 3
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.