Service Mapping stops displaying connecting nodes at some point after discovery is complete


If you run a deep, top-down/vertical Service Mapping discovery, you may run into an issue in Service Mapping where the discovered bottom nodes do not display outgoing connections to the next node(s) even though the discovery logs tell you that these outgoing connections have been successfully created and no errors were found.


The problem in this scenario is that Service Mapping discovery of the Business Service may have reached the depth of the service model recomputation.

You can increase the service model recomputation depth. Add the property named glide.service_mapping.computation_depth to the sys_properties table with a value of 30 (the default is 25). Then run the following script where 939137dd4ff4830056dc70021310c779 is the sys_id of the business service as an example:

var gr = new GlideRecord('cmdb_ci_service_discovered');
gr.get('939137dd4ff4830056dc70021310c779'); // the business service sys_id
var layerId = gr.layer;

var layerGr = new GlideRecord('svc_layer');

var env = sn_svcmod.ServiceContainerFactory.loadEnvironment(layerGr.environment);
var allLayers = env.layers();
for (var i = 0 ; i < allLayers.length ; i++) {
var layer = allLayers[i];


This script syncs the service model for the business service without deleting the history.

If you need to, you can increase glide.service_mapping.computation_depth and run the script again.

Article Information

Last Updated:2017-10-25 07:27:55