Operational Technology asset created by Discovery of IT CI

Go to solution
Kiril Petrov
Kilo Contributor

‎08-11-2022 02:36 AM

Hi all, I have a situation where while discovering Linux servers, OT assets are created in cmdb_ot_entity table. I am trying to understand why it is happening. Here is what I did to recreate the case. 

I got a Ubuntu VM , created a new non root user and discovered the machine in my PDI. 

Used command sudo usermod -aG "username" for the rights. Credentials got validated and there is no issue message for users permissions in the instance after discovering the vm. I read that Discovery for OT plugin when activated checks for every discovered CI if there is a similar one in cmdb_ot_entity table by event. If there is not then a new record is credated.

Why  do we have OT Asset created on server discovery?

find_real_file.png

Can I suppress this behavior somehow ?

Any explanation will be useful. 

Thanks in advance !

 

Preview file
12 KB
Preview file
12 KB
Preview file
11 KB
0 Helpfuls
  • 1,017 Views
1 ACCEPTED SOLUTION

Go to solution
Fabian Kunzke
Kilo Sage
Kilo Sage

‎08-12-2022 01:04 AM

Hello,

when activating the OT discovery, this is the expected behaviour. OT assets are - as you have stated - automatically created after the discovery was run. This is triggered by the "discovery.device.complete" system event.

If you want to disable that logic - or customise it - you will have to find the matching event handler/script action in your instance. You will find all the ones reacting to the "discovery.device.complete" event here: INSTANCE_URL/nav_to.do?uri=%2Fsysevent_script_action_list.do%3Fsysparm_query%3Devent_nameSTARTSWITHdiscovery.device.complete%26sysparm_first_row%3D1%26sysparm_view%3D%26sysparm_choice_query_raw%3D%26sysparm_list_header_search%3Dtrue

Hope this helps,
Regards
Fabian

View solution in original post

5 REPLIES 5

Go to solution
Fabian Kunzke
Kilo Sage
Kilo Sage
In response to Kiril Petrov

‎08-16-2022 05:14 AM

Hey,

only from the official docs (which is not very helpful for any details):

2. When it completes discovery of a configuration item (CI), it internally triggers a (discovery.device.complete) event. This logic checks if an OT entity (cmdb_ot_entity) record exists for it in the Configuration Management Database (CMDB).

    • If one exists, and any related attributes have changed for the discovered item, it updates the OT Entities that are related to that CI.
    • If one does not exist, it creates one for it.

Link for the docs: Here.

Regards,
Fabian

0 Helpfuls