---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# View the Dependency map for CMDB alerts

# View the Dependency map for CMDB alerts {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Dependency map illustrates how and why alerts are grouped, simplifying troubleshooting and issue management. It reveals connections between CIs within a CMDB alert group, enhancing visibility into their relationships. Additionally, if a CI is not part of the group but connects to other alert CIs, it remains visible on the map, aiding alert
resolution and proactive management.

## Before you begin

Role required: evt_mgmt_user, evt_mgmt_operator

## About this task

To create CMDB-based alert grouping, you can also create a grouping automation in Service Operations Workspace. For more information, see [Create Group automation](https://www.servicenow.com/docs/dzmFiicpe800NSz3XP_fGw "Grouping automation helps you manage alerts more effectively by collecting similar alerts together. This makes it easier to see patterns, quickly identify issues, and respond efficiently. By organizing alerts in this way, you can reduce alert noise, identify root causes, and assign them to the appropriate teams.").

## Procedure

1. Navigate to AllEvent ManagementAll Alerts.
2. Search for the CMDB group.
3. Open a CMDB group alert.
4. Scroll down and select the Activities tab.  
   You may see a message similar to the following:
   Alert2405199 and Alert2405219 were grouped together because of CI relationships. Open Dependency Map for CMDB Group Alerts. Open Dependency Map for CMDB Group Alerts.  
5. Select the link to see the dependency view of the CMDB alerts.  
{#dependency-view-map__steps_ijj_m11_dzb}

*[\>]: and then