How to include on-prem server in Tag Based Service Map

[SalilD]

We have an application hosted primarily in Azure, and its components are mapped using tag-based service mapping. However, there's one on-premises server running an NGINX service that directly communicates with a PostgreSQL resource in the cloud.

I want to include this on-prem server in the tag-based service map. Is it possible to establish a connection between the on-prem CI and the cloud-tagged components in the service map?

Specifically:

• Would creating a traversal rule between the cmdb_ci_cmp_resource (cloud resource) and cmdb_ci_nginx_web_server (on-prem server) tables help establish this relationship?
• Is this kind of hybrid mapping (on-prem CI + tag-based cloud components) even supported in Service Mapping?

Looking for guidance on whether this approach is feasible and if there are best practices or alternative methods to achieve this.
#servicemapping #discovery  #itom #cmdb

[AJ-TechTrek]

Hi @SalilD ,

Q1: Can a Traversal Rule between cmdb_ci_cmp_resource (Azure PostgreSQL) and cmdb_ci_nginx_web_server (on-prem) help?

Yes, but with conditions:

* Traversal Rules are used to define how Service Mapping moves from one CI to another in a pattern.
* In your case, creating a custom traversal rule from cmdb_ci_nginx_web_server ➝ cmdb_ci_cmp_resource is feasible if there is a discoverable relationship (like a TCP connection, known config, etc.).
* However, traversal rules are typically used within patterns, not directly across tag-based and discovered nodes unless you’re extending a pattern-based service.

 Key Point: The tag-based mapping mechanism by default does not use traversal rules. But once you convert a service map into a hybrid or semi-dynamic map, you can manually establish and persist such relationships.

Q2: Is hybrid mapping (on-prem CIs + cloud tag-based CIs) supported?
Yes, ServiceNow does support hybrid service maps, but it requires some manual effort or pattern extension.

Recommended Solution Approach

Here’s how you can link your on-prem NGINX server with the cloud-tagged PostgreSQL in the Service Map

Option 1: Convert to Hybrid Service Map

1. Go to the Service Map of your tag-based service.

2. Click on "Edit Service Map".

3. Manually add the on-prem NGINX CI (from cmdb_ci_nginx_web_server) using:
* Search by name or IP
* Or through related connection (if auto-discovered via Discovery)

4. Create a manual connection or dependency:
* Use cmdb_rel_ci table to create a logical or application dependency between:
* NGINX server (cmdb_ci_nginx_web_server)
* Cloud PostgreSQL (cmdb_ci_cmp_resource)

5. Save the map. This becomes a hybrid service, combining:
* Tag-based components (auto-updated)
* Manually added or discovered on-prem CIs

Option 2: Extend the Tag-Based Pattern (Advanced)
If you want to make this link automated and persistent across refreshes:
1. Create or edit the Tag-Based Pattern used in your cloud application service.

2. Add a custom step or script to include external (on-prem) CIs based on:
* IP range
* Hostname
* Known configuration info (stored in CMDB)

3. Optionally, define a custom traversal rule:
* From cmdb_ci_nginx_web_server ➝ cmdb_ci_cmp_resource
* Based on known connection (port 5432, for example)

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.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025