Uptime - Chrome OS Test

In most environments, it is essential to monitor the uptime of devices hosting applications in the infrastructure. By tracking the uptime of each of the device, administrators can determine what percentage of time a device has been up. Comparing this value with service level targets, administrators can determine the most trouble-prone areas of the target infrastructure. In some environments, administrators may schedule periodic reboots of their devices. By knowing that a specific device has been up for an unusually long time, an administrator may come to know that the scheduled reboot task is not working on a device.

This test included in the eG agent monitors the uptime of each device in the target Google Chromebooks Group.

Target of the Test : Google Chromebooks Group

Agent deploying the test: A remote agent

Output of the test: One set of results for each Chromebook in the target Google Chromebooks Group

Configurable parameters for the test
Parameters	Description
Test Period	How often should the test be executed. By default, this is set to 5 minutes.
Host	The host for which the test is to be configured.
Customer ID	To enable the eG agent to communicate to the devices managed by the target Google Chromebooks Group within the Google Workspace console and make REST API calls to collect metrics, the tests should be configured with the customer ID. To know how to obtain the customer ID mapped to the organization to which the target Google Chromebooks Group is mapped fron the Google Workspace console, refer to How does eG Enterprise Monitor Google Chromebooks Group? topic.
Private Keyfile Name	To connect to the Google Chromebooks Group, the eG agent requires a private key of a service account with Compute Viewer, Monitoring Viewer, and Cloud Asset Viewer roles in the target project. If a service account pre-exists in the project, then you can download the private key as a JSON file. Save this JSON file in the <eG_Install_Dir>/agent/lib folder and provide the name of that file against this parameter. However, if no such service account pre-exists, you will have to create one for monitoring the project. To know how to create a service account and download its private key, refer to How does eG Enterprise Monitor Google Chromebooks Group? topic.
Proxy Host and Proxy Port	In some environments, all communication with the Google Chromebooks Group be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the devices in the group via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the Proxy Host and Proxy Port parameters. By default, these parameters are set to none, indicating that the eG agent is not configured to communicate via a proxy, by default.
Proxy Username, Proxy Password and Confirm Password	If the proxy server requires authentication, then, specify a valid proxy user name and password in the Proxy Username and Proxy Password parameters, respectively. Then, confirm the password by retyping it in the Confirm Password text box.

Measures made by the test

Measurement

Description

Measurement Unit

Interpretation

Has the system been rebooted?

Indicates whether this device has been rebooted during the last measurement period or not.

The table below indicates the values that this measure can report and their corresponding numeric equivalents along with the signal quality range:

Measure value	Numeric Value
No	0
Yes	1

Note:

By default, this measure reports the above-mentioned Measure Values while indicating whether the device is rebooted or not. However, the graph of this measure will be represented using the corresponding numeric equivalents only.

Total uptime

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

This measure displays the number of years, months, days, hours, minutes and seconds since the last reboot. Administrators may wish to be alerted if a device has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions.