Cleaned doc.md

CLI/Program.cs

@@ -1,6 +1,5 @@
 // See https://aka.ms/new-console-template for more information
 
-using DotBased;
 using DotBased.Logging.Serilog;
 using DotBased.Logging;
 using Serilog;

DotBased/doc.md

@@ -1,34 +1 @@
-# DotBased info
-
-## Logging
-In most logging frameworks you will encounter all or some of the following log levels:
-
-- TRACE
-- DEBUG
-- INFO
-- WARN
-- ERROR
-- FATAL
-
-The names of some of those give you a hint on what they are about. However, let’s discuss each of them in greater detail.
-
-TRACE – the most fine-grained information only used in rare cases where you need the full visibility of what is happening in your application and inside the third-party libraries that you use. You can expect the TRACE logging level to be very verbose. You can use it for example to annotate each step in the algorithm or each individual query with parameters in your code.
-
-DEBUG – less granular compared to the TRACE level, but it is more than you will need in everyday use. The DEBUG log level should be used for information that may be needed for diagnosing issues and troubleshooting or when running application in the test environment for the purpose of making sure everything is running correctly
-
-INFO – the standard log level indicating that something happened, the application entered a certain state, etc. For example, a controller of your authorization API may include an INFO log level with information on which user requested authorization if the authorization was successful or not. The information logged using the INFO log level should be purely informative and not looking into them on a regular basis shouldn’t result in missing any important information.
-
-WARN – the log level that indicates that something unexpected happened in the application, a problem, or a situation that might disturb one of the processes. But that doesn’t mean that the application failed. The WARN level should be used in situations that are unexpected, but the code can continue the work. For example, a parsing error occurred that resulted in a certain document not being processed.
-
-ERROR – the log level that should be used when the application hits an issue preventing one or more functionalities from properly functioning. The ERROR log level can be used when one of the payment systems is not available, but there is still the option to check out the basket in the e-commerce application or when your social media logging option is not working for some reason.
-
-FATAL – the log level that tells that the application encountered an event or entered a state in which one of the crucial business functionality is no longer working. A FATAL log level may be used when the application is not able to connect to a crucial data store like a database or all the payment systems are not available and users can’t checkout their baskets in your e-commerce.
-
-To summarize what we know about each of the logging level:
-Log Level	Importance
-- Fatal	One or more key business functionalities are not working and the whole system doesn’t fulfill the business functionalities.
-- Error	One or more functionalities are not working, preventing some functionalities from working correctly.
-- Warn	Unexpected behavior happened inside the application, but it is continuing its work and the key business features are operating as expected.
-- Info	An event happened, the event is purely informative and can be ignored during normal operations.
-- Debug	A log level used for events considered to be useful during software debugging when more granular information is needed.
-- Trace	A log level describing events showing step by step execution of your code that can be ignored during the standard operation, but may be useful during extended debugging sessions.
+# DotBased