Application Logging
From my perspective I see logging as an essential component of most applications. It provides a framework on which we can attach items of interest at a later time. There are so many things that can make sense to log. There are so many ways to log things as demonstrated in many of the different logging frameworks.
So, my question today is what comes first, the application or the logging. Or, do they both get implemented at the same time. If you add it on later as you need insight into why your application is behaving in some fashion you may find your application requires serious refactoring in order to output logging information effectively.
If you start with logging, you may find that you log a lot of unneeded information, and can’t find what you are looking for because of the volume of things being logged.
Do we need different log destinations, or are keywords enough to assist in separation of data? We can always use RegEx to filter the log entries if everything is written to a single source.
In a cloud environment where your applications may run on one or more machines, how do you implement logging in a centralized form?
Share your insight or experience in this area by leaving comments below, or send me an email at btaylor@sswug.org.
Cheers,
Ben
$$SWYNK$$
Featured Article(s)
Learning SSAS: Part V – Creating Dimensions
In this article I show how to create new dimensions for your cubes. I also talk about some important properties that you should know when you are dealing with dimensions.
Featured White Paper(s)
How to Use SQL Server’s Extended Events and Notifications to Proactively Resolve Performance Issues
read more)
Featured Script
admin db – Index (fragmentation) Maintenance for Log Shipping
Keep your indexes in good shape with minimal blocking. Track table fragmentation and prevent maintenance from filling your lo… (read more)