Forum Discussion

Dave_Lee's avatar
Dave_Lee
Icon for Advisor rankAdvisor
24 days ago

CMDB Integration

Hi all

I'm looking into setting up a sync from LogicMonitor into our Service Now.  The mechanics of doing so seem pretty straight forward with the LM CMDB sync application.

I want to make sure I'm putting devices into the right CI Classes in ServiceNow.  I plan to do so by setting up some dynamic groups, each pulling in the devices for each class, then assign a property to each dynamic group to define the class that the device belongs to.  This is all as described in LMs documentation on CMDB sync with Service Now.

For the CI Classes themselves... starting with network devices, Service Now has a generic "netgear" (as in network equipment, not the manufacturer Netgear!) which is extended by the following classes that are specific to device of network device.

cmdb_ci_ip_switch
cmdb_ci_ip_firewall
cmdb_ci_lb
cmdb_ci_ip_router

There is a property on all devices called predef.externalResourceType which would appear to be a perfect fit for this use case as it has values like Switch, Firewall, Router, LoadBalancer.  But, it's really designed for topology mapping and I'm not sure how the platform devices what value to assign.  In some cases, I've found it has an incorrect value - such as "Firewall" when a device is actually a "Switch" or in some cases "Unknown".

I'm thinking I might create my own AppliesTo function for each CI Class that I want to use, base it on the value of predef.externalResourceType but then have my own additional inclusions and exclusions.  Then I can tweak things as needed to fix any issues I find with incorrect values in the predef.externalResourceType.  Then I can use my AppliesTo functions in the Dynamic Groups and finally have a Dynamic Group for everything that isn't included in my AppliesTo functions - which can sync to a generic CI type.

Being an MSP, the things that are sync'd to the CMDB will be changeable, so will need this to be flexible and hopefully not require a load of upkeep!

If anyone has done this before, I'd be interested to understand how you defined which LM device goes into which CI class on your CMDB.

1 Reply

  • I also work at an MSP and can say we actually do this the opposite way. We utilize CMDB as our Source of Truth. That then we can leverage it to drive our monitoring. We know what we should be monitoring before it's in the tool. We then modified the SN->LM provisioning module in SN to take both the CI Class and a custom property we have on the CI to put the Resource into a specific technology folder.