Geeks With Blogs
Saqib Ullah BootStrapper Know How
Logging is one the important part of any small or big application and selecting the right logging option is very crucial and the decision is made on the basis of logging time response (if you are working on the real time application like my CRM, Stock application), cost of logging implementation and in last at which level of logging you want in your application is very important. Yesterday I found a very interesting comparison between different available logging options; I felt I should share it with you guys.
 
Options
Positive Points
Negative Points
Event log
High-level application events (for example start and stop)
Limited in number of events
Performance counters
Use when you have rollup summary information (number of active users) or absolute (simple) values you want to measure (total requests)
Not suitable for complex data
Debug output
Single user code pathing and debugging
Overwhelming if used everywhere
SEH
Good for unexpected exceptions
Can bend your design
System.Diagnostics.Trace
Easy to use
Limited to Web apps
ASP.NET trace
Great for debugging
Fixed functionality
WMI
Widely supported, complementary to other schemes (for example, your event log code can be surfaced through WMI)
More complex to use and install applications with
EIF
Easier to program than WMI
Doesn't expose all of WMI's power
LAB
Common requirements provided: MSMQ logging, DBMS logging
A lot to learn
 
Posted on Wednesday, December 12, 2007 5:23 PM .Net , General , Security | Back to top


Comments on this post: Available Logging Options

# re: Available Logging Options
Requesting Gravatar...
o yarra ...... use "log4net" framework ...... zama da salor zaalim da framework dagha lorra.
Left by Ameen pathan (peon, Mixit Tech.) on May 29, 2014 5:14 AM

Your comment:
 (will show your gravatar)


Copyright © Saqib Ullah | Powered by: GeeksWithBlogs.net