Discovery source Service-now vs. ServiceNow

[robpickering]

We recently purchased Discovery from ServiceNow and I just finished taking the Discovery - Fuji virtual training class.

In our lab systems on Fuji, it appears that the "Discovery source" is always set to "ServiceNow" when Discovery adds or updates a CI in the CMDB.   However, in our Fuji test system, when I run Discovery, the Discovery source is being set to "Service-now".

Any ideas why?   We're going to writing various reports and notifications, and I'd prefer to not have to code to both conditions when trying to determine how a CI was added or updated in the CMDB.

-Rob

[robpickering · Accepted solution]

Doug, thanks for digging into this with me.   We have a nifty global search enabled on our Instance thanks to our work with Crossfuze.   I decided to utilize that and look what I found:

glide.discovery.source_name - The default ServiceNow name for populating the discovery_source field for CIs. Old customers will continue to have "Service-now" as the default where as new customers will have "ServiceNow" as the default.

Ours was last modified on 1/24/14 which is when we upgraded to Dublin.   I'm guessing that everyone who was on Calgary got this System Property set, so that Discovery Source would remain consistent over time.   However, in our case, we never implemented Discovery, so now it ends up just forcing customers who do adopt to have a legacy setting.

I've updated ours to "ServiceNow" to give us a more modern feel.  

-Rob

[alan_lowrance]

I just had to rebuild our MID Server for discovery (to get off Windows 2008 R2) and with the new MID server it wouldn't update our old CMDB records because of the mismatched discovery source field.  Luckily I knew how to use background script to change everything to update the source to the new spelling.

[Runjay Patel]

Check out this video, it will clear all your doubts and help you to understand Discovery queries in details.

Link: https://www.youtube.com/watch?v=30JbWVsusyE&t=10s&ab_channel=ServiceNowHelpdesk

It help you to understand below points.

• Discovery Overview
• Discovery prerequisite
• Understanding Discovery Phases in details
• Discovery credentials and IP Affinity
• Mid Server Management with Cluster and Load Balancer
• Schedule jobs
• Set up discovery from scratch to end
• Live implementation with real world data.
• Troubleshooting on various aspects
• Many more other issue related to mid server, CIs
• Cloud discovery
• Service Mapping

Please mark reply as Helpful/Correct, if applicable. Thanks!!