When comparing NLog vs JSNLog, the Slant community recommends NLog for most people. In the question“What are the best .NET logging frameworks?” NLog is ranked 1st while JSNLog is ranked 6th. The most important reason people chose NLog is:
The config file is fairly easy to understand and modify without having to pore over pages and pages of documentation.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easily configurable
The config file is fairly easy to understand and modify without having to pore over pages and pages of documentation.
Pro Easy to set up
Getting starting with NLog is quick and you can be up and running in a matter of minutes by following the official Getting Started tutorial.
Pro Supports Semantic Logging
Pro Integrates with your existing server-side logging package
Not a hosted option, so you'll store client-side logs along with your server-side logs.
Pro Stack traces
JSNLog passes exception log messages with its stack trace.
Cons
Con No hosted option
You'll have to store client-side logs along with your server-side logs.
Con No reporting capabilities
Your server logging solution should provide that, and JSNlog integrates with Elmah, Log4Net, NLog, Serilog, Common.Logging.