Default Parameters for CorOSPodStatusTest

This test reports the total number of pods launched using the target CRIO Container Engine. Using this test, administrators can figure out the pods that are currently running and those that are stopped. Drilling down to the detailed diagnostics of this test helps administrators figure out the name of those containers that remain inaccessible to the users due to pods being in stopped state.

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

• 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.

• Specify the number of days beyond which a container should be classified as a long running container in the LONG RUN CONTAINER DAYS text box. By default, this is set to 6 days.

• By default, SHOW TOTAL CONTAINERS IN DD flag is set to No indicating that by default, the test does not generate detailed measures for the Total containers measure, so as to conserve storage space. However, if you want the test to generate and store detailed measures for the Total containers measure, set this flag to Yes.

• By default, SHOW STOPPED CONTAINERS IN DD flag is set to No indicating that by default, the test does not generate detailed measures for the Exited containers measure, so as to conserve storage space. However, if you want the test to generate and store detailed measures for the Exited containers measure, set this flag to Yes.

• For this test to report the numerical statistics of the containers that were not started/running, set a valid value against TIME LIMIT IN WEEKS parameter. For example, if you wish to report the containers that were not started for more than 5 weeks, then set 5 against this text box. By default, this parameter is set to 4 indicating that this test will report the containers that were not started for more than 4 weeks.

• 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.