Agents Administration - Tests
 

Configuration of DockContainerStTest

This test monitors the containers available in the Docker server and reports the numerical statistics of the total containers, the containers in Running state, the containers that were added, the containers that were removed etc. In addition, this test reports the containers that are not running for a time duration above the specified limit and the containers that are utilizing disk space above the specified limit. By analyzing this, administrators can figure out the overall performance of the Docker server and identify bottlenecks if any.

The default parameters associated with this test are:

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

  • Specify the host for which the test is to be configured in the HOST text box.

  • Provide port number at which the specified HOST listens. The default is 2375.

  • By default, the USESUDO flag is set to Yes indicating either of the following:

    • The eG agent is using the sudo commands to collect the required metrics from the target docker server if monitored in an agent based manner or

    • The target docker server is monitored in an agentless manner and the eG agent install user is within a docker group.

    If the target docker server is monitored in an agentless manner and the user privileges are altered in the /etc/sudoers file, then, set this flag to No.

  • By default, the disk space utilized by each container may vary according to the size of the container. Sometimes, the containers may be over-utilizing the disk space which when left unnoticed may hamper the creation of new containers. To figure out such containers, you can specify a disk space limit beyond which the containers can be termed as large sized container. For example, if you wish to monitor the number of containers that are utilizing disk space above 50 MB, then specify 50 against the SIZE LIMIT IN MB text box.

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

  • By default, SHOW TOTAL CONTAINERS IN DD flag is set to No, indicating that this test will not report detailed diagnostics for the Total_Container measure. You can enable the detailed diagnosis capability of the Total_Container measure by setting this flag to Yes.

  • By default, SHOW STOPPED CONTAINERS IN DD flag is set to No, indicating that this test will not report detailed diagnostics for the Crashed_Container. You can enable the detailed diagnosis capability of the Crashed_Container measure by setting this flag to Yes.

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

  • To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability

    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.