SPIN logging features were designed to withstand "semi-trusted" investigators who could potentially attempt to conceal unwarranted investigations (publications).
| Anchor | ||||
|---|---|---|---|---|
|
...
By default SPIN logs to a local memory resident database provided by the JDK called Derby.
You can override Derby and log to your own database (such as mysql) by providing a copy for your database provider:
TODO
- edit SqlMapConfig.properties
- edit LogEntrySqlMap.xml
- edit spin-ibatis-logentry-create.sql
| Anchor | ||||
|---|---|---|---|---|
|
...
Application Logging with Log4j
SPIN uses log4j to set the logging level (DEBUG, INFO, WARN, ERROR, FATAL) and set the output targets (FILE, CONSOLE).
...
DEBUG > INFO > WARN > ERROR >FATAL
Log4J also allows multiple appender types such as CONSOLE or FILE or even SMTP.
Defaults
By default, SPIN will use the log4j configuration file located in /opt/spin/main/conf
...
This lo4j configuration will log all WARN, ERROR, or FATAL level messages to Tomcat STDOUT.
Any SPIN messaging related classes will log at the INFO level, also to Tomcat STDOUT.