AF Health Points which monitor connections to data sources outside of PI. For example, a heartbeat or connection status tag which looks at all ODBC connections. Or a health point which looks for stale attributes within elements.
ADMIN RESPONSE
Aug 19, 2022
Please implement such health points with the Data Archive. We have no plans to implement this idea with AF.
This seems a bit broad and dependent on configuration. Since clients are the ones asking for info, are you saying that regardless of if a client is requesting info, the AF server should maintain some sort of connection with an external data source and periodically check the health of the connection? Would this be a Performance Counter that is tracked by table connection?
What does it mean to look for stale attributes within an element? Since the attribute is configured with a data reference, this seems to be a separate request to track the staleness of the underlying data. Even if timestamped and conceding the fact that they are all different data references, what is defined as stale in this scenario? Is this a user-defined mechanism, and is it at the attribute level? If so, you could use an Analysis to figure out the previous timestamp and do comparisons.
AFTables are only refreshed periodically, based on user configuration and data access. We do not keep a persistent connection to external tables nor do we periodically check the state of the connection.
Does the external table contain static values or do they change?
