Tag based Service Mapping

Nisha30
Kilo Sage

3 weeks ago

Hello ITOM Experts,

Need some Step by Step guidance.  Have gone through documentation and many threads.

Still confused , how tagged based Service Mapping to be implemented.

 

Q1. Is Basic discovery be done for CIs with Tags (key value etc.) (for non cloud and cloud both)

 

Q2. What exactly in sequence to be done for Tag based discovery.

 

Q3.  What has to be done to get List of CI to be available for 'View Service Candidates' ?

 

Pretty sure I am missing things but if anyone can help step by step (Product document did not get much out of which new to this Service Mapping piece)

 

Thanks

0 Helpfuls
  • 474 Views
1 REPLY 1

sizzleMcFace
Giga Guru

3 weeks ago - last edited 3 weeks ago

Hi,

Yes, tags must be discovered (cloud discovery or regular Discovery) and are stored as key/value pairs (cmdb_key_value). Tag-based mapping uses those discovered tags to build candidates and works best for cloud resources but can be used for on-prem if you consistently apply tags.

 

Prepare a tagging taxonomy and configure the tag categories/keys you will use, run Discovery/Cloud Discovery so tags appear in cmdb_key_value, create or configure a Tag-Based Service Family (or open an Application Service and choose the “Tags” method), run Populate/Manually Update Candidates and then use View Service Candidates to preview and map the generated candidates into services. (For more info, see: Prepare for mapping application services based on tags)

 

To get CIs listed under View Service Candidates ensure those CIs actually have discovered tag values for the selected tag categories/keys (ServiceNow only creates candidates for CIs with matching tag values), verify tags exist in cmdb_key_value and that your Tag-Based Service Family references the correct keys, and run the populate/manually update job if candidates aren’t appearing.

 

0 Helpfuls