Monitoring Connector health

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?

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.

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)

Great Idea, it should be very useful for automatic alerting once combined with PI Notifications functionalities

It's a must for us

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.

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

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.

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.

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.

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)

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.

Including "estimated buffer capacity (time)"

Deal breaker for mission critical processes

Include Tao Buffering monitoring as well similar to PIbufSS counters.

Absolutely a feature that should have been there from day 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. +1

Definitely a need. The work-around of auto-running a powershell script could be a cyberSec vulnerability if the script is replaced / altered.

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.