Child CI Location = Empty

[s03jlord1]

Hi,

Is it by design that some 'lower level' CIs do not pick up the location details, from its parent discovery run?

Example: apache webserver/tomcat/MS SQL Database/Disk/MSSQL cluster node/disk.

I could go on but basically we discovered our first DC (lets say the location is Dublin DR DC ) to around 95% and using the dashboard. reports, workspaces of 'Dublin DC' the owners of the DCs interrogate what they wanted to see. The discovery ended with around 1500 CIs of which the owners said we had got 95% of the estate with a few things to fix...

However i was looking around at the CMDB_Ci.list and noticed a had a 2-3 thousand CIs, like the classes in my example, that were all set to location = empty where their 'parent CI' does have the location preset.

Any guidance appreciated.
Thanks

[SteveMacWWT]

Smarter people than me may feel differently, but if I needed that info for those types of CIs, I would be getting it from the parent CI via a CMDB Query. 

[CMDB Whisperer · Accepted solution]

Out of box the primary use of Location on CIs is on Hardware CIs, because they generally have a distinct physical/geographical location, whereas when you look at logical CIs, the having a Location actually may mean something different.  If you were to define a Service with a Location for instance, does that Location describe the location of the service providers, the service consumers, or the applications used to deliver that Service?  But as to your specific question, if we're talking about the installed Applications that literally Run On a Server, I do think there is justification to create a rule whereby the Runs On relationship causes that Location to cascade from the Server to the Application.  But I would be wary of doing anything like that beyond the Application.  In any case, no, nothing like that exists out of the box.