Docker Containers - Uptime Test

In environments where Docker server is used extensively, it is essential to monitor the uptime of critical containers within the Docker server. By tracking the uptime of each of the containers, administrators can determine what percentage of time a container has been up. Comparing this value with service level targets, administrators can determine the most trouble-prone areas of the infrastructure.

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 may come to know that the scheduled reboot task is not working on a container.

The Docker Containers - Uptime test included in the eG agent monitors the uptime of critical containers in the target Docker server.

Target of the test : A Docker server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each container available in the Docker server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which this test is to be configured.

Port

The port number at which the specified host listens. The default is 2375.

UseSUDO

By default, this flag is set to Yes. You are advised not to change the default setting of this flag.

Docker User and Docker Password

Specify the credentials of the user who is authorized to execute the docker commands on the target server

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.

Detailed Diagnosis

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 enabled/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.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Has the container been restarted?

Indicates whether/not this container was rebooted.

 

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value Numeric Value
No 0
Yes 1

Note:

This measure reports the Measure Values listed in the table above while indicating whether /not this container was rebooted. However, in the graph of this measure, the measure is indicated using only the Numeric Values listed in the above table.

Uptime of the container during the last measure period

Indicates the time duration for which this container has been up since the last time this test ran

Secs

If this container has not been rebooted during the last measurement period and the agent has been running continuously, this value will be equal to the measurement period. If this container was rebooted during the last measurement period, this value will be less than the measurement period of the test. The accuracy of this metric is dependent on the measurement period - the smaller the measurement period, greater the accuracy.

Total uptime of the container

Indicates the total time that this container has been up since its last reboot.

Mins

Administrators may wish to be alerted if a container has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions.