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 No status
Product PI Integrators
Created by Guest
Created on Aug 16, 2022

Provide more detailed error logging

Error message logs sometimes are not detailed enough to properly troubleshoot. The customer would like to increase logging available in order to get more insight as to what is going on. One example - the PI Integrator for BA does not publish any message when there is a permissions/access issue to output data to a Kafka Topic.
  • Attach files
  • Guy Acciai
    Reply
    |
    Aug 16, 2022
    Very much agree - and this can be in the Target setup stage, I'm fighting a similar issue with AWS Kensis - Basically just getting a "failed to connect to stream" message, versus details about what calls where attempted in the AWS SDK, and more importantly, any return status/error codes.
  • Guest
    Reply
    |
    Aug 16, 2022
    Agree. PI Vision has got a generic "Internal Server Error" which is not detailed enough to troubleshoot. In most of the situations, where "Internal Server Error" occurs, the message logs do not lead to the root cause of the issue and we can not make improvements towards resolving those problems. If we can have more granular message logs popping up, that would help guiding improvements in the system.
  • Lebretonp
    Reply
    |
    Aug 16, 2022
    very important topic to manage the quality and the rejects on the target. We have one case, where some rows were in error and no log provide to you which one rejected. Only way is to compare the source and the target (huge job to figure out the rejected rows)