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.
important to us.
we need to enable to ufl self-monitoring.
e.g.: able to parse info from device status or connector statistics (data flow):
We are able to parse data, but it breaks with API node restart.
see case 00761909 for more details.
Ignacio Aguirre commented
Connectors are black boxes for both customers and TechSupport engineers. The customer is unable to know the status of the connector. They just see many errors in the message logs but they are not sure which data source is affected or the exact root cause of the problems. The same for TS engineers.
In case interface is not able to connect to datasource tags had bad satus (I/O Timeout for example); tag from connector doesn't. They simply don't send data but without interruption.
Not having monitoring is the largest impedement to converting from interfaces to 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.