Default Parameters for AzrWVDMgmtTest

If administrators fail to pay attention to API- or Powershell- initiated cloud configuration changes, it can sometimes add to their management woes! Unauthorized users may gain entry into the AVD ecosystem and create many unwanted objects, delete key objects, and even update objects with changes that can have an adverse impact on the AVD service. To avoid this, administrators should periodically run the AVD Management Activity test and audit management activities performed on the AVD service. This test tracks the configuration changes - i.e., object creations, deletions, updates, fetches - that were successfully effected on each AVD host pool, using the Azure API/Powershell. Detailed diagnosis, if enabled, reveals when each change occurred, who initiated it, and how many objects were impacted. Using this information, administrators can quickly determine whether/not the changes are valid, and can also confirm if such changes were performed by authorized personnel only.

This page depicts the default parameters that need to be configured for the AzrWVDMgmtTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored in the SUBSCRIPTION ID text box.To know the ID that maps to the target subscription, click here.

• Specify the Directory ID of the Azure AD tenant to which the target subscription belongs in the TENANT ID text box. To know how to determine the Directory ID/Tenant ID, click here.

• The eG agent communicates with the target Microsoft Azure Subscrption using Java API calls. To collect the required metrics, the eG agent requires an Access token in the form of an Application ID and the client secret value.Specify the Application ID of the created Application in the CLIENT ID TEXTBOX To know how to determine the Application ID, click here. Specify the client secret value in the CLIENT PASSWORD text box. To obtain the client secret value, click here.

• 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.

• 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.

• 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, click here. 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, click here.

• By default, this test does not report detailed diagnostics for the Objects fetched measure. Accordingly, SHOW OBJECT FETCHED DD parameter is set to No by default.

  Typically, in large AVD roll-outs, this measure can report numerous records as part of detailed diagnostics. In such environments therefore, the detailed statistics for this measure can consume excessive space in the eG database. This default setting conserves valuable database space by ensuring that the test does not collect detailed metrics for the Objects fetchedmeasure.

  However, If you have a well-sized and well-tuned eG database, you can configure the test to capture detailed metrics for this measure. To achieve this, set SHOW OBJECT FETCHED DD flag to Yes.

• By default, this test does not report detailed diagnostics for the Objects created measure. Accordingly, SHOW OBJECT CREATED DD parameter is set to No by default.

  Typically, in large AVD roll-outs, this measure can report numerous records as part of detailed diagnostics. In such environments therefore, the detailed statistics for this measure can consume excessive space in the eG database. This default setting conserves valuable database space by ensuring that the test does not collect detailed metrics for the Objects fetchedmeasure.

  However, If you have a well-sized and well-tuned eG database, you can configure the test to capture detailed metrics for this measure. To achieve this, set SHOW OBJECT CREATED DD flag to Yes.

• By default, this test does not report detailed diagnostics for the Objects updated measure. Accordingly, SHOW OBJECT UPDATED DD parameter is set to No by default.

  Typically, in large AVD roll-outs, this measure can report numerous records as part of detailed diagnostics. In such environments therefore, the detailed statistics for this measure can consume excessive space in the eG database. This default setting conserves valuable database space by ensuring that the test does not collect detailed metrics for the Objects fetchedmeasure.

  However, If you have a well-sized and well-tuned eG database, you can configure the test to capture detailed metrics for this measure. To achieve this, set SHOW OBJECT UPDATED DD flag to Yes.

• By default, this test does not report detailed diagnostics for the Objects deleted measure. Accordingly, SHOW OBJECT DELETED DD parameter is set to No by default.

  Typically, in large AVD roll-outs, this measure can report numerous records as part of detailed diagnostics. In such environments therefore, the detailed statistics for this measure can consume excessive space in the eG database. This default setting conserves valuable database space by ensuring that the test does not collect detailed metrics for the Objects fetchedmeasure.

  However, If you have a well-sized and well-tuned eG database, you can configure the test to capture detailed metrics for this measure. To achieve this, set SHOW OBJECT DELETED DD flag to Yes.

• 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.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.