|
|
Audit Log for QPR ScoreCard |
|
|
|
||
|
Audit Log for QPR ScoreCard |
|
|
|
|
Audit Log for QPR ScoreCard
|
|
|
Audit Log for QPR ScoreCard |
|
|
|
||
|
Audit Log for QPR ScoreCard |
|
|
|
|
|
|
||
All operations targeted at a QPR ScoreCard model can be recorded into a log file called "SCSAudit.txt" located in the folder that can be defined in the General tab of the Common settings section in the QPR Configuration Manager utility. To enable logging, launch QPR Configuration Manager, open QPR ScoreCard Server settings, open the General tab and check the Enable audit log checkbox.
The Structure of the Log File
When the audit trail writing is enabled, a session entry will be written into the log file. In each entry there is a header, event, and footer section.
Header Section
The header section starts the session, and it will be written into the log file when the ScoreCard Application Server is started. Header contains a time stamp, such as the following:
### Audit Trail logging started at 4.3.2003 17:44:55 ###
Event Section
When an operation (action) is committed to the ScoreCard Application Server (or a Database Management System), a corresponding event will be written into the log file to the event section. The following actions are recorded:
| • | manual input of a new value |
| • | manual change of a value |
| • | manual delete of a value |
| • | value inputted by a scheduled SQL import |
| • | value inputted by a SQL mass import |
| • | value inputted by an Olap import |
| • | value inputted by an Olap mass import |
| • | value changed by a scheduled SQL import |
| • | value changed by a SQL mass import |
| • | value changed by an Olap import |
| • | value changed by an Olap mass import |
Note |
Calculated values are not recorded. |
An entry (a record) in the event section contains the following data (fields) on action:
When the action was made?
| • | date: <mm>/<dd>/<yy> |
| • | time: <hh>:<mm>:<ss> |
Who made the action?
| • | login name: <user's login name> |
| • | user name: <user's real name> |
What was the target?
| • | name of the model: <model name> |
| • | scorecard symbol: <scorecard symbol> |
| • | name of the scorecard: <scorecard name> |
| • | element symbol: <element symbol> |
| • | name of the element: <element name> |
| • | series symbol: <series symbol> |
| • | name of the series: <series name> |
| • | name of the period: <period name> |
What kind of an action was made?
| • | type of an action: User | System <import name> |
| • | action: Value Change | Value Deletion |
Value after and before the action.
| • | previous value, formatted according to value's unit: <null> | <value> |
| • | current value, formatted according to value's unit: <null> | <value> |
| • | value's unit: <unit> |
Record's end mark is a line feed (LF+CR) and fields are separated with tabulators.
Footer Section
The footer section ends the session, and it will be written into the log file when the ScoreCard Application Server is shut down. Footer contains a time stamp, such as the following:
### Audit Trail logging stopped at 5.3.2003 17:44:55 ###
Warning |
Audit log file can become very large. |
