
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2018 07:31 PM
Hi All,
Sorry if the question is obvious, I'm still learning about service now - event management.
On our instance, we have 2 CIs with exact same name (one is capital, one is lowercase) but one is Retired. I'm trying to bind event to the active CI not the Retired CI but couldn't get it to work. I tried the below:
- Created event rule with Additional Information - ${u_active} with value is always true.
- Binding section set to Override default binding, binding type: CI field matching, CI type: Configuration Item.
I thought when binding SN will find 2 CIs and then use the u_active field to pick the one with value = true.
but SN can only find one CI as per below log:
Binding alert CI process flow:
Node will be resolved to CI id: 6d1323d44fa36600f9... : found by node name
Event CI type is cmdbi_ci
Checking for matching with processes that are running on the node
No matching CI found
No related CI found for binding, alert CI will be bound to node (id): 6d1323d44fa36600f9...
Bind to 6d1323d44fa36600f9...
I'm not sure if I'm on the right direction. If not could someone please point me to where I need to look into?
Thank you in advance,
Regards,
Terry
Solved! Go to Solution.
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2018 10:54 AM
This can be done a couple ways (more actually).
First, what kind of binding are you applying? CI Identification or CI Field Matching. If CI Identification, then consider adding an identification inclusion rule that does not lookup "Retired" CIs.
If doing Field Matching, then add a manual attribute with the same name as the CI attribute you're setting as retired (operational_status or installed_status I assume), and set this to the value you want to match (operational, installed, etc)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2018 03:41 PM
Thanks Nick, the CI is under Hardware.
I was trying to use "Configuration Item" as the "CI Identification" Class which has no "Identification" rule set.
I switched the Class to Hardware and it worked.
I'll look into create identification rule for "Configuration Item" class so I can use it with that class.
Thank you so much for your help 🙂