|
Dear Sir,
We've been looking at log4plsql for
possible use as a standard database logging tool within our organization. We
currently have a standard package that we employ, but often find we have to
customize it for our different applications. Log4plsql would appear to address
a lot of our needs, with one major exception: our database application logging
usually employs explicit columns for key value storage; allowing us to join
directly in sql from our logging table(s) to staging/load tables etc. The
query-ability of these data attributes is crucial to us. Having to parse
TLOG.LTEXTE for significant values (e.g. keys, parameter values etc.) would be
quite onerous.
If I were to customize Log4plsql, I'd
consider perhaps another table to store some sort of template for the contents
of TLOG.LTEXTE (alternatively add an additional column instead) to accommodate
named attributes and a format (xml would be ideal for this). I'd also consider
creating an api for converting parameters into the template format, for use
prior to calling plog.error/fatal etc.
You may already have considered this, or
perhaps someone has already suggested it. Might this be something that someone
is already working on? Should we endeavor to create this extension ourselves?
Your thoughts and comments would be very welcome.
Very best regards,
Ashton
|
