---
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


---

# View impact of child service on parent service

# View impact of child service on parent service {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

In the map view of an application service, the severity of a child service is
propagated to its parent service.

## Before you begin

Role required:

* for application services, evt_mgmt_admin
* for discovered services, service_mapping_admin
{#cross-business-service-impact__ul_ptb_n32_qbb}

## About this task

In the map view of a discovered application service, you can see that the severity of a child service is propagated to the parent service.

An application service is affected by the severity of alerts that are directly
associated with it and alerts on the CIs that are in the service. If the severity of
a child service is higher than that of its parent service, on the map view the
parent service shows the severity of the child service. In the map view, the
Impact Tree list shows the CIs. The color of the CIs
indicates the alert severity. The child service is also affected by application
services that are under it.  
Figure 1. Example where the parent service shows the severity of the child service  
If a loop is created, for example, by connecting a parent service to a sub-service, this relationship can be viewed in the map view. The impact of this loop is not calculated and the Impact Tree does not display this relationship. For example, assume that there are three CIs, A, B, and C, where C is a sub-service to B and B is a sub-service to A. The relationship of the A connected service to C is displayed in the map view. However, this relationship is not shown in the Impact Tree.  
Note:  
A message appears in the system error log in the following format, where the sys_id of the service and the node changes accordingly: Found loop in ServiceId:\[sysId\], and node:\[sysId\]. Removing this relation to avoid impact loops

For example, Found loop in ServiceId:409d4fd59f030200fe2ab0aec32e705c, and node:df5cf6159f030200fe2ab0aec32e70a2. Removing this relation to avoid impact loops

Click a service or
CI to see the alerts that are associated with it. For example, if you click the
high-level application service, the alerts that are associated with it are displayed
in the alert area under the Map View. The alerts listed are those of the selected
service. Alerts of child-services are listed when those services are selected.  
Figure 2. Example of alerts listed under the Map View

## Procedure

Open an application service map:  
1. Navigate to Event ManagementServicesApplication Services.
2. Select View Service next to the service.
3. On the right-hand panel, select Impact tree.
4. On the lower panel, select Impact.
{#cross-business-service-impact__ol_abh_2yy_cmb}

## Result

In the service map, you can visually verify that the service health of the sub-service is rolled-up to the parent service. At the bottom of each icon of an impacted CI is a colored bar that represents the severity of the alert. This color bar also displays in the bottom bar of its parent service. For manual cluster configuration, you can modify the Application Impact and Application Cluster Member.
**Related tasks**   

* [Transfer a map segment into another application service](https://servicenow-prod.fluidtopics.net/8_AlRz5snn~YqOp5~kuhTw "You can remove a branch of a service and place it into another application service, either new or existing. Transfer map segments to split large services or when you want to organize services differently from the initial mapping result.")
* [Configure a manual cluster](https://servicenow-prod.fluidtopics.net/lAb8p8fU3sXXEQcyLK4Qtw "Provide redundancy capabilities of an entire cluster in case of failure of one or more CIs in that cluster. By viewing the relative impact of a cluster member on the cluster information, you can better understand the source of alerts and take remediation steps.")
* [Adjust alert impact while triaging an alert](https://servicenow-prod.fluidtopics.net/GSEn_pzREoB2CRWbipqFtA "As an Event Management operator, you might need to modify the impact that an alert has on an application service and on the CIs in a service. Do this when you think that the impact does not accurately represent what you see in your network environment so other operators and administrators see the correct impact information.")
* [View an alert impact on CIs in a service map](https://servicenow-prod.fluidtopics.net/vLdIapkutKYMK2xEFQLrrg "You can view service maps to see active alerts for CIs and the relationship between CIs. By viewing this information, you can better understand the source of alerts and take remediation steps. The service map is available for all application services.")

*[\>]: and then