[SDP3][bc36449d-7020-4680-b6ba-628f51d56157] Microsoft Azure role-based cache (WAD) diagnostics

View products that this article applies to.

Summary

In-Role Cache in Microsoft Azure Cache applications uses a diagnostic level for diagnostic data collection. This diagnostic level provides a single setting that you can use to configure the level of data collection.

You can obtain Azure In-role cache diagnostics files from the Microsoft Azure Diagnostics (WAD) storage account. For more information about how to enable the collection of In-Role cache diagnostics data, see the following Microsoft Azure website:

In-Role Cache Troubleshooting and Diagnostics (Microsoft Azure Cache)

If the following functions are not called in the role's OnStart override, In-Role cache diagnostics data will not be transferred to WAD storage.

public override bool OnStart()
{
    DiagnosticMonitorConfiguration dmConfig = 
        DiagnosticMonitor.GetDefaultInitialConfiguration();

    // Configure the collection of cache diagnostic data.
CacheDiagnostics.ConfigureDiagnostics(dmConfig);

DiagnosticMonitor.Start("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString", 
        dmConfig);

    return base.OnStart();
}

Note If the In-Role cache diagnostics is not enabled to be transferred to WAD storage, you may be still able to get the In-Role cache diagnostic data from role-based virtual machines by using the PaaS VM Log SDP package.

↑ Back to the top

More Information

To run the In-Role cache diagnostics package, follow these steps.

Step 1: Enter the Microsoft Azure storage account for WAD

Step 2: Enter the Microsoft Azure storage account access key.

Note You can obtain the account name and key from Azure Management Portal.

Step 3: Enter the deployment ID for the Cache Server role.

Note To locate the deployment ID for the Cache Server role, enable In-Role cache on the Dashboard page of the cloud server in Azure Management Portal.

Step 4: Enter the name of Cache Server role.

Note For dedicated caching, the Cache Server role name is the same as the Cache Worker role name.

Step 5: Enter the instance numbers of the Cache Server role

Note Separate the instance numbers by commas. The input string can be validated.

Step 6: Enter the Cache Client role name.

Note For co-located caching, the Cache Client role name is the same as the Cache Server role name.

Step 7: Enter the start time of the diagnostic data to be collected.

Note The default start time is 24 hours in the past.

Step 8: Enter the end time of the diagnostic data to be collected.

Note The default end time is the current time.

After you complete these steps, a report is generated that provides links to the collected files. See the "Information collected" section for the files that are collected.

Information collected

Location of cache diagnostic data in WAD storage

Log Type	Storage Type	Container/Table Name
ETW traces	Blob	wad-custom-logs
Performance Counters	Table	WADPerformanceCountersTable
Windows Event Logs	Table	WADWindowsEventLogsTable
Crash Dumps	Blob	wad-crash-dumps
Client Logs	Table	WADLogsTable

Diagnostic files collected in the package for Azure In-role cache

Description	File name
.zip file for all client trace files for In-role cache	accountName_ClientTraces.zip
.zip file for all crash dumps files for In-role cache	accountName_CrashDumps.zip
.zip file for all event log files for In-role cache	accountName_EventLogs.zip
.zip file for all PerfMon logs for In-role cache	accountName_PerfMonLogs.zip
.zip file for all Server logs for In-role cache	accountName_ServerLogs.zip

General Information

Description	File name
Basic System Information, including computer name, service pack, computer model, and processor name and speed	resultreport.xml

References

For more information about the Microsoft Automated Troubleshooting Services and about the Support Diagnostic Platform, see the following Microsoft Knowledge Base article:

2598970 Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform

↑ Back to the top