Perspective Sessions generate entries in an assigned audit profile. The following actions are recorded in the Audit Profile:
The Vision project needs an audit profile configured and auditing enabled. Vision Clients will then log records to an assigned audit profile. Here is a list of audit actions that will be tracked in the Ignition auditing system:
The following Tag related actions generate entries in the audit log. Note that the functions below must originate from the Tag Browser, the Designer's Scripting Console, or Vision component-based scripts.
Write requests sent from a tag either through a standard Tag Binding, Indirect Tag Binding, or manual entry from the Tag Browser.
The system explicitly captures modifications made to database tables through the following methods:
The following functions generate entries in the audit log if called from Vision component-based scripts, or from the Designer's Scripting Console.
If the project opened in the Designer has an assigned Audit Profile, then changes made to database tables using the database query browser are automatically recorded to the audit log. "Changes" in this case refer to UPDATE, DELETE, or INSERT statements manually typed and executed from the database query browser.
Enabling edit mode and applying changes, including typing in new values, adding rows, removing rows, and clearing out fields, are recorded as queries called from the project.
Attempts to send out alarm notifications are recorded in the auditing system. Specifically, the Gateway will record when it attempted to send out a notification, as well as if the attempt failed (such as the SMTP server refusing the request). It is important to note that the auditing system can not report failures that occur outside of the Gateway. Thus, if a voice notification fails to send due to some error in the VOIP system, it's possible that the Gateway won't report the VOIP error, but the audit log will have an entry stating that the Gateway attempted to send the notification.
Reporting Module Reports generate an entry in the auditing system when a report is executed. Thus:
The following table describes the audit table as it exist in the database:
|AUDIT_EVENTS_ID||The id of the row.|
|ACTION||Brief description of the action.|
|ACTION_TARGET||The target of the action.|
|ACTION_VALUE||The value acted upon the action target.|
|ACTOR||The logged in user when the action occurred or a description of the system that generated the action.|
|ACTOR_HOST||The host computer where the action occurred.|
|EVENT_TIMESTAMP||The time when the action occurred.|
|ORIGINATING_CONTEXT||A numerical description of the origin of the originating system. gateway = 1, designer = 2, client = 4|
|ORIGINATING_SYSTEM||The name of the project or system where this action occurred.|
|STATUS_CODE||The quality code where (where applicable). 192 signifies success. 0 signifies bad or failure.|