FSLogix Azure Storage Provider - OS Test
FSLogix is widely used for managing user profiles in environments where users might frequently log in to different virtual desktop instances. The Azure Storage Provider integrates with FSLogix to store and manage these profiles more efficiently. It eliminates the need for persistent virtual desktop infrastructure (VDI) and helps ensure that users have a consistent and seamless experience.
For performance to be optimal it is imperative that all components within the system are working at high efficiency. To manage system performance and fix any potential issues, administrators needs to keep track of key performance indicators so that they are the first ones to know if there is any performance bottleneck. FSLogix Azure Storage Provider - OS Test can help in this regard.
For each user connecting to a FSLogix Azure Storage Provider, this test reports whether the storage provider experiences a sudden surge in data read/write operation. In addition, the test points administrators to users whose experience suffer due to inadequate disk space.
Target of the test : A virtual desktop on the cloud
Agent deploying the test : A Remote agent
Outputs of the test : One set of results for each combination of virtual machine:user on the target virtual server to be monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
The default port is NULL. |
Inside View Using |
To obtain the 'inside view' of performance of the cloud-hosted virtual desktops - i.e., to measure the internal performance of the virtual desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent. |
Report By User |
This flag is set to Yes by default. The value of this flag cannot be changed. This implies that the virtual machines in VDI environments will always be identified using the login name of the user. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename. |
Report Powered OS |
This flag is relevant only for those tests that are mapped to the Inside View of Desktops layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those virtual desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_virtualdesktopname. On the other hand, if this flag is set to No, then this test will not report measures for those virtual desktops to which no users are logged in currently. |
Is Cloud VMs |
Since this test runs for every virtual desktops component which is a cloud-hosted desktop group, this flag is set to Yes by default. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Data read rate |
Indicates the rate at which data was read by this user. |
KB/sec |
|
Data write rate |
Indicates the rate at which data was written on the storage provider by this user. |
KB/sec |
|
Data read |
Indicates the amount of data read by this user. |
KB |
This measure gives an idea of how the storage is being used.
|
Data write |
Indicates the amount of data written by this user on the storage provider. |
KB |
|
Read transactions |
Indicates the number of read transactions performed by this user. |
Number |
This number can be monitored over multiple measurements and if there is a constant downward trend, investigation may be required.
|
Write transactions |
Indicates the number of write transactions performed by this user. |
Number |
|
Read transaction rate |
Indicates the rate at which read transactions were performed by this user. |
Transaction/sec |
|
Write transaction rate |
Indicates the rate at which write transactions were performed by this user. |
Transaction/sec |
|
Writes after optimization |
Indicates the number of times data has been written after optimization. |
Number |
|
Writes before optimization |
Indicates the number of times data has been written before optimization. |
Number |
|