A popular logging framework with .NET developers is log4net, a text-only logging library that has been ported to .NET from the well-known Java logging library log4j. Similar to how I already outlined in our recent log4j blog posting, we regularly get emails from users who are interested in switching from log4net to SmartInspect. They want to take advantage of SmartInspect’s rich logging capabilities, our Console (SmartInspect’s monitoring and analysis tool) and all the unique protocol options available in SmartInspect (such as log file encryption, the memory protocol, backlog queues etc).
Switching to a new logging library is not an easy task if you have to replace all existing logging calls with new ones. Luckily, you can extend log4net with custom appenders that allow you to route the log messages to a new destination, for example, to SmartInspect. We have developed such an appender (two, actually) and demonstrate how to use them in a new article:
We hope this will make it a lot more attractive for .NET developers to port existing projects that make use of the classic log4net log framework to SmartInspect.
Customer Portal
Using a custom Log4net appender with SmartInspect
A popular logging framework with .NET developers is log4net, a text-only logging library that has been ported to .NET from the well-known Java logging library log4j. Similar to how I already outlined in our recent log4j blog posting, we regularly get emails from users who are interested in switching from log4net to SmartInspect. They want to take advantage of SmartInspect’s rich logging capabilities, our Console (SmartInspect’s monitoring and analysis tool) and all the unique protocol options available in SmartInspect (such as log file encryption, the memory protocol, backlog queues etc).
Switching to a new logging library is not an easy task if you have to replace all existing logging calls with new ones. Luckily, you can extend log4net with custom appenders that allow you to route the log messages to a new destination, for example, to SmartInspect. We have developed such an appender (two, actually) and demonstrate how to use them in a new article:
Using a Custom Log4net Appender with SmartInspect
We hope this will make it a lot more attractive for .NET developers to port existing projects that make use of the classic log4net log framework to SmartInspect.