Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

206 VOTE
Status Declined
Product PI Connectors
Categories General
Created by Guest
Created on Aug 20, 2022

Monitoring Connector health

Support for health tags (similar to UniInt health tags), Windows performance counters, or any other way to bring Connector status and health information into PI tags to put them side-by-side with Interface health monitoring.
  • ADMIN RESPONSE
    Aug 20, 2022
    Thank you for your input. While we are declining to add health monitoring for PI Connectors, we will include health data for PI Adapters. We encourage you to go to the PI Adapters forum to share your use cases.
  • Attach files
  • Brent Bregenzer
    Reply
    |
    Oct 17, 2022

    Edit to my previous post: there is also PI Connector Relay API that would allow capturing some metrics on a per connector basis. Could this also be documented?

  • Brent Bregenzer
    Reply
    |
    Oct 17, 2022

    Following up on what Gabriel commented earlier: there is a REST API used for communications by Connectors. An example of using the REST endpoint is given in the blog Gabriel linked. Currently, this API is undocumented so there is no support for its usage. Since the stated response is that any new health monitoring improvements will go toward Adapters, could the Connector API at least be documented so customers and partners would have a supported way of developing their own custom monitoring solutions? If you support this and would like to implement your own custom monitoring solution for Connectors using the API, please comment and upvote.

  • Guest
    Reply
    |
    Aug 20, 2022
    I would also like to see a counter like the IO Rates. This is crucial to our daily monitor while collecting data. I have seen too many times that tags get in stored-forward state, which basically stop collecting data for those particular tag. (PI-Connector for Wonderware)
  • Mirko Bani
    Reply
    |
    Aug 20, 2022
    Great Idea, it should be very useful for automatic alerting once combined with PI Notifications functionalities
  • marcogiunti
    Reply
    |
    Aug 20, 2022
    It's a must for us
  • Guest
    Reply
    |
    Aug 20, 2022
    in UFL connector, it should be great if we have an option to easily configure tags to have latest file timestamp for each data souce and also list of tags created by the connector.
  • Gabriel Verreault
    Reply
    |
    Aug 20, 2022
    Although very basic in term of the health statuses that can be picked up, Nathan shared a clever way to monitor the webpage statuses with PowerShell and AFSDK: https://pisquare.osisoft.com/community/all-things-pi/blog/2017/03/27/monitoring-the-health-of-your-pi-connectors-with-powershell-and-af-sdk
  • Guest
    Reply
    |
    Aug 20, 2022
    For UFL connector it is able to have multiple streams for a single service that can be controlled independently of the service. Health tags to monitor such streams would also be fabulous.
  • Guest
    Reply
    |
    Aug 20, 2022
    Would be nice to have several sets of same type of health tags, each set monitoring a particular data flow within the connector itself. We need to know when there are issues with a specific data flow, not just issues with the connector.
  • Michael Kreideweis
    Reply
    |
    Aug 20, 2022
    We'd also need health tags for the UFL connector. We monitor the interface-health by checking IO-rates and heartbeats in PI AF and Notifications.
  • Guest
    Reply
    |
    Aug 20, 2022
    I would like to have information's like Number of files processed and Number of Events processed, preferable in the Perfmon to be able to get it using the Perfmon interface (similar to what we have in PI Analysis)
  • Gabriel Verreault
    Reply
    |
    Aug 20, 2022
    IO rates (data source specific), heartbeat, and Device status (data source specific) would be the minimum acceptable to be able to monitor a connector. The same should also be applied to the relay for relay-enabled connectors.
  • Danny Dijke
    Reply
    |
    Aug 20, 2022
    Including "estimated buffer capacity (time)"
  • Guest
    Reply
    |
    Aug 20, 2022
    Deal breaker for mission critical processes
  • Guest
    Reply
    |
    Aug 20, 2022
    Include Tao Buffering monitoring as well similar to PIbufSS counters.
  • Guest
    Reply
    |
    Aug 20, 2022
    Absolutely a feature that should have been there from day 1.
  • Guest
    Reply
    |
    Aug 20, 2022
    I think monitoring connector health very need to know stabilize connecting include feature
  • Fred_EYRAUD
    Reply
    |
    Aug 20, 2022
    Absolutely a feature that should have been there from day 1. +1
  • sahilp
    Reply
    |
    Aug 20, 2022
    Definitely a need. The work-around of auto-running a powershell script could be a cyberSec vulnerability if the script is replaced / altered.
  • phsutterRoche
    Reply
    |
    Aug 20, 2022
    We need this urgently. Right now we can monitor that the service is running, but not if it does anything useful. BTW the situation is the same with the Connector Relay.
  • Load older comments
  • +106