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.
We understand and acknowledge the importance of this request. We are evaluating how to provide a homogeneous and unified experience for health information across all our connectors.
Must have ASAP please.
This is a must have. We really need this for ongoing system monitoring.
Very important feature
Yes, its really needed for monitoring PI Connector's health.
Absolut Must-Have for supporting uninterrupted data collection in GxP environment!
really needed for us!!
Because of the criticality of this feature, fast-tracking of the development would be of very helpful.
Absolutly neccessary for relaiability and transparency.
Absolutely a feature that should have been there from day 1. How OSISoft could release PI Connectors to production without proper monitoring capabilities!
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.
Definitely a need. The work-around of auto-running a powershell script could be a cyberSec vulnerability if the script is replaced / altered.
Absolutely a feature that should have been there from day 1. +1
I think monitoring connector health very need to know stabilize connecting include feature
Absolutely a feature that should have been there from day 1.
Include Tao Buffering monitoring as well similar to PIbufSS counters.
Deal breaker for mission critical processes
Danny Dijke (AG Solution) commented
Including "estimated buffer capacity (time)"
Gabriel Michaud-Verreault commented
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.
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)