DiagnosticMonitor takes too long to start

If you try to start diagnostic monitoring  by calling  DiagnosticMonitor.Start(..) it can happen that this call takes too long (2 Minutes). After this time the call will just return successfully. Unfortunately you will figure out later that diagnostic monitoring does not work at all.

In fact there is not any error and nothing works.

This will happen if you setup an not existing account name in diagnostic connection string. The TCP/HTTP call will in this case try to resolve the storage with THEACCOUNT prefix (which does not exist) and fail time-out.

Unfortunately the Start() will return with no exception.

   <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString"
                 value="DefaultEndpointsProtocol=https;AccountName=THEACCOUNT;..

You can figure out this behavior in console of Compute Emulator.