This post has been republished via RSS; it originally appeared at: Microsoft Developer Blogs - Feed.
In this post, Sr. Consultant Kurt Schenk explains how to instrument your SF Cluster to send diagnostic data to Log Analytics.CollectServiceFabricData (https://github.com/microsoft/CollectServiceFabricData) is a fantastic tool created and used by the Service Fabric Support team to easily ingest Azure Service Fabric traces and diagnostic data into your Log Analytics workspace, or Azure Data Explorer instance. Once you have done this, you can run powerful interactive analytics queries. This Service Fabric traces and diagnostic data is stored in the Azure Storage account that was configured in ARM. For example:
{ "name": "[concat('VMDiagnosticsVmExt','_vmNodeType0Name')]", "properties": { "type": "IaaSDiagnostics", "autoUpgradeMinorVersion": true, "protectedSettings": { "storageAccountName": "[variables('applicationDiagnosticsStorageAccountName')]", "storageAccountKey": "[listKeys(resourceId('Microsoft.Storage/storageAccounts', variables('applicationDiagnosticsStorageAccountName')),'2015-05-01-preview').key1]", "storageAccountEndPoint": "https://core.windows.net/" }The Fabric Diagnostics Collection Agent (FabricDCA) which runs on each Service Fabric node then sends the traces and diagnostic data below to this Azure Storage account:
- service fabric detailed .dtr logs in .zip. (fabriclogs-*)
- service fabric counter .blg files. (fabriccounters-*)
- service fabric fabric exceptions .dmp files. (fabriccrashdump-*)
- service fabric events stored in Azure blob tables
- service fabric setup .trace files