Tag Based Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2022 03:51 AM
Hi guys,
We have historic services set up in our Prod environment, that are actively used in tickets (ie incidents). For this example, we will use ServiceNow
We are moving towards a cloud tag based service mapping approach, some of these services contain a servicename tag, the issue I am having is that when I try and map these tag based services, I get the below error:
"The following service names already exist. Change the names of the following service candidates to unique names: servicenow."
This is because the servicename tag for this service candidate is ServiceNow and the service ServiceNow already exists. If I change the candidate name to say ServiceNow 2, it will create the tag based service but this is not ideal.
Question is how do I update the existing Service with tagged cloud reources? How would I handle the change to tag based approach, regarding the creation of the candidates and historic ticket relationships..
Please help!
Thanks,
Rash
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2023 03:11 AM
Did you find a solution for this?