The Audit Trail feature records events generated either by user actions or system activity. Examples of user actions include logging in to the Site Management Portal UI or issuing commands to a point. Examples of system activity include device restart initialization settings or internal security changes. An audit message consists of the information that describes a significant event on the building automation system (BAS). For each significant event, a new audit message is generated and appears in the Audit Viewer.
Once an event is sent to the Audit Trails subsystem, an audit message is generated and stored in an Audit Repository file located on the server or engine that detected the condition.
You can forward audit messages from the Local Audit Repository to a user-specified ADS Audit Repository for permanent storage on a server (ADS/ADX), based on user-defined rules.
You can view audits in the System Activity feature in Metasys UI. System Activity is a system-level audit log that provides a time line view of all audits that have occurred across an enterprise.
You can also view audit messages in the Audit Viewer of the SMP UI. When you log in to the Site Director, you can view all audit messages from the server or any device that contains a Local Audit Repository. When you directly log into a device not designated as the Site Director, you can only view audit messages in that device’s Local Audit Repository. Any audit messages generated on a server are placed directly into the ADS/ADX Audit Repository.
You can also view user changes made within the last seven days for a selected piece of equipment in the Equipment Activity widget of the Metasys UI. You can also discard user changes in this widget.