How to verifying CI Updated with Discovery Schedule

[FWilks]

When there are situations, like Crowdstrike, is there a best way to validate CIs are being discovered without checking each table manually?  In my case, the Discovery Job and the individual CIs showed it ran successfully and updated, which was a misleading.  I also found that the Discovery Dashboard did not reflect the CI that were not updated.  It ended up requiring a second reboot for the jobs to kick back in and really update the CIs.

[Community Alums]

hi @FWilks , 

Below are the fields where you can check if CI was updated thru Discovery schedules. 

1) Look for updated, updated by and discovery source fields in the list view.

Updated ( time log should match with the discovery schedule log time)

Updated by (Should be the midserver name where the discovery schedule got trigged)

Discovery Source (Should be ServiceNow)

I hope that answers your query. i am not sure about CrowdStrike scenario you mentioned.

Regards, 

Srinija

[Sandeep _1]

You can look at the discovery status log for each scan and it will show you which identifier matched on the CI.   You'll see a line similar to this:

If its matching on something else you can modify the hardware identifier (discovery definition > identifiers) to suit your local needs.

[GaneshSuresh]

Interested to know how discovery and Crowdstrike are related here?🤔