An often overlooked functionality when writing Oracle database code is instrumentation. With instrumentation it is possible to see after the production code has been executed which codepath was taken and which arguments are passed along. Instrumentation is, unfortunately, not used very often and missed when an application goes into production. Writing your own instrumentation code starts easy, but quickly extra features are requested to expand the functionality. A popular framework called Logger, actively maintained on GitHub, which offers a lot of features out of the box.

This session will introduce instrumentation to the delegates, as well as show various aspects of Logger and LoggerUtil to increase the uptake of using instrumentation.