Traditional debugging and troubleshooting of on-premise applications is through the IDE-based Java debugger option to run the application in debug mode with the visibility to the executed code path. For example, a desktop application in-house to an organization to manage their employee information can be developed and tested in a single IDE and debugged through the Java debugger option. However, this approach doesn't let us review the application performance, and has a restriction to replicate the production application issues and distributed issues.
One traditional approach to review the issues is through analyzing the log files during the defect timing. This allows the production application logs to be reviewed for identifying the actual issues; however, it is very time consuming having limited scope and visibility...
