Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:logginevent [2007/10/11 09:12] ravith |
dev:logginevent [2009/07/06 20:36] (current) |
||
---|---|---|---|
Line 43: | Line 43: | ||
* **FATAL** | * **FATAL** | ||
- | **__//'' | + | **__//'' |
The log level defaults to **INFO**. \\ | The log level defaults to **INFO**. \\ | ||
Line 58: | Line 58: | ||
* **UNCLASSIFIED** | * **UNCLASSIFIED** | ||
- | **__//'' | + | **__//'' |
The senisitvity level defaults to **NOT_SENSITIVE** \\ | The senisitvity level defaults to **NOT_SENSITIVE** \\ | ||
Line 85: | Line 85: | ||
**//'' | **//'' | ||
- | The default method of logging (to file or to database) can be configured in the sysconf.inc under $conf[' | + | The default method of logging (to file or to database) can be configured in the sysconf.inc under $conf[' |
A custom logger can be created by extending the class Logger and overriding the log_message() function. | A custom logger can be created by extending the class Logger and overriding the log_message() function. | ||
Line 102: | Line 102: | ||
</ | </ | ||
+ | **//'' | ||
+ | The logging API **MUST** be used in the following and similar instances, additionally the module developer is free to use it else where.\\ | ||
+ | \\ | ||
+ | * When a write commit is made to the database | ||
+ | * On a configuration change | ||
+ | * On a important event in the business logic of the module | ||
+ | * On an error | ||
+ | * On a security violation or suspicious action | ||
+ | The log messages should be recorded with the appropriate logging level, and sensitivity level, to make event audit more efficient. | ||
\\ | \\ | ||
**//'' | **//'' | ||
//Ravith Botejue.// | //Ravith Botejue.// |