Options to resolve high CPU use on target CI when running service mapping discovery<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Description High CPU use may occur on target configuration items (CI) when Service Mapping discovery runs. When Service Mapping (vertical discovery) is initiated: It creates discovery tasks and sends them to MID Servers via the ecc_queue.Tasks are created based on the entry points configured in the application service.Each task runs a discovery pattern on the target IP address to collect data.The process may lead to the discovery of additional endpoints, creating more tasks.This cycle continues until there are no new connections or tasks to process. Tasks are distributed across MID Servers using the MID Server selection algorithm. The IP address displayed in the ecc_queue is usually the "main" IP from the ip_address field of the CI. For example: A Windows server has IP A in cmdb_ci_win_server.ip_address and IP B in cmdb_ci_ip_address.In the ecc_queue, the output record displays IP A. Note: If the IP is found in the load balancer IP Service table [cmdb_ci_lb_service], an entry is created for the load balancer. Cause High CPU use on a target server may occur due to: Too many discovery tasks sent to the server. This often happens when: A discovery pattern creates unnecessary connectionsTraffic-based discovery runs in the background CPU-intensive steps in a discovery pattern.Insufficient server resources allocated. Resolution Too many tasks are sent to a target Check the pattern logic Review the pattern log to see if it is creating multiple or unnecessary connections.Adjust the pattern to reduce unnecessary connections. Traffic-based discovery runs Verify if connections were created by traffic-based discovery.If not required, disable traffic-based discovery Adjust concurrent task limits System property sa.max_concurrent_service_discovery_tasks Controls the maximum number of concurrent non-inclusion Service Discovery tasks.Default: 100. MID Server parameter mid.servicewatch.max_concurrent_connections Limits the number of concurrent tasks sent to a single host by one MID Server.Default: 7. Reducing these values can lower the load on target servers. Too many MID Servers targeting the same host Limit the number of MID Servers that can connect to the same target by adjusting: IP ranges assigned to MID Servers.Application setups for MID Servers. Disable Traffic-based discovery Option 1: Turn off globally Set the sa.traffic_based_discovery.active system property to false. Option 2: Turn off for a specific CI or CI type Create a traffic-based rule in the sa_traffic_based_rules table. Option 3: Turn off for a specific service In the application service page, set Traffic-based discovery to false.Note: This stops creating connections in the service map but does not stop background tasks. Target resources may still be consumed. Determine if task output was created by traffic-based discovery Open the ecc_queue record.In the payload, look for the endpoint sys_id: <parameter name="endpointId" value="sysIdValue"/> Go to the cmdb_rel_ci table: Find the relationship where: CHILD = CI with the sys_id found above.TYPE = Use End Point to::Use Point From Copy the sys_id of this relationship.Navigate to the cmdb_rel_attributes table: Find the record where the relationship field matches the sys_id.If Qualifier type is Traffic Based, the task was created by traffic-based discovery. Find connections created by the pattern Open the Service Map pattern discovery log for the CI.Review the connection sections.Steps that created connections have "[created]" appended to the step name.