"Display Name" of SW record is different than "Discovered Product" of Discovery model

[PCN12]

I manage normalization of SW data. In my training it was explained to me that cmdb_sam_discovery_model is aggregated data of cmdb_sam_sw_install table. It came to my attention that there are instances where “Display name”( which is afaik name of software as it is discovered by the tool) in the sw install table is not in sync with “Discovered Product” in cmdb_sam_discovery_model table.

I see this for a few records of Red Hat, IBM, and other publishers. But it is not consistent.

Example:

Sw record “redhat-release” is in DM discovered product: “Red Hat Red Hat Enterprise Linux X.X”

Some sw records with “redhat-release” is in DM “redhat-release” (no changes)

For both the primary key of these discovery models displays “Red Hat.redhat-release*).

The changing from redhat-release to “Red Hat Red Hat Enterprise Linux X.X”  causes a two version in the DM and hence is excluded from automatic normalization (weirdly enough the versions are different).

Most of the difference between display name in sw install table and discovered product in DM goes align with what is done during normalization. I checked SN Knowledgebase for information about this behavior but unsuccessfully.

My first question, is the update of the discovered product field of the DM an OOB SAMPro feature? If so, where can I find more information about it?

Second question, when content team creates normalization rules, is it based on the values in Discovered Publisher, Discovered Product and Discovered Version field or is it based on the value of the Primary Key of the discovery model?

Thank you for your help!

[dreinhardt]

Hi @PCN12,

got your point about the responsibilities! 🙂 Are you able to PoC the discovery process for Red Hat/Unix with ITOM Discovery instead of your custom solution. This could help to adjust the custom integration to import the same data as a supported integration does.

Best, Dennis