Which is the source of data populating the "Name" field on CMDB via Discovery

[mdavis933]

Which would be the steps to provide to an Infrastructure team in order to get discovery reading the name of the CI with the FQDN. Example

Server name                                     CMDB Name                                     

exampleserver1.mydummyorg.com     exampleserver1           <--how it is currently

exampleserver1.mydummyorg.com     exampleserver1.mydummyorg.com   <--how People want to see the data

The idea is to no change anything on probe sensor as I am getting most of the discoverable records with the desired format so my assumption is that on the server ( Windows or Linux) something needs to be changed but I am not sure about what that is.

Thanks

[chuckm]

In the Discovery properties select the following property:

Include domain name in host name: If "yes", include the domain name as part of the host name. For example, "bosco.service-now.com" instead of "bosco".

[mdavis933]

Hi Chuckm

Indeed it is true... As I mention what I am looking is for some insight on how the server should be updated on itself ... I don't think there is nothing on the ServiceNow side to be done since due to the property you are mentioning other records get properly updated

[chuckm]

The best way to figure out why the FQDN value isn't being populated for the Server name is to debug the individual server. If you are using the Pattern-based discovery, you can debug using the Pattern designer.  For windows servers you would use the Windows OS - Servers pattern to debug.  The hostname is assigned to the name attribute [name] in step 9. Insert System, OS and CPU data to cmdb_ci_win_server as shown.

If you are not getting the expected value in step 9, then you can look at the previous steps to determine where the issue is.

[mdavis933]

This is good. In my case is a Linux server but you gave me an idea. On my org we still use probe/sensor but I can debug via Patterns.

Thanks