AVD Errors Test

To ensure the error-free functioning of the AVD service, administrators should swoop down on errors as soon as they occur, quickly determine what type of error it is, and figure out why it occurred, so that they can mitigate the errors before service delivery is impacted. This is where the AVD Errors test helps!

This test scans each host pool's diagnostic logs for errors of different types - namely, connection errors, service errors, management errors, and even unknown errors. Every time an error is captured and logged into the diagnostic logs, the test alerts administrators to that error, and points them to the exact host pool where that error occurred. This way, the test turns the administrator's attention to problems with the AVD service. Detailed diagnostics reported by the test reveal what the error is, when it occurred, which user caused it, and what is its source. With the help of these diagnostics, administrators can quickly and effectively troubleshoot the error.

Note:

Typically, to consolidate log entries, correlate log data, and perform complex analysis, a host pool's logs are often sent to one/more Log Analytics Workspaces. This test reports valid metrics by reading data from these Log Analytics Workspaces only. If the host pool's logs are not sent to any Log Analytics Workspace, then this test will only report the value 0 for most of its measures. To avoid this, before configuring this test, make sure that the host pool's logs are configured to be sent to at least one Log Analytics Workspace. Follow the steps discussed in Configuring the Host Pool Logs to be Sent to a Log Analytics Workspace to achieve this.

Target of the Test: A Microsoft AVD Broker

Agent deploying the test: A remote agent

Output of the test: One set of results for each AVD host pool managed by the target AVD broker, in each resource group of the configured subscription

Configurable parameters for the test
Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Subscription ID	Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored. To know the ID that maps to the target subscription, do the following: Login to the Microsoft Azure Portal. When the portal opens, click on the Subscriptions option (as indicated by Figure 1). Figure 1 : Clicking on the Subscriptions option Figure 2 that appears next will list all the subscriptions that have been configured for the target Azure AD tenant. Locate the subscription that is being monitored in the list, and check the value displayed for that subscription in the Subscription ID column. Figure 2 : Determining the Subscription ID Copy the Subscription ID in Figure 2 to the text box corresponding to the SUBSCRIPTION ID parameter in the test configuration page.
Tenant ID	Specify the Directory ID of the Azure AD tenant to which the target subscription belongs. To know how to determine the Directory ID, refer to Configuring the eG Agent to Monitor a Microsoft AVD Broker Using Azure ARM REST API
Client ID and Client Password	To collect the required metrics, the eG agent requires an Access token in the form of an Application ID and the client secret value. If a Microsoft Azure Subscription component or a Microsoft Azure Active Directory component is already being monitored, then an Application would have already been created for monitoring purposes. The Application ID and Client Secret of such an application can be specified here. However, if no such application exists, then you will have to create one for monitoring the AVD broker. To know how to create such an application and determine its Application ID and Client Secret, refer to Configuring the eG Agent to Monitor a Microsoft AVD Broker Using Azure ARM REST API. Specify the Application ID of the created Application in the Client ID text box and the client secret value in the Client Password text box.
Proxy Host	In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud 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.
Log Analytics Workspace Name	Typically, to consolidate log entries, correlate log data, and perform complex analysis, a host pool's logs are often sent to one/more Log Analytics Workspaces. By default, the Log Analytics Workspace Name parameter is set to All. This indicates that the test reads log data from all Log Analytics Workspaces configured for the target subscription, by default. However, if you want the test to use only those Log Analytics Workspaces to which a host pool's logs are sent, then provide the names of these workspaces here as a comma-separated list. To determine the names of the workspaces, do the following: Login to the Microsoft Azure Portal, and click on Host Pools to view the configured host pools. Select any of the host pools displayed therein by clicking on it. Next, keep scrolling down the left panel of the page that then appears, until the Diagnostic Settings option (under Monitoring) become visible. Click on Diagnostic Settings to proceed. The diagnostic settings that pre-exist (if any) for the chosen host pool will then appear. If any of the existing diagnostic settings have already been configured with Log Analytics Workspaces, then the Log Analytics workspace column of that list will display these workspace names. You can configure the LOG ANALYTICS WORKSPACE NAME parameter of this test with any of these workspace names. If required, you can even configure this parameter with two/more workspaces displayed here, as a comma-separated list However, If the Log Analytics workspace column is blank for all the existing diagnostic settings, it is a clear indication that the host pool's logs are yet to be configured to be sent to any Log Analytics Workspace. In this case therefore, you should create a new diagnostic setting for the target host pool where a Log Analytics Workspace is configured as the destination for the logs. To achieve this, follow the procedure detailed in Configuring the Host Pool Logs to be Sent to a Log Analytics Workspace.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, 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 On option. To disable the capability, click on the Off option. 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.

Measures made by the test:
Measurement	Description	Measurement Unit	Interpretation
Connection errors	Indicates the number of connection errors encountered by this host pool.	Number	Ideally, the value of this measure should be 0. If a non-zero value is reported, then, use the detailed diagnosis of this measure to know what the error is, when it occurred, who caused it, what type of error it is, and what is its source. This information will help you troubleshoot the errors easily.
Total feed errors	Indicates the number of feed errors encountered by this host pool.	Number	Ideally, the value of this measure should be 0. If a non-zero value is reported, then, use the detailed diagnosis of this measure to know what the error is, when it occurred, who caused it, what type of error it is, and what is its source. This information will help you troubleshoot the errors easily.
Total management errors	Indicates the total number of management errors that occurred on this host pool during the last measurement period.	Number	Ideally, the value of this measure should be 0. If a non-zero value is reported, then, use the detailed diagnosis of this measure to know what the error is, when it occurred, who caused it, what type of error it is, and what is its source. This information will help you troubleshoot the errors easily.
Unknown errors	Indicates the total number of 'unknown' errors that occurred on this host pool during the last measurement period.	Number	Ideally, the value of this measure should be 0. If a non-zero value is reported, then, use the detailed diagnosis of this measure to know what the error is, when it occurred, who caused it, what type of error it is, and what is its source. This information will help you troubleshoot the errors easily.
Service errors	Indicates the total number of service errors that occurred on this host pool during the last measurement period.	Number	Ideally, the value of this measure should be 0. If a non-zero value is reported, then, use the detailed diagnosis of this measure to know what the error is, when it occurred, who caused it, what type of error it is, and what is its source. This information will help you troubleshoot the errors easily.