Implement control on database logging (.lg) verbosity and type of events to include/exclude? - OpenEdge Database - Products Enhancements - Progress Community

 OpenEdge Database

What new features or enhancements could improve the OpenEdge Database? Use this challenge to let the OpenEdge team know what would make your life easier by reducing costs and increasing productivity!

Implement control on database logging (.lg) verbosity and type of events to include/exclude?

  • Under Review

Implement setting on the database side to control the verbosity of the logging and to be able to exclude some types of log events. In our case the database .lg file gets flooded with:

P-2359410    T-1     I ABL     7: (7129)  Usr 7 set name to batch@xxxx.com.
P-2359410    T-1     I ABL     7: (15914) Usr 7 set tenant-id to 1, tenant-name to xxxx
P-2359410    T-1     I ABL     7: (7129)  Usr 7 set name to batch@xxxx.com.
P-2359410    T-1     I ABL     7: (15914) Usr 7 set tenant-id to 2, tenant-name to oooo
P-2359410    T-1     I ABL     7: (7129)  Usr 7 set name to batch@oooo.com.

Making it very hard to troubleshoot real issues when the log files are flooded with events that we wish to exclude.

The log control we have on the AppServers via ubroker.properties is excellent, can we get something like this for the database engine?

Status update

We are actively researching and determining how best to address this scenario and several other database log challenges.  We may implement logging levels in the database or provide alternative mechanisms to be able to better manage the messages that are generated in the database log.  The direction is still TBD.

Comments
  • It would be great to give us some way to suppress things like 7129 (Usr set name to), 452 (Log in), and 453 (log out) messages especially if we do our own application auditing or Progress Auditing.  These entries are getting in the way of debugging real errors.  We have to truncate the log files also which also removes real errors.

  • It would be great if the DB log could be set to rollover or switch to new log files just like the appserver logs.