Progress Database Uptime Test

In most production environments, it is essential to monitor the uptime of critical servers in the infrastructure. By tracking the uptime of each of the servers, administrators can determine what percentage of time a server 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 servers. By knowing that a specific server has been up for an unusually long time, an administrator may come to know that the scheduled reboot task is not working on a server.

The Progress Database Uptime test monitors the uptime of the Progress database servers.

Target of the test : A Progress Database server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the target Progress database server that is to be monitored

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed


The IP address of the Progress database server.


The port number on which the database server is listening. By default, this is NULL.

Database Name

Specify the name of the Progress database instance that is to be monitored.


In order to monitor a Progress database instance, a special database user account has to be created in every Progress database instance that requires monitoring. This special user needs to be granted a set of privileges. To know how to create the database user and grant the required privileges, refer to Pre-Requisites for monitoring the Progress database. Specify the name of such a user in this text box.


The password of the specified Username.

Confirm Password

Confirm the password by retyping it here.


By default, this flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the device in the manager’s time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running (i.e., the system being managed for agent-based monitoring, and the system on which the remote agent is running - for agentless monitoring).

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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 Onoption. To disable the capability, click on the Offoption.

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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates how long the database instance has been up and running.



Uptime since last measure

Indicates the duration for which the database instance has been up since the last measurement period.


If the value of this measure is lesser than the test frequency, it indicates that the instance was rebooted during the last measurement period.

Is rebooted?

Indicates whether the database instance was rebooted or not.


This measure reports the value Yes if the instance was rebooted in the last measurement period, and the value No if it was not rebooted. The numeric values that correspond to these measure values have been listed in the table below:

Measure Value Numeric Value






This test reports the Measure Values listed in the table above to indicate whether/not the instance was rebooted. In the graph of this measure however, the same will be represented using the numeric equivalents.