Configure Tracing for application logging RRS feed

  • Question

  • We have a security requirement for more complete logging of activity in both CRM and custom pages—successful requests as well as exceptions—and with the ability to send the log files to the security department if need be. I know that best practice in production environments is to only enable tracing while troubleshooting, but is it possible to enable info-level tracing in such a way that the performance hit in Dynamics isn’t so bad (for example, record only certain trace categories)? It would need to be "on" all the time.

    Or would you recommend custom logging (such as using log4net)? Can log4net be implemented to capture oob CRM activity? (All of what I’ve read so far has it applied only to custom code.)

    Dynamics CRM 2013

    • Edited by CrmAdm Wednesday, August 27, 2014 8:39 PM
    Wednesday, August 27, 2014 8:38 PM

All replies

  • Hi,

    I usually prefer Log4Net. In this way I can debug and customize all in my way. The unique problem is if you are registering your plugin assembly as a sandbox assembly (sandbox mode is required for CRM-online) you will not have access to the file system. In that case, your only option is Tracing.



    Alessandro Graps

    Thursday, August 28, 2014 8:51 AM
  • Hi Alessandro, and thank you for weighing in. Do you know if Log4Net can be used to log standard (non-custom) CRM activity as well? 
    Thursday, August 28, 2014 12:39 PM
  • Hi

    There is an appender for CRM



    but I never tried in crm2013...

    Alessandro Graps

    Monday, September 1, 2014 9:55 AM