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.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Notifications
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Notification when message sent to Delivery Endpoint is rejected

When a notification is sent to a delivery endpoint (web service) and the message is rejected, no failure notification is shown within PSE.  In order to track this issue I currently have to sift through the log files looking for exceptions such as this: Exception: System.Web.Services.Protocols.SoapException: Internal Error EventFrameId=8286c3f8-1241-11e9-80df-005056b06dd7, EventFrameName=Meter Value Change Detected 2019-01-07 01:00:00.000, NotificationId=4ab639dd-5241-43ca-a205-05226d1559b2, NotificationName=Maximo Web Service, EngineOperation=EventFrameChange I then have to turn on advanced logging via the Notifications.UserNLog.config file and then go back to my log file to see which analysis/notification is throwing the error. As with Analyses, can I get some way to know if notifications to an endpoint are in error?
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Since PI System Explorer is not a real time client, i.e. you need to refresh it to get updates, it's really not a good place to provide this information, especially if the problem is transient in nature. For example, if the notification is rejected by the end point unexpectedly once in a while, I would not expect users to sit in front of PI System Explorer and continuously hit Refresh to catch this information. What's the best way to expose this information for it to be useful?
  • Guest
    Reply
    |     Aug 20, 2022
    In response to Stephen Kwan, "Since PI System Explorer is not a real t..." In this instance we are not using it as a real time client.  Instead, it's being used as an integration point between PI Archives and our Maintenance system.  Tags are polled or monitored for change, analyses are run and a message is passed on to a web service end point.    For monitoring of our analyses we are using a tag that is available for this: _PI Analysis Service_Analyses in Error   I think that we might be able to use a last 15 minute sampling of  _PI Notification Service_Failed Sends to at least get some visibility for this.  We'll still need to enable advanced logging to see the values being sent to our web service end point.  It would be nice if we could have messages that cause exceptions be dumped into another log file.  With over 5000 successful notifications being sent daily and the notifications log file overwriting itself, this would be helpful to me.