. NET Log System Design

Logs are obviously an important means to help you locate the problem. Originally, NLog was intended to be used directly as a system log tool, a metamorphosis has to say that there are many uncontrollable factors. Here I will tell you how I implement the Log Module.

Overall Architecture

• Here, I divide the daily classification into tracking, and the three definitions of BUG and error are enumerated as follows:

     /           =

• Here we consider the scalability of the Log Module (two methods are supported for databases and files). Here we use the adapter mode to complete this module. Here we will provide you with year-end benefits. Post Code

Define an interface ILogTarget

                                 WriteTrack(                            WriteBug(                            WriteError(

 

• FileLog, and DBLog classes implement the above interface. The specific reality is not attached here.

                WriteTrack(   WriteBug(   WriteError( 

 

      WriteTrack(   WriteBug(   WriteError( 

     ._adaptee =  WriteTrack(  WriteBug(  WriteError(

• Call Method

SmartLog log = SmartLog ();