NLogRequestLoggingModule - Introduce ShouldLogRequest

[snakefoot]

Like ShouldLogRequest is available for NLogRequestLoggingMiddleware, so one can downgrade LogLevel, then it should always be available for NLogRequestLoggingModule.

Maybe consider changing the logging so when LogLevel <= Info, then skip logging the exception. But just perform logging of the Exception.Type and Exception.Message (Ex. Input-Validation-Errors).

This could also be useful for ASP.NET Core, where HTTP 499 Client Closed Request together with TaskCanceledException should not be seen as "Error" (catch (OperationCanceledException) when (httpContext.RequestAborted.IsCancellationRequested))

[RomanLeonB]

Hello,
I have experience with NLog and Nlog.Syslog (s. NLog/NLog#5754 (comment)).
As far as I can read, the goal of the ticket is, on the one hand, to support ShouldLogRequest in NLogRequestLoggingModule and, on the other hand, to change the logging so that when LogLevel <= Info, skip logging the exception. Is this correct?

[snakefoot]

You are correct NLogRequestLoggingModule provides request-logging for ASP.NET Classic (not ASP.NET Core), and this issue is about being able to also override ShouldLogRequest, and customize the LogLevel based on the request-result (exception being thrown or http-status-code).

There is also NLogRequestLoggingMiddleware for ASP.NET Core. If you have ideas for improving request-logging with NLog, then pull-requests / ideas are most welcome.