Potential Values for Completed Activity in discovery_device_historySummaryDuring different phases of discovery, you may see different values in the Completed Activity field on a discovery_device_history record. Below are some common examples of values, when you may see them, and what they mean. Value When you may see this value Meaning Alive, not active, not classified After Shazzam Device is responding, but it does not have any open (active) ports that we can run classification against. Active After Shazzam Device has open (active) ports that we potentially can run classification against. Classified After Classification Probe We were able to classify the device type and will be proceeding to the Identification stage Active, couldn’t classify After Classification Probe We were unable to classify the device type. Sometimes, this value will also include a reason for why we were unable to classify. Ex. Active, couldn't classify: No WMI connection Created CI After Identification Probe/Pattern or after Discovery - Device Complete Business Rule is ran (for new CI) New CI has been created based on identification results Identified CI After Identification Probe/Pattern Existing CI has been found based on identification results Identified, ignored extra IP After Identification Probe/Pattern Device has already been discovered via a different IP in same discovery status Updated CI After certain Exploration Probes/Patterns or after Discovery - Device Complete Business Rule is ran (for existing CI) CI has been updated with additional information And these are some of the less common values you may see. Value When you may see this value Meaning Unclassified After Shazzam (only for credential-less discovery and the Discover value on the Discovery Schedule is set to IP Addresses) For the credential-less discovery of the target IP, we were unable to match to an existing CI on the instance. Classified After Shazzam (only for credential-less discovery and the Discover value on the Discovery Schedule is set to IP Addresses) For the credential-less discovery of the target IP, we were able to match to an existing CI on the instance. Active, Windows Cluster VIP After Windows - Classify Device is a Windows Cluster VIP and will be updated as such. Classified, but disabled After Classification Probe We made a match to a Classifier type, but the classifier itself is disabled Classified, couldn't identify After Identification Probe/Pattern Couldn’t create or match to existing CI record Identified, not updating CI After Identification Probe/Pattern We were able to properly identify a CI record, but we are choosing not to update the CI