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.

Add a new idea Subscribe
Status Completed
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Audit Trail Scope

I am unable to implement Audit Trail due to the performance implications associated with auditing my entire server. Being able to audit very specific attributes, elements, or trees would allow me to take advantage of the Audit Trail feature in a practical way. I want the ability to audit attribute changes with the following details: * old value * new value * timestamp * user
  • ADMIN RESPONSE
    Aug 19, 2022
    We have implemented additional filtering capability in the AF Audit Trail in recent releases. Please have a look and let us know if it's sufficient for your needs. Regarding AF Audit Trail for individual databases, we currently do not have any plans to implement that idea.
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    The auditing feature in the AF Server is implemented with SQL Server Changed Data Capture (CDC), which is designed to capture all changes. With this implementation, there's not a good way to only capture changes to specific attributes, elements or trees. In addition, an element spans multiple tables so that adds more complexity.
  • Guest
    Reply
    |     Aug 19, 2022
    I ran into similar issues (space usage) using the audit trail. I also would like to limit the scope, but i would be helped quite much if i could limit the audit trail to one or more AF databases. And if the CDC does not support the limitations, you can also create the Audit Trail and then prune the Audit Trail for the unwanted entries. Less then ideal i agree, but that would be a stop-gap approach.