Creating Duplicate Record instead of Updating on the Manual Record.

[abakassahoo]

Hi Team,

I would require your help or suggestion on how this Service now Discovery works.

We have manually uploaded the data in Virtual Machine Instance table and later when the SNOW Discovery works,its started creating the duplicate record in the same Virtual Instance table rather than updating on the old record as the Names are same for both the records(Manual and SNOW created one).

Here I am unable to find the root cause of this issue.

[Krischan]

Hi,

Discovery tries to identify the existing items based on their item type. If your manually added items to not match the criteria (e.g. if the attributes are different or the values or the attributes are different) it recognizes the items and "never before seen" and creates new ones.

It basically works like with coalesce in transformation tables.

I'm not familiar with the ootb identifiers but you can have a look into the configuration and of course this wiki article might help, too.

It can be a bit irritation but usually works fine. Just make sure, you consider the fact, that your probes do not get access to all data on the target system... or that your serial numbers might get "invalidaded" because they match some criteria in the invalid serial numbers table. This can lead so situations like this one as well.

regards

Christian

[abakassahoo]

Thanks a lot Christian for the Quick response.Even I was tried exploring the identifiers for that class but still no luck.

I just want to know what is the identifier being mentioned OOB for the virtual machine instance class as I have uploaded the XML's of manual data for Virtual machine instance .

[Krischan]

Well, unfortunately, I don't have access to an instance with Discovery anymore.

What you could do is, delete the newly created one, run a discovery on it and then check the DIscovery Status log. it is pretty chatty about identification. Maybe you can find the rule there.

[robertgeen]

Hello Abakas,

Can you give a quick example of the type of data attributes you loaded in? As far as I know in Fuji and Geneva the virtual machine table extends the server table which extends the hardware table and thus the attribute you should be worried about is Serial Number. I suspect either the Serial Number is different or is blank and that could be what is causing it. I've attached a screenshot that shows you the CI identifier for the hardware table (it would get used by any of the child tables that extend it). It's also important to note that it does lookups in the serial number table for the serial number so even if the serial number is set in virtual machine but there is no entry in the serial number table then I believe that would cause it not to match. Keep in mind this is in Geneva so it might be different in your version as well. Check out the CI Identifier section in your instance for more information.