Logs are key to part of any software. Read how can one make the log more insightful. Learn about things to keep in mind and things to avoid while logging.<\/b>
\nJoin the DZone community and get the full member experience. What is going on? Why it is not working like that? This is not expected behavior:( Sounds familiar? I am sure every software engineer has been in this situation where they are not able to figure out what is going on in the code? Well, sometimes an Insightful log statement can come in handy to answers the queries. Let us go over a few things which I personally have adopted and feel are decent enough for others to follow for effective and insightful logging. Note: While writing this, log4j has been kept in mind. Some commonly used log levels: FATAL, ERROR, WARN, INFO, DEBUG, TRACE. Simple interpretation can be taken as: Logs should help out software engineers to figure out Where, What, and Why something went wrong. If the developer is able to find issues just from logs, logging is good. Happy Logging!:) Published at DZone with permission of Setu Patani. See the original article here. Opinions expressed by DZone contributors are their own.<\/p>\n