Device Audit Logs

In accordance with recent additions to the BACnet protocol, the Desigo BACnet implementation now provides for an on-device audit log. These logs can be used to record a range of system activities, including (but not limited to) updates related to commanding, time of event, backups, restores, and configuration.

Values recorded by audit logging include

• Time of change
• Object
• Property
• Value before and after the change
• User ID responsible for change
• Comment field

Audit log entries are stored in an Audit Log Object on each device, analogous to the way trend samples are stored on-device within a Trend Log Object. However, audit logs do not support the trend log “buffer full” mechanism. You must manually select the method of data collection. Data can be collected at least two ways:

1. The collect button on an audit log object
2. Macros for periodic collection

Note that the size of audit logs may become large over time. If you enable audit logging, be sure your device has sufficient storage.

Audit log entries can be viewed two ways:

1. In the BACnet Object Browser
2. In the Activity Log

The BACnet Object Browser can also configure Audit Reporter objects. These are used to configure which objects and operations have their data collected for the Audit Log Object.

If you wish to activate audit logs, be sure they are supported by your device.

For additional information on BACnet audit logging, see ASHRAE addendum "bi" to BACnet standard 135-2016 (Approved June 15, 2018).