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 Completed
Product AVEVA™ PI System Access (PSA)
Categories PI Web API
Created by Guest
Created on Aug 23, 2022

RELATED IDEAS

Add Options for PI Web API Call Statistics

Add auditing or a view of statistics for the calls or requests done by each individual application. Allow a PI Admin to see which user or application is making a specific call and see how long it takes to complete to monitor performance and potentially resource intensive Web API calls.
  • ADMIN RESPONSE
    Aug 23, 2022
    This has been completed as a part of the PI Web API 2021 release
  • Attach files
  • Guest
    Reply
    |     Aug 23, 2022
    Could you also add failed requests counters?
  • pspeybro
    Reply
    |     Aug 23, 2022
    Also some general performance counters like requests per second (or minute), response time, ... to get an idea how intensively the api is called.
  • Guest
    Reply
    |     Aug 23, 2022
    Right now we are trying to find some problems with our current WebAPI 2017R2 and without these it's been pretty hard. I can get some of the values looking at the Debug/Audit logs, but it takes a lot of time. Things like Average response time, Number of calls per second/minute, total number of calls, failed requests, maybe a different counter for each different type of call (POST, GET, BATCH, etc).
  • Guest
    Reply
    |     Aug 23, 2022
    We'd like to know when clients are not able to connect or are getting timeouts on their queries. See Case 885702. The particular event of May 30 which prompted the case is a situation we want to be on top of - we want proactive intelligence of when it is happening instead of having a customer report the issue
  • Guest
    Reply
    |     Aug 23, 2022
    We're having ongoing stack overflow memory leaks with WebAPI 2017R2. Desperate for more stats to alert us ahead of frustrated user calls.
  • peheuvel
    Reply
    |     Aug 23, 2022
    Dear Kevin, This request is now open for almost 4 years. Last august you informed that the development on this has been started. Any progess? Peter
  • alviserossi
    Reply
    |     Aug 23, 2022
    In light of Peter's comment, I just wanted to point out that we have also been waiting a long time for this new feature to be released - when the feature was switched to the "in development" state we even stopped our efforts on a custom development of some scripts to have statistics on WEB API usage on our own. Alvise
  • Guest
    Reply
    |     Aug 23, 2022
    The current status has not changed. We are still working on implementing this feature, and it will be available in the next feature release.
  • peheuvel
    Reply
    |     Aug 23, 2022
    What is the planned delivery date of the next feature release? and are you able to give a preview how this will look like in that release?
  • peheuvel
    Reply
    |     Aug 23, 2022
    Kevin - a missed opportunity is that OSIsoft/Aveva has not connected with us what we expect from performance parameters. Can you share a whitepaper how we can see which user/application is consuming wich amount of data from which server. I suppose this data can be published in PowerBI.