The CreatorCon Call for Content is officially open! Get started here.

IRE Issue

Juhi Tembhare
Tera Contributor

Hi Everyone, 
I am trying to create an Identification rule on cmdb_ci_service_auto table; its label has recently been updated to service instance after the Yokohama patch updates. The identification rule was created successfully, but there is a RED mark on it, and another error occurred.

"Rule entry under cmdb_ci_service identifier using non-existent table is ignored during identification!"

I am using the Robust transform map for this development and trying to fetch the data by import set number. In the staging table records, there is a comment,

"IRE payload is empty, there are no records to insert or update.

Even when we already have 20+ records in the Payload. I assume that image (2).pngthis empty payload comment might be related to the IRE issue. 

Can someone please guide me on this? 

 

 

1 ACCEPTED SOLUTION

Laveena-Agarwal
Kilo Sage

Hi @Juhi Tembhare 

 

I was able to reproduce the issue in my Personal Developer Instance and apply a fix.

Since you mentioned that the Identifier is written on the cmdb_ci_service_auto table, the same value should also be reflected in the Identifier entry.

Solution

Please update the Identifier field in your configuration to cmdb_ci_service_auto. Once done, the error should no longer appear.

I’d also recommend running an Identification Simulation afterwards—this will allow you to validate and test your identifiers effectively.

 

View solution in original post

3 REPLIES 3

Laveena-Agarwal
Kilo Sage

Hi @Juhi Tembhare 

 

The issue appears to be with a Related Entry linked to this identifier. A table seems to be missing, which is causing the error.

I found some articles describing similar problems—please review them and let me know if they help resolve it.

"Rule entry under cmdb_ci_hardware identifier using non-existent table is ignored during identificat...

x_nbt_netbrain_nb_device table missing causes Error: Rule entry under cmdb_ci_hardware identifier us...

Juhi Tembhare
Tera Contributor

Hello @Laveena-Agarwal 
We don't have activated discovery on our instance, and the suggested article plugins are already up to date. Can you provide any other suggestions?

Thank you.

Laveena-Agarwal
Kilo Sage

Hi @Juhi Tembhare 

 

I was able to reproduce the issue in my Personal Developer Instance and apply a fix.

Since you mentioned that the Identifier is written on the cmdb_ci_service_auto table, the same value should also be reflected in the Identifier entry.

Solution

Please update the Identifier field in your configuration to cmdb_ci_service_auto. Once done, the error should no longer appear.

I’d also recommend running an Identification Simulation afterwards—this will allow you to validate and test your identifiers effectively.