Comments on: Logging – The Smart Way http://www.udidahan.com/2008/08/01/logging-the-smart-way/ Enterprise Development Expert & SOA Specialist Sun, 14 Mar 2010 06:27:00 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Logging Best Practices « Niraj Bhatt – Architect’s Blog http://www.udidahan.com/2008/08/01/logging-the-smart-way/comment-page-1/#comment-36452 Logging Best Practices « Niraj Bhatt – Architect’s Blog Wed, 22 Jul 2009 05:45:56 +0000 http://www.udidahan.com/2008/08/01/logging-the-smart-way/#comment-36452 [...] Also I would recommend that exceptions are also posted in the Event Logs (you can create a category for your application), the motivation being that this increases visibility & is easy for admins to locate them instead of wading through your text, Udi organizes the same thought here. [...] [...] Also I would recommend that exceptions are also posted in the Event Logs (you can create a category for your application), the motivation being that this increases visibility & is easy for admins to locate them instead of wading through your text, Udi organizes the same thought here. [...]

]]> By: udidahan http://www.udidahan.com/2008/08/01/logging-the-smart-way/comment-page-1/#comment-28709 udidahan Mon, 04 Aug 2008 09:25:13 +0000 http://www.udidahan.com/2008/08/01/logging-the-smart-way/#comment-28709 raveman, I'm not exactly sure of your question/point - while the table structure may be stable, the existence of a specific row can definitely change. I agree that having that kind of method level logging is valuable at times (like when the developer is working on their machine), and I think that AOP/framework level logging is a fine way of going about it. raveman,

I’m not exactly sure of your question/point – while the table structure may be stable, the existence of a specific row can definitely change.

I agree that having that kind of method level logging is valuable at times (like when the developer is working on their machine), and I think that AOP/framework level logging is a fine way of going about it.

]]> By: udidahan http://www.udidahan.com/2008/08/01/logging-the-smart-way/comment-page-1/#comment-28706 udidahan Mon, 04 Aug 2008 08:23:18 +0000 http://www.udidahan.com/2008/08/01/logging-the-smart-way/#comment-28706 Sneal, absolutely :) Sneal, absolutely :)

]]> By: raveman http://www.udidahan.com/2008/08/01/logging-the-smart-way/comment-page-1/#comment-28609 raveman Fri, 01 Aug 2008 22:39:46 +0000 http://www.udidahan.com/2008/08/01/logging-the-smart-way/#comment-28609 nice idea with “I know the entity isn’t in the database. I can see that. I want to know why it isn’t there.” Because datebase is stable and it doesnt change. when you add entity, it can never be deleted by other users/threads. maybe you meant when you use logging as debug tool. sometimes its important to know if bug happened when entity was or wasnt in the db. sometimes its nice to have input and output of method that does not behave like it should once every month. nice idea with
“I know the entity isn’t in the database. I can see that. I want to know why it isn’t there.”
Because datebase is stable and it doesnt change. when you add entity, it can never be deleted by other users/threads. maybe you meant when you use logging as debug tool.
sometimes its important to know if bug happened when entity was or wasnt in the db. sometimes its nice to have input and output of method that does not behave like it should once every month.

]]> By: Sneal http://www.udidahan.com/2008/08/01/logging-the-smart-way/comment-page-1/#comment-28595 Sneal Fri, 01 Aug 2008 14:39:40 +0000 http://www.udidahan.com/2008/08/01/logging-the-smart-way/#comment-28595 ...And read Release It! …And read Release It!

]]>