Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our 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 Tell us more
Product PI Integrators
Created by Guest
Created on Aug 16, 2022

Specify desired logging level

As a PII4BA administrator I would like to specify a logging level so I can filter which logs I want to store and which ones I don't want to store in the database.
  • ADMIN RESPONSE
    Aug 16, 2022
    Is this an issue of limited SQL storage? We have a log retention policy that can be configured by the user in the CAST.UI.WindowsService.exe CONFIG file today. By default it only retains a maximum of 2 months of data AND no more than 100k rows AND no more than 1000MB of disk space. Similar retention policies can be created for the PIIntegratorStats database as well. Let me know if this would satisfy the requirement. Or provide more information on how specifying the logging level would help. If you could, which logging levels would you keep vs. throw away and why?
  • Attach files
  • Guest
    Reply
    |
    Aug 16, 2022
    Is this an issue of limited SQL storage? We have a log retention policy that can be configured by the user in the CAST.UI.WindowsService.exe CONFIG file today. By default it only retains a maximum of 2 months of data AND no more than 100k rows AND no more than 1000MB of disk space. Similar retention policies can be created for the PIIntegratorStats database as well. Let me know if this would satisfy the requirement. Or provide more information on how specifying the logging level would help. If you could, which logging levels would you keep vs. throw away and why?