dotnetnuke event logging - Synchronous? Potential speed issues? -

I want to take advantage of the DotNetNuke logging system (both event logging and exception logging).

However, I am concerned about potential performance issues if we start logging too many events.

Is the logging system to write an asynchronous database event? If not, is there an effective way to do this? I hate waiting for end-users on many databases to write just one page.

Thanks

short answer: This depends on your DNN configuration. Logging by default is synchronous.

Detailed answer

Event logging in the logging provider to the Web. Set up in config.

DotNetNuke has been sent with DBLoggingProvider and XMLLoggingProvider. By default, DotNetNuke uses the DBLoggingProvider which writes in the EventLog table.

How it is done, depending on the host settings and the event viewer setting of the site, if the host settings should be "as the enable event log buffer " in the check, the logging should be asynchronous must be , as the asynchronous logging uses the scheduler, and if the scheduler is not enabled or stopped, the logging will be immediate.

Instant logging can also be applied with LoginFoda. Property.

The event log setting determines the log type is logged by the base. If you are using event logging in your module, you must give the log type in EventLogController.AddLog method I usually use EventLogType.HOST_ALERT, because these events are easily recognizable in the log view and are logged in by default (as opposed to ADMIN_ALERT).

For more information, check AddLog implementation in DNN source code: