EggEgg.CSharp-Logger 3.8.52-beta

csharp-logger

A convenient C# Logger implementation, with reliable console interaction encapsulation support available.

You can download it on nuget.org by searching EggEgg.CSharp-Logger.

Update

v4.0.0 - Preview 9 Patch 2 (v3.8.52-beta)

(Note: This is the last minor preview version before the official version v4.0.0. Its latest Patch will be identical to the official version v4.0.0.)

This version almost re-implements the entire logger, extracting the main functions of the static class Log and encapsulating them into BaseLogger. The original functions are not affected and some bugs have been fixed, but there may be some breaking changes.

Please note that although BaseLogger is a complete log implementation, you must first call Log.Initialize to use it. In addition, although different initialization LoggerConfig can be provided for each BaseLogger, its key fields must be consistent with the version provided when Log.Initialize, to keep the behavior of Logger consistent throughout the program.
The affected fields at this stage are: Use_Console_Wrapper, Use_Working_Directory, Max_Output_Char_Count, Enable_Detailed_Time.

Main changes:

• Fixed the problem that due to the defect of the timing algorithm, the log processing background task will not wait for the specified time after processing the log.

• Fixed the problem that in most cases, the waiting time for cleaning (1.5s) will reach the maximum value, and it is still possible that the console cleaning cannot be completed.

• A new KMP-based algorithm is used to analyze color tag information, which speeds up processing. See Benchmark data for details.

• Added LogTextWriter, but note that it uses a buffer to maintain characters that have not been wrapped; that is, all content before the newline character is not displayed in Logger.
  If some external code uses the Console method and you use ConsoleWrapper (such as CommandLineParser), you must provide an instance of LogTextWriter for it.

• Added LoggerChannel. For code that implements a certain logic, it usually passes the same sender parameter when calling the Log method. You can create LoggerChannel to reduce the amount of code and increase maintainability.

• Some static methods pointing to the corresponding methods of BaseLogger were created in the Log static class.

• Now you can set whether to enable time details by setting LoggerConfig.Enable_Detailed_Time. By default, the time recorded by Logger is only accurate to the second and does not include the date, corresponding to the formatted string HH:mm:ss.
  After enabling time details, the details of the log submission time up to one-seventh of a second will be displayed. The corresponding formatted string is yyyy-MM-dd HH:mm:ss fff ffff. The two parts fff and ffff represent the millisecond level and the ten-thousandth of a millisecond (100 nanoseconds, 0.1 microseconds) level, such as 2023-08-22 15:43:36 456 4362. This configuration requires global unity and is effective for both console and log file output.

• When creating a new log file, you can use LogFileConfig.IsPipeSeparatedFormat to indicate whether the created log file is a pipe-separated value file (PSV).
  Outputting the log as a table is helpful for analysis when the data volume is extremely large, especially if a large amount of modular code in the program does not change the sender parameter when calling the Log method. This configuration does not affect the content output to the console, and for some performance considerations, currently only | is accepted as the separator. The output format is:

  [time]|[level]|[sender]|[content]
  23:14:17|Warn|TestSender|Push a warning log!
  

• Now you can provide a basedlogger parameter for LogTraceListener and LogTextWriter to change their output target BaseLogger. The default value is still Log.GlobalBasedLogger shared by the global static class.

• Some codes of tonerdo/readline are used to implement the new version of ConsoleWrapper. But please note that this version of the nuget package does not include references to the nuget package ReadLine, nor does it include the ReadLine class. All operations are still encapsulated as ConsoleWrapper.

• The experience of modifying text when the text volume is large in ConsoleWrapper has been greatly improved.

• Now setting ConsoleWrapper.AutoCompleteHandler can auto-complete user input.

• Optimized the method indication in the Log, BaseLogger and LoggerChannel classes.

Breaking changes

