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 System Access (PSA)
Categories PI Web API
Created by Tyler Engelhardt
Created on Nov 28, 2023

RELATED IDEAS

Public PI Web API Endpoint (for health checks)

Currently, all endpoints of the PI Web API are access protected. When using the PI Web API with a load balancer (namely with managed load balancers from AWS/Azure), the health check endpoint for the servers must be configured to accept both 200 & 401 status codes as a healthy server. This is an improper way to configure the load balancer, but it's the only available option.


Most APIs have a public endpoint specifically for health checks, and it would be great if the PI Web API followed this pattern.

  • Attach files
  • Evan
    Reply
    |     Jun 3, 2024

    The Pi Web API already has an endpoint for this (.../piwebapi/system/status -> State). Unfortunately this endpoint is limited to Pi Web API Admin group members, which means any authenticated health checks need to be run with very high privilege. Most cloud load balancing services are unable to make authenticated health check calls anyways. Suggest adding a .../piwebapi/health endpoint that is unauthenticated and returns 1 or 0