Tag a CI to multiple locations via customization

K14an
Tera Contributor

Hi folks,

 

I have come across a sort of wierd ask from one of my stakeholders related to storing the data in CMDB.

 

Currently, we have majority of CIs following the below naming convention and associated with respective locations

<AppName> + <Location A> + <Environment>    tagged to    <Location A>

 

A new vertical wants us to allow storing the apps in below format:

<AppName>   tagged to    <Location A>,  <Location B>,  <Location C>

 

This would mean changing the location field type to "List". I want to deny this option but need more backing. Can someone please help me with some justifications why this is not a recommended practice?

5 REPLIES 5

AJ-TechTrek
Giga Sage
Giga Sage

Hi @K14an ,

 

As per my understanding this is not the best practice, one application which is running on Server A is should part of Datacenter a and that datacenter belongs to location A., Location should be updated based on the CI location to that Associated APP or Server. One Server cant be run from Different location.

 

Also Application can be logical entity if they want use the logical Application name not which is discovered by the ServiceNow, They we can do that but make sure you mentioned the Pros and cons of it.

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

 

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

 

 

Hi @AJ-TechTrek ,

 

Thank you for responding. The 1st point is something we have communicated, however the 2nd point is interesting. What are the pros & cons of it?

"Also Application can be logical entity if they want use the logical Application name not which is discovered by the ServiceNow, They we can do that but make sure you mentioned the Pros and cons of it."

SteveMacWWT
Kilo Sage

Are they looking to track what ‘locations’ are served by the application, or where it is located? Are you talking about Application Services? 

 

If you are talking about where the Application is located, then there would be multiple instances (or stacks - Dev/Test/Prod) of the App Service. 

Hey @SteveMacWWT , 

They are looking specifically for Application services - they want to create 1 logical entry of the application in the form, and tag with multiple locations such as - USA, UAE,Australia etc.