PI AF Audit Trail: Option to exclude certain (tchnical interface) users from being audited
PI AF Audit Trail: Option to exclude certain (technical interface) users from being audited
Currently the only option for AF Server is to activate or disable audit trail. In our scenario most data is written by interfaces via SDK Calls. This leads to a very large audit trail and to 99% Audit Trail data that is not required (hard to find the human entries).
It would be helpful if a list of users could be configured that will not be audited.
Having a mor configuable Audit Trail (for both Data Archive and AF) wold definitely be an benefit.
But due to the comment from Jake there is a performance issue with audit trail in AF? Or might be an issue under certain circumstances?
Having a mor configuable Audit Trail (for both Data Archive and AF) wold definitely be an benefit.
But due to the comment from Jake there is a performance issue with audit trail in AF? Or might be an issue under certain circumstances?
Noticed this is marked as 'completed' but first creating the Audit Trails, and next removing them is an unneccesary load on the SQLserver. I just struggled with a SQLserver that nearly collapsed under a huge cleanup of the Audit trail.
In response to Roger Palmen, "Noticed this is marked as 'completed' bu..."
Since this is implemented using built-in SQL change data capture (CDC), there is not a way change what is being added to the Audit Trail tables initially. SQL CDC is a very efficient mechanism for capturing changed data in SQL.
