Επεξεργασία

Κοινή χρήση μέσω

Set up diagnostics for Autoscale in Azure Virtual Desktop

  • Άρθρο

Diagnostics lets you monitor potential issues and fix them before they interfere with your Autoscale scaling plan.

Currently, you can either send diagnostic logs for Autoscale to an Azure Storage account or consume logs with Microsoft Azure Event Hubs. If you're using an Azure Storage account, make sure it's in the same region as your scaling plan. Learn more about diagnostic settings at Create diagnostic settings. For more information about resource log data ingestion time, see Log data ingestion time in Azure Monitor.

Tip

For pooled host pools, we recommend you use Autoscale diagnostic data integrated with Insights in Azure Virtual Desktop, which providing a more comprehensive view of your Autoscale operations. For more information, see Monitor Autoscale operations with Insights in Azure Virtual Desktop.

Enable diagnostics for scaling plans

To enable diagnostics for your scaling plan:

  1. Open the Azure portal.

  2. In the search bar, type Azure Virtual Desktop and select the matching service entry.

  3. Select Scaling plans, then select the scaling plan you'd like the report to track.

  4. Go to Diagnostic Settings and select Add diagnostic setting.

  5. Enter a name for the diagnostic setting.

  6. Next, select Autoscale logs and choose either Archive to a storage account or Stream to an event hub depending on where you want to send the report.

  7. Select Save.

Note

If you select Archive to a storage account, you'll need to Migrate from diagnostic settings storage retention to Azure Storage lifecycle management.

Find Autoscale diagnostic logs in Azure Storage

After you've configured your diagnostic settings, you can find the logs by following these instructions:

  1. In the Azure portal, go to the storage account you sent the diagnostic logs to.

  2. Select Containers and open the folder called insight-logs-autoscaling.

  3. Within the insight-logs-autoscaling folder select the subscription, resource group, scaling plan, and date until you see the JSON file. Select the JSON file and download it to your local computer.

  4. Finally, open the JSON file in the text editor of your choice.

View diagnostic logs

Now that you've opened the JSON file, let's do a quick overview of what each piece of the report means:

  • The CorrelationID is the ID that you need to show when you create a support case.

  • OperationName is the type of operation running while the issue happened.

  • ResultType is the result of the operation. This item can show you where issues are if you notice any incomplete results.

  • Message is the error message that provides information on the incomplete operation. This message can include links to important troubleshooting documentation, so review it carefully.

The following JSON file is an example of what you'll see when you open a report:

{
    "host_Ring": "R0",
    "Level": 4,
    "ActivityId": "c1111111-1111-1111-b111-11111cd1ba1b1",
    "time": "2021-08-31T16:00:46.5246835Z",
    "resourceId": "/SUBSCRIPTIONS/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/RESOURCEGROUPS/TEST/PROVIDERS/MICROSOFT.DESKTOPVIRTUALIZATION/SCALINGPLANS/TESTPLAN",
    "operationName": "HostPoolLoadBalancerTypeUpdated",
    "category": "Autoscale",
    "resultType": "Succeeded",
    "level": "Informational",
    "correlationId": "aaaa0000-bb11-2222-33cc-444444dddddd",
    "properties": {
        "Message": "Host pool's load balancing algorithm updated",
        "HostPoolArmPath": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/test/providers/microsoft.desktopvirtualization/hostpools/testHostPool ",
        "PreviousLoadBalancerType": "BreadthFirst",
        "NewLoadBalancerType": "DepthFirst"
    }
}

Next steps