How Does eG Enterprise Monitor CRI-O?

eG Enterprise monitors the target CRIO Container engine using a container agent deployed as a Daemonset. This container agent will start the discovery process in the target environment. By default, eG Enterprise is capable of automatically discovering and managing the target CRI-O Container Engine as well as the applications hosted on the target Container Engine once the container agent is deployed.

To ensure seamless discovery and management of the target CRI-O Container Engine, you need to check the following:

• By default, the Agent discovery and Containerized applications discovery options in the AGENT DISCOVERY - ENABLE/DISABLE page that appears when you navigate through the Admin -> Discovery -> Agent Discovery -> Actions -> Enable/Disable menu sequence is enabled. Ensure that this setting remains unchanged in the target environment.

• By default, the target CRI-O Container Engine will be automatically discovered by eG Enterprise. To this effect, the CRIO Container Engine component type is automatically listed in the Component types chosen for discovery section available in the COMMON SETTINGS - GENERAL page that appears when you navigate through the Admin -> Discovery -> Settings -> General menu sequence. Ensure that the CRIO Container Engine component type is not removed from this list.

• By default, the target CRI-O Container Engine will be automatically managed once it is auto discovered by eG Enterprise. To this effect, the CRIO Container Engine component type is automatically listed in the Component types to be automatically managed section available in the COMMON SETTINGS - AUTO MANAGE page that appears when you navigate through the Admin -> Discovery -> Settings -> Auto manage menu sequence. Ensure that the CRIO Container Engine is not removed from this list.