Weekend Learning: Ways to instrument code

Have you ever had a situation where you wished code was instrumented?  Maybe a situation where you had no idea what the error was for a report when it crashed or what table/data was behind the error?  How about needing to get progress information into gv$session_longops?  Well Tim Hall of oracle-base.com fame wants you to instrument your code!  His article even has a few suggestions on how you can accomplish this feat, and I'll tell you that being in Support it is really critical that we plan to have as much information at hand at all times since when we have that .01% chance of encountering an issue we have the same amount of information as the 99.9% when it works right.