logging - Azure - Enable diagnostics for worker/web role -
i log every exception occurs, (mvc cloudapp), in table storage.
i followed official tutorial microsoft seems complicate things much. tutorial can viewed here: https://azure.microsoft.com/sv-se/documentation/articles/cloud-services-dotnet-diagnostics/#how-to-enable-diagnostics-in-a-worker-role
it feels it's of hassle because azure diagnostics 1.3 isn't supported default? there's faster , easier option in configure window web/worker role let's enable diagnostics 1.0?
i want log exceptions in storage account azure diagnostics 1.0 should enough, no?
what i've done:
- enabled diagnostics in worker , web role clicking on checkbox in configure window web , worker role.
- specified storage account credentials.
what need with:
no wad containers created in storage account. not supposed created after have enabled , specified storage account credentials?
why complicated enable azure diagnostics 1.3 compared 1.0?
what's difference between worker role diagnostics , web role diagnostics? if had app in webrole , caching in worker role.. logged individually? need enable them both if want exception logging both app , caching?
to answer questions:
no wad containers created in storage account. not supposed created after have enabled , specified storage account credentials?
if you're looking wad-control-container
, won't created. should see containers iis logs, failed request logs , crash dumps if have enabled in diagnostics configuration.
why complicated enable azure diagnostics 1.3 compared 1.0?
essentially diagnostics model has changed. version 1.0 plugin model while version 1.3 extension model (it changed sdk 2.5 when introduced version 1.2). whether complicated, think debatable. while 1.0 version rather straight forward , had capabilities definining diagnostics configuration in code, think 1.3 step in right direction. felt frustrated begin realizing benefits offers use more. of benefits appealed me are:
- pure decalarative model instead of mixed model (programmatic + decalarative).
- unified approach collect diagnostics data both cloud services , virtual machines (at time windows only).
- ability enable/disable diagnostics configuration on fly because extension model.
- support etw logs.
some of things don't in 1.3:
- deployment process rather convoluted if you're not deploying through visual studio.
- limited tooling support. options available either visual studio or powershell. @ time, portal (both current , preview) doesn't support it.
- deprecated
on-demand transfer
functionality. use functionality lot deprecated relies on code-based diagnostics changes.
what's difference between worker role diagnostics , web role diagnostics?
afaik, there's no difference between two. depends on diagnostics data want collect each role.
if had app in webrole , caching in worker role. logged individually?
well, yes , no. each role it's own diagnostics.wadcfgx
file define storage account store diagnostics data. if define different storage accounts in each role's wadcfgx
file data go separate storage account. if keep same storage account, data have role name
, role instance name
can distinguish between different diagnostics data.
do need enable them both if want exception logging both app , caching?
yes. need enable them both.
Comments
Post a Comment