# ServiceNow notifications: Incoming incidents aren't mapped to the affected server in the CMDB

**URL:** <https://community.dynatrace.com/t/servicenow-notifications-incoming-incidents-arent-mapped-to-the-affected-server-in-the-cmdb/43470>\
**Category:** Troubleshooting\
**Tags:** cmdb, integrations, problem-notification, servicenow\
**Created:** [January 12, 2024, 8:10pm UTC](https://community.dynatrace.com/t/servicenow-notifications-incoming-incidents-arent-mapped-to-the-affected-server-in-the-cmdb/43470 "2024-01-12T20:10:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nandini\_balakri](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/nandini_balakri/32/13262_2.png) [@nandini\_balakri](https://community.dynatrace.com/u/nandini_balakri)\
**Post date:** [January 12, 2024, 8:10pm UTC](https://community.dynatrace.com/t/servicenow-notifications-incoming-incidents-arent-mapped-to-the-affected-server-in-the-cmdb/43470/1 "2024-01-12T20:10:00Z")

</div>

1. First check if you have [Dynatrace CMDB integration](https://docs.dynatrace.com/docs/shortlink/servicenow) activated in your environment (that is, check if the Service Graph Connector for Dynatrace is enabled).
2. If there’s no server with the same name, search for a server that has the Dynatrace entity ID (for example, `HOST-12121212`) in the `sys_object_source` table within ServiceNow.

For more information, refer to ServiceNow documentation on the [Service Graph Connector for Observability - Dynatrace](https://dt-url.net/ku22xke).