• Now if the user indicates to use the program path (provided false for LoggerConfig.Use_Working_Directory) during Log.Initialize and it cannot be accessed, compared with the previous implementation, it will not issue a warning that the program will fallback to the working directory. Similarly, there will be no warning prompts if an error occurs when compressing past log files.
• Important: In the new version, not only latest.log and latest.debug.log, but any log files under the logs folder that match the wildcard latest.*.log will be renamed to the last time they were written when Log.Initialize processes past logs.
  They are also affected by automatic log compression, but this is actually consistent with past behavior.
• Now at the end of the program, the leave time given to Logger is 1000ms, and the leave time given to console output (whether it is normal output or ConsoleWrapper) is 500ms (it will only be performed after Logger's cleaning work is completed). In previous versions, these two numbers were 300ms and 1200ms respectively.
• The color judgment uses a new algorithm, so it may not be "bug compatible" with the previous implementation.
• ConsoleWrapper uses a new algorithm, developers try to put the breaking changes caused by it below, but the fixed bugs may not be listed.
• ConsoleWrapper used to support pasting multi-line text into the input (although there will be problems when modifying the text); now it does not support this function, and all newline characters entered will be replaced with two spaces.

  The list of recognized newline sequences is CR (U+000D), LF (U+000A), CRLF (U+000D U+000A), NEL (U+0085), LS (U+2028), FF (U+000C), and PS (U+2029). This list is given by the Unicode Standard, Sec. 5.8, Recommendation R4 and Table 5-2.

• ConsoleWrapper now supports history merging similar to bash, that is, executing a command multiple times in a row will not leave multiple records in history.
• The new reading method of ConsoleWrapper is similar to GNU Readline, but this causes a conflict with the past behavior of Ctrl+C, so the function of Ctrl+C triggering the ConsoleWrapper.ShutDownRequest event is retained. In addition to this, all other functions of the attached GNU readline shortcut keys can be regarded as breaking changes.
• This project will not be backward compatible with any version below .NET 6.0 in the future, including .NET Standard 2.1.

Features

• Basic log implementation
  Usage: First Log.Initialize(LoggerConfig), then Log.Info(content, sender), Log.Erro(...)、Log.Warn(...)、Log.Dbug(...). You can also first call Log.GetChannel(sender) to determine a sender parameter, and then call logchan.LogInfo(content).

• Color output Support
  Just add xml tags in text, like:<color=Red>Output as red color</color>.
  The Color value should be a valid value in ConsoleColor, e.g. "Red", "Green". Recognized color tags will be removed in the log file.

• Parallel user input/log output support
  If you want to read the user's input while outputting logs in parallel (e.g. making a CLI program), ConsoleWrapper is provided.
  You can set the value of ConsoleWrapper.InputPrefix as a waiting-input prefix, just like mysql> or ubuntu ~$, and use ConsoleWrapper.ReadLineAsync to read inputs from the user.
  It accepts some GNU readline shortcut keys to read data. The following table is the support list:

  Shortcut key	Function
  Ctrl+A / HOME	Go to the beginning of the input
  Ctrl+B / ←	Move the cursor back one character (usually move left)
  Ctrl+C	Different from GNU readline, it means to terminate the program
  Ctrl+E / END	Go to the end of the input
  Ctrl+F / →	Move the cursor forward one character (usually move right)
  Ctrl+H / Backspace	Delete one character before the cursor
  Tab	Auto complete
  Shift+Tab	Previous auto complete
  Ctrl+J / Enter	Confirm input
  Ctrl+K	Cut off the characters from the cursor position (including) to the end of the input
  Ctrl+L	Clear the input area
  Ctrl+M	The effect is equivalent to enter
  Ctrl+N / ↓	Next command history
  Ctrl+P / ↑	Previous command history
  Ctrl+U	Cut off the characters from the cursor position (not including) to the beginning of the input
  Ctrl+W	Cut off a word before the cursor, that is, cut off the characters from the cursor position (not including) to the first space behind (usually left) (not including)
  Ctrl+T	Transpose (reverse) the character before the current cursor position with the character after it, and move the cursor forward one position (to the right)
  Backspace	Delete one character before the cursor
  Ctrl+D / Delete	Delete one character at the cursor position

  In addition, it can read data larger than 4096 bits without any configuration. But please note that when the user's input is very large and the console frequently outputs logs, it may affect performance. It is disabled by default, and you can enable it through LoggerConfig(use_Console_Wrapper: true).

• Output Quantity Limit Outputting a large amount of information to the console can severely impact performance. You can set the maximum output limit for each log message using LoggerConfig.Max_Output_Char_Count. If a log message exceeds this value, its content will not be displayed in the console, and a special warning will be shown instead. You can find the content in the log file. You can also disable this feature by setting it to -1.

• Auto Compress Logs If there are logs created 1 day ago, they will be compressed into a zip file like logs.[Date].zip.

• Separated Table Record When creating each new log file, you can use LogFileConfig.IsPipeSeparatedFormat to indicate whether the log file should be in Pipe-separated values format (PSV).
  Outputting logs as a table helps with analysis when dealing with large amounts of data, especially if the Log method is called by modularized code that does not change the sender parameter. This configuration does not affect the content output to the console, and currently only accepts | as the separator for performance reasons. The output format is:

  [time]|[level]|[sender]|[content]
  23:14:17|Warn|TestSender|Push a warning log!
  

Best Practices

1. Call Log.Initialize(LoggerConfig) at the entry point of the program (or anywhere else, the earlier the better) to initialize globally, then start using the log related methods.

2. If the program uses CommandLineParser, please redirect its output TextWriter. The code is as follows:

   public readonly static Parser DefaultCommandsParser = new Parser(config =>
   {
       // Set custom ConsoleWriter during construction
       config.HelpWriter = TextWriter.Synchronized(new LogTextWriter("CommandLineParser"));
   });
   

3. Be careful to configure the various functions of LoggerConfig. If you just want to use it as a regular logger, here is a recommended configuration:

   Log.Initialize(new LoggerConfig(
       max_Output_Char_Count: -1,
       use_Console_Wrapper: false,
       use_Working_Directory: true,
   #if DEBUG
       global_Minimum_LogLevel: LogLevel.Verbose,
       console_Minimum_LogLevel: LogLevel.Information,
   #else
       global_Minimum_LogLevel: LogLevel.Information,
       console_Minimum_LogLevel: LogLevel.Information,
   #endif
       debug_LogWriter_AutoFlush: true,
       is_PipeSeparated_Format: false,
       enable_Detailed_Time: false
       ));
   

4. If you want to use the ConsoleWrapper function, you need to set the use_Console_Wrapper in the above LoggerConfig to true, and then start using its function.

5. When creating a new log file, you can use LogFileConfig.IsPipeSeparatedFormat to indicate whether the created log file is a pipe-separated value file (PSV).
   Outputting the log as a table is helpful for filtering and analysis when the data volume is extremely large, especially if a large amount of modular code in the program does not change the sender parameter when calling the Log method. You can use BaseLogger(LoggerConfig, LogFileConfig) to create a BaseLogger and its log file specifically for statistical data, and make content also use a similar PSV format for data query.

6. You can enable the time detail of the log by setting enable_Detailed_Time in LoggerConfig to true. By default, the time recorded by Logger is only accurate to the second and does not include the date, corresponding to the formatted string HH:mm:ss.
   After enabling time details, it will display the details of the log submission time up to one-seventh of a second, and the corresponding formatted string is yyyy-MM-dd HH:mm:ss fff ffff, the two parts fff and ffff represent the millisecond level and the ten-thousandth of a millisecond (100 nanoseconds, 0.1 microseconds) level, such as 2023-08-22 15:43:36 456 4362. This configuration requires global unity and is effective for both console and log file output.

7. If you're using ConsoleWrapper, you'd better subscribe event ConsoleWrapper.ShutDownRequested to do certain responses when the user pressing Ctrl+C. Notice that sender and args provided by the EventHandler make no sense.