CI Classification Issue in CMDB – Virtual Machine Identified as Deployed Marketplace Product

[Shraddha Dube]

Hello Community,

We are part of the Discovery team and have encountered an issue during CI classification in CMDB.

We received a change task (ctask) where the Configuration Item (CI) is a virtual machine. This was confirmed through the Discovery logs, which correctly identified the CI as a virtual machine instance. However, upon reviewing the CMDB, we noticed that the CI is classified under the "Deployed Marketplace Product" class instead of "Virtual Machine Instance".

We would like to understand:

1. What could be the possible reasons for this misclassification?
2. Are there specific identification or classification rules that might be causing this behavior?
3. As the Discovery team, what steps can we take to correct this and ensure accurate CI classification going forward?

Any insights or guidance on how to troubleshoot and resolve this issue would be greatly appreciated.

Thank you!

[srinija_itom]

Hi @Shraddha Dube , 

 Can you help me with the name of the discovery pattern in the discovery logs? 

I think this misclassification can happen in two areas. One is CI classifiers level and other is discovery pattern level. As this is a vm, I am assuming this happening inside the discovery pattern code. 

Regards, 

Srinija

[Shraddha Dube]

Hi @srinija_itom ,

During the validation of a Configuration Item (CI) in the CMDB, we observed a discrepancy between the discovery logs and the CMDB record for a specific CI.

Details:

• In Discovery Logs, the CI is correctly identified and classified as a Virtual Machine but we are not able to see which discovery pattern is getting used here.
• However, in the CMDB table, the same CI is currently categorized as a Deployed Marketplace Product.
• This inconsistency is observed only for this particular CI.
• As part of the current change task, we need to validate and correct the CI classification in the CMDB to reflect it as a Virtual Machine Instance, aligning it with the discovery data.

Please help us to find out the issue and how can we change class type for this CI as discovery admin.

Thanks,

Shraddha

[Mannapuram]

Hello, provided feedback with an 'arrow ->' below. 

• In Discovery Logs, the CI is correctly identified and classified as a Virtual Machine but we are not able to see which discovery pattern is getting used here.  -> Discovery Pattern for later stage, not classification. After Discovery run, under the tab 'ECC Queue', sort by Creation time, after Shazzam stage, it will mention Classifier used under 'Topic and Name'. 
• However, in the CMDB table, the same CI is currently categorized as a Deployed Marketplace Product. -> What is the CI classified under 'Devices' tab after Discovery run. Is it VM instance or Deployed Marketplace. 
• This inconsistency is observed only for this particular CI. -> What exactly is the class Deployed Marketplace? Is it a custom one? There is no such class in OOB.  
• As part of the current change task, we need to validate and correct the CI classification in the CMDB to reflect it as a Virtual Machine Instance, aligning it with the discovery data. -> This will be fixed, if the CI is under correct Class in CMDB.

[mattiaditro]

Hi,

we have the same issue & concert as @Shraddha Dube .   Can we have a link to proper documentation that describe this behaviour and pattern in details? 
BR