---
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 the impact tree

# View the impact tree {#ariaid-title1}

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

The impact tree shows the relationships between CIs and the relative percentage
impact for each child CI. This information is available for both discovered services and
application services.

## Before you begin

Role required: evt_mgmt_admin, evt_mgmt_operator, or evt_mgmt_user

## About this task

The impact tree shows the result of impact rules on CI parent and child
relationships. The tree represents a service map with CIs from the Service
Configuration Item Associations \[svc_ci_assoc\] table. When related CIs are connected
but not part of the service map, the impact for the related CIs can also appear in
the impact tree.

The numbers or percentages on a parent CI summarize overall
severity based on alerts from child CIs. The parent severity is based on impact rule
computations.

You can also learn about the impact tree from the following
video tutorial.  
Figure 1. Impact Tree

## Procedure

1. Open the service map for the service from the Application service list.  
   1. Navigate to Event ManagementServicesApplication Services.
   2. Click View service next to the service.
   {#t_EMViewImpactTree__ol_bkk_q5y_cmb}
2. On the service map, click a CI that has a severity color.
3. Click the Impact tab.
4. From the Impact Tree tab in the side pane, expand the parent CI and click the CI that generated alerts.
5. Use the severity color to locate CIs that contain alerts:
   * Critical (red): Immediate action is required. The resource is either not functional or critical problems are imminent.
   * Major (orange): Major functionality is severely impaired or performance has degraded.
   * Minor (yellow): Partial, non-critical loss of functionality or performance degradation occurred.
   * Warning (blue): Attention is required, even though the resource is still functional.
   * OK (green): An alert is created. The resource is still functional.
6. Do one or more of the following.

   | Option | Description |
   | Adjust impact rules | 1. Click the Impact tab. 2. Review and adjust the impact rules as necessary. {#t_EMViewImpactTree__ol_zhx_z1m_35} |
   | Remediate an alert | 1. Click the Alerts. 2. Right-click the alert and select Run remediation. {#t_EMViewImpactTree__ol_ybj_bbm_35} |
   |-|-|

   {#t_EMViewImpactTree__choicetable_rdg_w1m_35}  
   Network paths appearing in the impact tree can use a large amount of
   resources, which degrades system performance. To disable network paths from
   appearing in the impact tree, navigate to System PropertiesAll Properties and set the
   evt_mgmt.network_path_excluded property to
   true.

   To view impact tree using Service Operations Workspace, see [View impact tree using Service Operations Workspace](https://servicenow-prod.fluidtopics.net/MJu3RDlQajXN6F7~7REvvg "Visualize relationships between Configuration Items (CIs) and alerts with real-time updates and detailed impact paths. Enhance troubleshooting and proactive management by quickly identifying root causes and dependencies for both discovered services and application services.").

*[\>]: and then