Write logs outside of WebApp

[SeanFeldman]

Into %home%\LogFiles that is used for all other logs by Azure

[SeanFeldman]

@andreasohlund after reviewing this, I'm questioning the traditional approach of writing a file. Anything written to Trace is captured by azure website/webjob. We can enable writing that into storage table. A new log file is created every hour (default setting).

This is how it would look like in blob storage:

Sample of captured blob (log file):

apicomparer/2015/04/01/03/c0216c.applicationLog.csv

Content of file is:

date,level,applicationName,instanceId,eventTickCount,eventId,pid,tid,message,activityId
2015-04-01T03:00:04,Information,apicomparer,c0216c,635634540045036971,0,652,20,2015-04-01 03:00:04.503 ERROR NServiceBus.Faults.Forwarder.FaultManager Message with 'a02d976e-85b1-4127-917c-a46d0030c0ef' id has failed FLR and will be moved to the configured error queue.,

Alternatively, we could capture this into storage table, but that would be a single table for all logs, which would make it less responsive to work with over time.

I think we should not write our own files.
Thoughts?

[andreasohlund]

You're the expert! :)

On Wed, Apr 1, 2015 at 5:06 AM, Sean Feldman [email protected]
wrote:

@andreasohlund https://github.com/andreasohlund after reviewing this,
I'm questioning the traditional approach of writing a file. Anything
written to Trace is captured by azure website/webjob. We can enable writing
that into storage table. A new log file is created every hour (default
setting).

Sample of captured blob (log file):

apicomparer/2015/04/01/03/c0216c.applicationLog.csv

Content of file is:

date,level,applicationName,instanceId,eventTickCount,eventId,pid,tid,message,activityId
2015-04-01T03:00:04,Information,apicomparer,c0216c,635634540045036971,0,652,20,2015-04-01 03:00:04.503 ERROR NServiceBus.Faults.Forwarder.FaultManager Message with 'a02d976e-85b1-4127-917c-a46d0030c0ef' id has failed FLR and will be moved to the configured error queue.,

Alternatively, we could capture this into storage table, but that would be
a single table for all logs, which would make it less responsive to work
with over time.

I think we should not write our own files.
Thoughts?

—
Reply to this email directly or view it on GitHub
#22 (comment)
.