Loading...
Loading...
Discovery.device.complete events may take a long time to process, which causes the event queue to be backed up. Steps to Reproduce 01. Have a CI with multiple IP addresses, 200 +. 02. Create a discovery schedule to discover each of the IP addresses. 03. Discover CI. 04. Navigate to sysevents and check the processing time for each discovery.device.complete. 05. Confirm each discovery.device.complete took a long time due to the large number of IP addresses the CI has.
Update the discovery.device.complete script actions, "System Policy > Events > Script Actions", to check on the last_state of the discovery device history. If the last state is "Identified, ignored extra IP" there should be no need to process this event, as it is already processed via another discovery device history event. For example, add following to script action "Discovery - map device to netgears": var lastState = current.last_state; if (lastState == "Identified, ignored extra IP"){ return; } Script action "Discovery - map device to netgears" start would look like: (function() { var ciid = current.cmdb_ci + ''; if (!ciid) return; var lastState = current.last_state; if (lastState == "Identified, ignored extra IP"){ return; } Note: If using patterns, IP optimization needs to be setup in order for above workaround to work (glide.discovery.ip_based.active = false). See KB0694477.
PRB1397581
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.