Reason #1
In production, I create an agent that monitors the error table and notifies me via e-mail once an error occurs. If you are monitoring multiple sites, this can be extremely handy and useful. The detailed error information allows me to get to the root of the problem quickly.
Reason #2
The typical development staff usually has one or two master gurus monitoring several junior code warriors. The average day is usually spent helping them track-down simple coding errors. Well, what if you could give them a way to trace down the errors without bugging you every 30 minutes? This would definitely increase productivity within the development shack. The error.asp contains all the ASP error codes as well as a detailed description for each error. This page can be routinely updated to display fixes and things to try before running to the master gurus.
Reason #3
As a manager it is important to monitor the effectiveness of your staff. By logging errors you can track common mistakes and address them with a training class.
Reason #4
When you have 6 to 12 web developers it is a lot easier to query a table for information, than trying to drain it out of the new hire or freshly minted consultant. Besides, it really scares them when you call their extension and tell them the answer to the question that they were getting ready to ask you =).
Comments