Track if auditing was turned off

I hope that after several years of this request, AVEVA will add improvements to this feature. This came up recently with a pharma customer during system acceptance testing and raised some eyebrows that this wasn't already a feature.

Request would be to have all Tuning Parameters audit-able. They should be tracked in the same format that changes to the Archive data or Database Security, etc are. They should be available to view and search/report on via PI AuditViewer just like the rest; no new tools to learn would be preferable. Customer wants to be able to track for x Tuning Parameter (here especially where x=EnableAudit) what is the value before and after a change, when was it changed, and by whom.

And importantly, if this parameter changes such that auditing will from then on be disabled for all or some subsystems, that change should be entered into the audit trail files prior to the end of the auditing/audit trail so there's at least a record of when auditing was disabled.

for GMP sites we must need this feature along with username and time

This is a desired feature especially while working in a GMP environment and a PI System that is also used for GxP.

Yes maintaining a history of all changes to this flag is critical. Without this there is potential that someone could turn off auditing, make changes to the system without generating any records and enable auditing again. A message in a log file is acceptable so long as it can be easily found during audit trail review. The first step of our typical audit review process is to confirm that auditing is enabled and has not been turned off since the time of last audit.

Changes to auditing in the AF Server are recorded in the Windows System Event Log along with the user who made the change. Is this the type of tracking you are looking for or are you wanting something in addition to this?

In response to David Hearn, "Changes to auditing in the AF Server are..." We are more concerned with changes in the PI Data Archive at this time. We set the 'EnableAudit' tuning parameter to -1 on all our systems which means all changes made by administrators are logged. Currently an admin could change this setting to 0 which would disable auditing and then freely change other settings in the system without maintaining a history.

I have another customer wanting changes to the enableAudit parameter logged by auditing. Note: I believe this used to be tracked as PLI 9591osi8 but this is hard to find and has status: "removed".

Hello, has there been any progress on this item? We are also needing a method to detect if the Audit Trail was turned off or a way to prevent admins from turning it off. Thank you!

I want to track this information by a message in the Audit Trail Viewer Application. it should be immediately visible (e.g. in red font) if in the searched time-range the audit trail was switched of (include the information when it was switched off/on and from whom).

I absolutely agree it should be done somehow!

I would like to be able to automatically detect when the OSI PI Data Archive Audit Trail is turned off. The Audit Trail is a tuning parameter, these tuning parameters should be able to be internal PI Tags where I can add Asset Framework configurations to trigger notifications. This is an absolute must for Pharmaceuticals and regulated industries.

To answer the question posed by the product manager -- it should be in the audit trail viewer and captured as a configuration change. Keeping it in the logs would be too cumbersome since they are removed after 30 days.