Our ServiceNow Discovery Connector extends your ServiceNow discovery sources into SCOM, allowing you to leverage the rich management pack discoveries and wide SCOM agent deployment to populate your CMDB with everything from servers and devices to databases, clusters, and services. All with no extra agents, so you are up and running in minutes not months!
Our latest version also brings with it some new features.
Gone are the days of pushing simple values returned from a key into ServiceNow; as this can result in duplicate CIs. With our new RegEx feature, we can now transform values using ‘regular expressions’.
So how does this work in practice?
Imagine you have a Linux Server which has been identified by ServiceNow’s own Discovery product and that server uses the Netbios name of the Linus Server as the default name field for each CI. This means for Cookdown Discovery to co-exist with ServiceNow Discovery, the CIs that are created by the Linux Server must use the Netbios name attributed to them.
This can be problematic! As when you look at the data in SCOM for the Linux Server, you will only find the FQDN of the server (“server01.mydomain.local” rather than simply “server01”). While this data is close, if you were to push CIs from SCOM using their FQDN, you would create duplicate CIs in ServiceNow.
Our RegEx feature means we get the Cookdown Discovery engine to drop everything after the first full stop in the Linux Server’s FQDN. In other words, we can drill down to get the “server01” tag from “server01.mydomain.local”. Meaning no more duplication, enabling you to get even more value from your existing SCOM data!
Discovery Scheduling you can now push new/changed CIs from SCOM on a schedule rather than manually and have a different schedule for each type of Discovery.
To start working smarter with our ServiceNow Discovery Connector click here.