Log4Net and DXC Service

Gregory Langhorst

Vote:

Log4Net is great but I am not seeing best practices on where to log when using the DXC service. Some mention the D:\Home\LogFiles directory while some Azure documentation points to Azure Blob with storage provider configuration. Does anyome have a best practice to share that can be leveraged in DXC without incurring additional costs?

#178655

May 16, 2017 20:30

Johan Petersson

Vote:

Hi,

Have you read this information https://world.episerver.com/digital-experience-cloud-service/troubleshooting/#ActivateLogging?

#178658

May 16, 2017 22:30

Gregory Langhorst

Vote:

I did come across this article but it requires a storage setting which means more monthly fees. I was looking for a free option. Maybe the answer is there isn't a great free solution. The goal is keeping cost down for the customer while providing helpful logging for developers. Thanks for responding.

#178673

May 17, 2017 13:29

Johan Petersson

Vote:

Storage is included in the DXC Service. Where do you store uploaded assets, that requires a storage account as well. What is a free option?

#178674

May 17, 2017 13:31

Per Jungnelius

Vote:

Hi,

For other people coming across this post: There is now possible to download DXC logfiles yourself if you get access to the customer's Paas portal. Request access here: http://world.episerver.com/digital-experience-cloud-service/accessing-azure-information/).

This logging doesn't use Log4net however, so you have to switch from using log4net.LogManager to EPiServer.Logging.LogManager.

For reference, see http://world.episerver.com/documentation/developer-guides/CMS/logging/logging-into--net-diagnostics-trace/ and possibly http://world.episerver.com/digital-experience-cloud-service/troubleshooting/#ActivateLogging.

#184858

Nov 06, 2017 13:24