Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

CMDB - Discovery - Normalization and impact on Incident Software CIs

mathieu_brule
Kilo Sage

Hi everyone,


I have many interrogations about normalization (in SAM Foundation), and impact on CIs, which can be selected in Configuration Item field in incidents (or other processes).


let me explain :

When creating an incident, and selecting a Software CI (let's say Microsoft Teams Classic), I have duplicated ones, but with a different version, as we can see in following picture of cmdb_ci_spkg table :

Duplicated Teams classic.png
These CIs have been discovered.


I've undestood that I have to manually configure normalization on models, by setting Publisher, Product and Version in the Discovered model, for "grouping" the discovered models on only one model.

For example, Microsoft Teams Classic with version 1.7.0.17852/1.7.0.3851/... can be considered and grouped as Microsoft Teams Classic 1.7.0.


Here are my questions :

1- when I manually configure the normalization, how do I process to set all my Software installations to the "grouped" model ?

2- On incident side, how can I have software grouped in one software CI, relative to one normalized model ? Said differently, how can I avoid to have multiple cmdb_ci_spkg records for teams classic records which have the same 1.7.0 version ?

How the normalization impact the cmdb_ci_spkg records ?


Thanks for your answers !

 

0 REPLIES 0