| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
Indicates the current status of the monitored gateway appliance. |
  |
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the gateway appliance. In the graph of the measure however, the same is indicated using the numeric equivalents only.
If this measure reveals that the gateway appliance is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for the abnormal status.
|
| Session_count |
Indicates the current number of sessions on the gateway appliance. |
Number |
The value of this measure includes all protocol sessions. |
| Auth_count |
Indicates the number of authenticated sessions. |
Number |
|
| High_mark |
Indicates the high water mark of sessions count on the gateway appliance. |
Number |
By tracking the variations to this measure over time, you can figure out the maximum number of sessions the appliance can handle. |
| Bro_status |
Indicates the current status of the VMware Horizon Connection server connected to the target Access Gatway. |
  |
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the connection broker. In the graph of the measure however, the same is indicated using the numeric equivalents only. If this measure reveals that the broker is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status. |
| Success_logins |
Indicates the number of logins that were successful. |
Number |
Ideally, the value of this measure should be high. |
| Failed_logins |
Indicates the number of logins that failed. |
Number |
Ideally, the value of this measure should be 0. |
| Back_status |
Indicates the current status of the backend. |
  |
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the backend. In the graph of the measure however, the same is indicated using the numeric equivalents only. If this measure reveals that the backend is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status. |
| Edge_service_status |
Indicates the current status of the Edge service. |
  |
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the backend. In the graph of the measure however, the same is indicated using the numeric equivalents only.If this measure reveals that the Edge service is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status. |
| Pcoip_stat |
Indicates the current status of the PCoIP protocol. |
|
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the PCoIP protocol. In the graph of the measure however, the same is indicated using the numeric equivalents only.If this measure reveals that PCoIP protocol is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status. |
| Pcoip_sess |
Indicates the current number of PCoIP sessions. |
Number |
|
| Max_pco_sess |
Indicates the high watermark of PCoIP sessions. |
Number |
|
| Balst_stat |
Indicates the current status of the Blast protocol. |
|
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the Blast protocol. In the graph of the measure however, the same is indicated using the numeric equivalents only.If this measure reveals that the Blast protocol is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status.
|
| Blast_sess |
Indicates the current number of Blast sessions |
Number |
|
| Max_blast_sess |
Indicates the high watermark of Blast sessions. |
Number |
 . |
| RDP_status |
Indicates the current status of the RDP protocol. |
  |
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the RDP protocol. In the graph of the measure however, the same is indicated using the numeric equivalents only. If this measure reveals that the RDP protocol is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status.
|
| RDP_session |
Indicates the current number of Blast sessions. |
Number |
|
| Max_rdp_sess |
Indicates the high watermark of RDP sessions. |
Number |
|
| Utserver_status |
Indicates the current status of the Utserver protocol. |
  |
The values that this measure can report and their corresponding numeric values are detailed in the table below:
| Measure Value |
Numeric Value |
| Running |
1 |
| Not Running |
2 |
| Partial Running |
3 |
| Disabled |
4 |
| Idle |
5 |
| Not Reachable |
6 |
Note:
By default, this measure reports the Measure Values listed in the table above to indicate the current status of the Utserver protocol. In the graph of the measure however, the same is indicated using the numeric equivalents only.
If this measure reveals that the Utserver protocol is in an abnormal state presently, then, you can use the detailed diagnosis of this measure to determine the reason for this abnormal status. |
| Utserver_session |
Indicates the current number of Utserver sessions. |
Number |
|
| Max_uts_sess |
Indicates the high watermark of Utserver sessions. |
Number |
|