When Citect Interface loses connection to a device, throttle errors relating to failed tag reads

OSI PI Citect Interface The interface will log an entry to the message log for every tag that it can't source data for. This is fine for a small number of tags that have not been able to read data from Citect. However, when a Citect Unit (eg PLC) goes offline and there are thousands of tags assigned to that unit, every single tag that is scanned is logged with the same message generating thousands and at times hundreds of thousands of log entries in a short time frame, eg every second. This results in a very, very large log file and can eventually fill up the disk space. It would be preferable to have a single, summary log entry indicating the unit is offline. Alternatively, only log the first instance that it can't source the data for the tag and ignore subsequent failed reads.