MPLog View 2021.01.16 18:00
Why do you need a log viewer?
Each software always has at least 1 error, usually more. Fixing the bug is usually a difficult task. Fixing bugs is also a challenging task for experienced programmers and developers and it takes much time and costs money. The extra money that was not anticipated.
- Developers too often analyze log files using a text editor only.
- It is not very effective in complex multi-threaded applications.
- The number in the logged line of the log is very helpful as well as the depth of the stack nesting.
- The file name, line number, and method name are standard for each logger.
MPLog View 2021.01.09 18:38
Why is logging useful?
Logging is useful in all non-trivial applications especialy in real time aplications. In the case of an error the logged exception will tell you the state of the program at the exact point of failure. If we had no log files, then we would have to depend only on the customer's or the support team's description of what happens in what case.
Logging is hepful for the information you cannot get at the time of failure. In the first step:
- Capture stack traces
- Capture what data was being processed when your application crashed
- Remember, debuggers only help if they are present when the crash happens
MPLog View 2021.01.09 18:37
Logging Standard
Logging is essential, there is a standard RFC_5424 on how to log from applications. The main part here is the severity of logs as listed below:
- 0 Emergency: the system is unusable
- 1 Alert: action must be taken immediately
- 2 Critical: critical conditions
- 3 Error: error
- 4 Warning: warning
- 5 Notice: normal but significant
- 6 Informational: informational
- 7 Debug: debug-level messages