The Audit Flags operate independently of the currently set Audit level. Each flag relates to a particular area of functionality in the application and when set, will generate a large volume of information about that specific area.
This allows an in depth analysis of specific problems whereas audit levels provide a more general level of information about the application as a whole.
Tip: Audit Flags should be used sparingly since they can generate large volumes of auditing. Typically they should only be used when requested be Jemmac during problem analysis.
|
Audit Flag: |
Description: |
|
B |
Logs which 'buckets' are being used to fulfil a data request from a Sapphire Client. |
|
C |
General data collection progress (and collection, not just OPC). |
|
D |
Shows the individual value and quality field for each OPC data item read. |
|
E |
All logic relating to exporting (scheduling as well as export definition creation). |
|
F |
General operation on SDPs. |
|
G |
String table audit messages (used to store Annotations). |
|
I |
Shows each Network API call made (including parameters). |
|
L |
Internal lock Activities. |
|
M |
Shows details of memory mapping logic. |
|
O |
Generates logging of all OPC calls without providing details at the individual item level. |
|
P |
Audit messages specific to Plug-in Data Sources. |
|
R |
Provides general output relating to item resolution. |
|
S |
Log all security operations (Users, Roles, Addresses etc). |
|
V |
Messages related to Archiving. |
|
Z |
Used to determine the number of references to items in the Collectors memory (verbose). |