---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Predefined traversal rules

# Predefined traversal rules for application services {#ariaid-title1}

* Release version: Yokohama
* 
* Updated November 4, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Service Mapping uses traversal rules to bring in related configuration items and expand the application service map. Several predefined rules are provided by default to help find and correctly map these
relationships.

## About traversal rules {#default-traversal-rules__understanding-traversal-rules}

Predefined traversal rules in Service Mapping are key to identifying the relationships between configuration items (CIs) and building accurate application service maps. To maintain integrity and avoid issues, such as incomplete maps or service
disruptions, these rules are fixed. You can't change, customize, or remove them. To create custom traversal rules to meet your organization's needs, see [Traversal Rules for Application Services form completion](https://servicenow-prod.fluidtopics.net/e6xIhRqkraMlp_mvL5u1vg "To edit an existing CI relationship or add a new CI relationship during the tag-based discovery process, complete the Traversal Rules for Application Services form.").

## Predefined traversal rules {#default-traversal-rules__predefined-traversal-rules-table}

{#default-traversal-rules__predefined-traversal-rules-table__entry__5}

| Parent Type | Relationship | Child Type | Priority Level | Is Reverse |
|-|-|-|-|-|
| cmdb_ci | Runs on::Runs | Hardware \[cmdb_ci_hardware\] | 100 | false |
| cmdb_ci | Hosted on::Hosts | Logical Datacenter \[cmdb_ci_logical_datacenter\] | 200 | false |
| cmdb_ci_lb_service | Hosted on::Hosts | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | 300 | false |
| cmdb_ci_cluster_node | Hosted on::Hosts | Server \[cmdb_ci_server\] | 400 | true |
| cmdb_ci | Contains::Contained by | Tracked Configuration File \[cmdb_ci_config_file_tracked\] | 500 | false |
| cmdb_ci_cluster_node | Cluster of::Cluster | Cluster \[cmdb_ci_cluster\] | 600 | false |
| cmdb_ci_cluster_node | Cluster of::Cluster | Cluster \[cmdb_ci_cluster\] | 700 | true |
| cmdb_ci_cluster_node | Hosted on::Hosts | Server \[cmdb_ci_server\] | 800 | false |
[ ]

For example, the first row of the table illustrates a traversal rule that identifies and adds the hardware (cmdb_ci_hardware) supporting a given software application (cmdb_ci). When Is Reverse is set to
false, the discovery process starts with the application and identifies the hardware it runs on-traversing from the parent CI to the child CI. The relationships are then added to the application service map.

To learn more about traversal rule components and related terminology, see [Traversal rules in Service Mapping](https://servicenow-prod.fluidtopics.net/~ROXNytS7quE~_vWiD3rew "Traversal rules identify and map relationships between configuration items to create comprehensive application service maps. They connect relevant configuration items based on predefined relationships, promoting accurate service mapping and visualization.").