
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2022 09:16 AM
Hi,
In alerts list (em_alert) could see some of the alerts are having empty CI means they are not binded to any CI
An initial review of this, shows that most of these are related of alerts coming from one source alerts, which are not related to any Configuration Item.
This causes ServiceNow to capture the 'node' field of the alert and consider it an 'object' towards the licenses count. and have also gone through em_unique_nodes table to check the license usage and could see the type as unknown
Please suggest a fix to resolve this or root cause of this issue, could you please help why those particular alerts are having empty CI's
Solved! Go to Solution.
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2022 12:17 AM
Hi Dhana, that's right since the CIs do not exist in your instance they won't be binded to the alert.
- When an event arrives, Event Management checks the node or CI identifiers.
- If no node exists, the generated alert can bind to the CI using the alert Type, Additional information, or Configuration item identifier fields.
- If the event has a node value, search for a valid host.
- If the event has a host and a CI type, try to bind to a device CI.
- If the event has a host, try to bind to the application CI.

Ideally, if you can't find the right CI, the last resort is to bind it to the application service CI the event is associated with.
Read through this further and see if this helps - https://docs.servicenow.com/bundle/quebec-it-operations-management/page/product/event-management/ref...
Thanks
-Harneet Sital
Request you to please mark my answer as HELPFUL or CORRECT based on the impact
Find all my ServiceNow articles here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2024 06:20 AM
Reason for failure could be 1. source node is not a hardware CI in which case try using other types of binding options such as CI identifier or CI field matching
2. If there are duplicates binding will fail
Event record processing notes shud tell the cause for failure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 03:13 AM
Hi Varan,
I tried using the CI identifier or CI field matching. However it is asking me to select a CMDB table name, however those node names are not part of any CMDB table, how can I create the event rule for CI binding ? Please suggest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-01-2024 09:52 PM
Few node names are not part of CMDB CI tables, how can we create an event rule to bind the CI, if the node names are not part of CMDB tables ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2023 01:35 PM
Any solution for this case? also I use the "new relic" app...
Fernando Urrutia | LinkedIn
Consultor Certificado en ServiceNow desde 2018
Especialista en ITSM, Mejora Continua, Soporte y Administración
Solex – Soluciones Expertas S.A.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-23-2023 08:30 PM - edited 12-23-2023 08:32 PM
Decision tree while reviewing Unresolved monitored objects
How to which event rule is applied on alert ?
A fix script is created that can help analyze event rules PF link