Modules/Log implements the basic functionality needed to create an application log - this module is in use, practically as-is, in some of our projects, but you could of course modify it as needed.
The module is meant to be incorporated into your application by adding the Log system & view to your application, to be used by the application administrator. The modeler should then reuse Log/Reusable Models/Add Log Entry in the application models, wherever it is deemed necessary to make a log entry.
Logging a DB event, such as a certain table becoming full, would require you to model a process which checks whether the table is full, and if so call Add Log Entry with the details. This process can then be executed periodically using a Miscellaneous/Timer, placed in the application root system (which starts as soon as the application is started in the server).This is of course just one of many possible implementation. You could use other strategies to incorporate DB monitoring into the log (depending on specific database capabilities), such as having the database itself call a Basic/Callable Service which exposes Add Log Entry, or catching error exception on any of the relevant Database palette category calls, and analyzing the returned error.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
