Default Parameters for CorOSConUptmeTest

In environments where CRIO container engine is used extensively to launch containers and pods, it is essential to monitor the uptime of critical containers launched by the target CRIO engine. By tracking the uptime of each of the containers, administrators can determine what percentage of time a container has been up. In some environments, administrators may schedule periodic reboots of their containers. By knowing that a specific container has been up for an unusually long time, an administrator can easily identify that the scheduled reboot task is not working on a container. The CorOSConUptmeTest helps administrators track such irregularities with ease!

Use this test to promptly detect unscheduled reboots and unexpected breaks in the availability of each container on the target CRIO container engine.

This page depicts the default parameters that need to be configured for the CorOSConUptmeTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• By default, USE SUDO flag is set to No. This indicates that, by default, this test will report the metrics by executing the crictl command. However, in some highly secure environments, the eG agent installed user may not have the permissions to execute this command directly. In such cases, do the following:

  • Edit the SUDOERS file on the target host and append an entry of the following format to it:

    <eG_agent_install_user> ALL=(ALL) NOPASSWD:<Command>

    For instance, if the eG agent install user is eguser, then the entries in the sudoers file should be:

    eguser ALL=(ALL) NOPASSWD: crictl

  • Finally, save the file.

  • Then, when configuring the test using the eG admin interface, set this parameter to Yes. This will enable the eG agent to execute the sudo crictl command and retrieve the relevant metrics for this test.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.