Disk Activity - Chrome OS Test

This test auto-discovers the devices in the target Google Chromebooks Group and reveals how much data was read from and written to the disks of each device. In the process, this test also reports the latency while performing the read and write operations on the disks of each device. This revelation sheds light on the IO processing delays, if any, and enables administrators to take necessary actions immediately.

Target of the Test : Google Chromebooks Group

Agent deploying the test: A remote agent

Output of the test: One set of results for each device 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
Data read	Indicates the amount of data read from the disks on this device during the last measurement period.	MB	Ideally, the value of this measure should be high. A steady dip in this measure value could indicate a potential reading bottleneck.
Data write	Indicates the amount of data written to the disks on this device during the last measurement period.	MB	Ideally, the value of this measure should be high. A steady dip in this measure value could indicate a potential writing bottleneck.
Disk read latency	Indicates the average time taken by the disks on this device to process read requests during the last measurement period.	Seconds	Ideally, the values of these measures should be very low. By comparing the values of these measures, administrators can figure out where the slowness is maximum - when processing read requests? or write requests?
Disk write latency	Indicates the average time taken by the disks on this device to process write requests during the last measurement period.	Seconds
Disk IO duration	Indicates the time taken to perform the I/O operations on the disks of this device during the last measurement period.	Seconds	A consistent drop in this value is a cause for concern, as it indicates a IO processing slowdown.