1. SummaryLogging, often a back-burner activity in the development cycle can actually be the very lifeline of the development team once the application is in production. Assuming that readers are well acquainted with various logging frameworks like Log4J, SLF4J, etc, this article lays guidelines for 'real-world' production logging, examines its influence on the application quality attributes and also rediscovers a forgotten high performance, smarter logging technique with codes and centralized logging.
2 IntroductionLogging is often relegated to a back-burner activity while architecting, designing and developing applications or even when enhancing applications. Finally when the application is ready, you deploy it. And then what happens? Your application now is out of your development environment - it is not running out of your favorite IDE workbench and much less having a debugger at your service. It is now that you realize the importance of logs. And as you wade through a huge set of logs trying to debug any problem with your application, you realize that it is not a trivial task. It is boring, tedious and time-taking. You ask yourself, with all your experience and expertise, is this what you were destined to do - finding a needle in a haystack of logs! Or possibly you off-load this activity to your sub-ordinates or an application maintenance team who equally curse you for their tedious and thankless job! Or possibly they would just throw up their hands, and you the specialized architect/designer would get involved, muttering under your breath how your skills are being wasted away. Logs can be the very lifeline of your production application and should not be taken lightly or as an afterthought. Sure, most of us know the basics - that there are various logging levels which can be turned on or off at will, that there are log categories and using one's favorite logging framework - Log4J, Commons Logging or SLF4J one can direct logs to various destinations such as Files, Databases, JMS Queues, etc. Read more: Architect zone
QR:
2 IntroductionLogging is often relegated to a back-burner activity while architecting, designing and developing applications or even when enhancing applications. Finally when the application is ready, you deploy it. And then what happens? Your application now is out of your development environment - it is not running out of your favorite IDE workbench and much less having a debugger at your service. It is now that you realize the importance of logs. And as you wade through a huge set of logs trying to debug any problem with your application, you realize that it is not a trivial task. It is boring, tedious and time-taking. You ask yourself, with all your experience and expertise, is this what you were destined to do - finding a needle in a haystack of logs! Or possibly you off-load this activity to your sub-ordinates or an application maintenance team who equally curse you for their tedious and thankless job! Or possibly they would just throw up their hands, and you the specialized architect/designer would get involved, muttering under your breath how your skills are being wasted away. Logs can be the very lifeline of your production application and should not be taken lightly or as an afterthought. Sure, most of us know the basics - that there are various logging levels which can be turned on or off at will, that there are log categories and using one's favorite logging framework - Log4J, Commons Logging or SLF4J one can direct logs to various destinations such as Files, Databases, JMS Queues, etc. Read more: Architect zone
QR:
Posts
0 comments:
Post a Comment