Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status Completed
Created by Guest
Created on Aug 19, 2022

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.
  • ADMIN RESPONSE
    Aug 19, 2022
    PI Server 2018 has been released.
  • Attach files
  • Guest
    Reply
    |
    Aug 19, 2022
    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?
  • Guest
    Reply
    |
    Aug 19, 2022
    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?
  • Guest
    Reply
    |
    Aug 19, 2022
    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.
  • Guest
    Reply
    |
    Aug 19, 2022
    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.