Azure Cloud Service Diagnostic output changed with 2.6 SDK

AzureSdkAzure Diagnostics

Azure Problem Overview


After upgrading the SDK to Azure Cloud Service Diagnostic 2.6, all the WAD trace logs started to look like this:

EventName="FormattedMessageEvent" FormattedMessage="Subscription {0} Already Created" Argument0="sub2feature-staging" TraceSource="w3wp.exe"

Previously it use to just write out "Subscription sub2feature-staging Already Created" TraceSource="w3wp.exe"

Is this something I can configure? Also looks like a lot of messages has moved from information to verbose.

It's probably a combination of my log provider and some changes done in Azure Cloud Service Diagnostic 2.6.

Azure Solutions


Solution 1 - Azure

I know this is old, but since it is unanswered, it is a great way to test knowledge.

https://docs.microsoft.com/en-us/previous-versions/azure/reference/dn479282(v=azure.100)#azure-sdk-release-dates-retirement-dates-and-support-information

If you goto that link you will see the supported version of .net are 4.5.2, 4.6*, 4.6.1* So it is possible 4.5.1 could work but not be supported.

That would answer why updating your framework fixed the issue.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionPoul K. SørensenView Question on Stackoverflow
Solution 1 - AzureRonView Answer on Stackoverflow