The Accelerator has logging built into the runtime engine.

For WPF, you have the ability to log both the client and server side code.  The log settings for the client are located in the app.config within your System WPF project.  The server side log settings are located in your web.config withing your BP Service Host Project. 

For MVC, you can log just the server side. The server side log settings are located in your web.config within your MVC project.

By default, the Accelerator generates with the following log settings:

<!--Logging Settings -->
    <add key="Logging.Enabled" value="True" />
    <add key="Logging.AssemblyName" value="A4DN.Core.BOS.Logging.dll" />
    <add key="Logging.ClassName" value="A4DN.Core.BOS.Logging.AB_NLogLogger" />
<!--Valid values are "Debug," "Info," "Warn," "Error," "Fatal" (Debug is the most verbose, Fatal is the least.)-->
    <add key="Logging.LoggerLevel" value="Error" />
    <add key="Logging.Async" value="True" />
    <add key="Logging.LogPath" value="%APPDATA%\Accelerator for .NET\Logging\<YourSystemName>" />
<!-- Remote Logging Settings -->
    <add key="Logging.RemoteLoggingEnabled" value="True" />
    <add key="Logging.RemoteLoggerLevel" value="Error" />

You can change any of these settings in your WPF app.config and/or BP service Host Web.config for WPF client and server side logging; and in your MVC project Web.config for MVC server side logging.

Here is information regarding the app.setting logging keys and values:

  • Key: Logging.AssemblyName
    • The name of the assembly that holds the logger implementation that will be used to perform logging. By default, the accelerator uses A4DN.Core.BOS.Logging.dll.  You are welcome to develop your own and plug in your DLL Assembly Name.
  • Key: Logging.ClassName
    • The full namespace of the class that implements the logger interface. By default, the accelerator uses A4DN.Core.BOS.Logging.AB_NLogLogger.  You are welcome to develop your own and plug in your Class Name.
  • Key: Logging.LoggerLevel
    • The minimum message level to log.
    • Valid values are Debug, Info, Warn, Error, Fatal
      • Debug is the most verbose, Fatal is the least.
  • Key: Logging.Enabled
    • The flag to enable logging.
    • Valid values are True, False
  • Key: Logging.Async
    • The flag to set logging to be synchronous or asynchronous
    • Valid values are True, False
  • Key: Logging.LogPath (Only use if storing logs to a file)
    • Set the path the log files will be written to.
    • Valid values are a valid windows folder path
  • Key: Logging.EventLogName (Only use if storing logs to event viewer)
    • Set the name of the EventLog section to write the logs to.
    • Valid values are any permitted Event Viewer section name
  • Key: Logging.SourceName (Only use if storing logs to event viewer)
    • Set the source value in the event viewer log
    • Valid values are any string value
  • Key: Logging.RemoteLoggingEnabled
    • Set the client to make service calls to the error logging service for the event log module
    • Valid values are True, False
  • Key: Logging.RemoteLoggerLevel
    • Sets the value to be logged using the remote logging service to create logging entries on the server
    • Values include Debug, Info, Warn, Error, Fatal
    • Warning DO not use Info or Debug in production setting as it will make excessive network calls. 

You have the option to log to a windows folder or windows event viewer and/or to the Accelerator remote Event Log module. 

Retailed Topics:

http://support.surroundtech.com/thread/accelerator-launch-pad-and-maintenance-logging/

http://support.surroundtech.com/thread/accelerator-remote-error-logging/