Static OMF Health Data
- Last UpdatedMar 04, 2025
- 2 minute read
During the very first start-up of the interface, the AF element hierarchy is created. Here is an example of the PI AF elements that are created when an interface is configured to communicate with a PIWebAPI endpoint.
Note: CONNECT data services does not currently support static structure. The two streams that are created by setting an CONNECT data services endpoint communicate dynamic data.
Examples
This is what the PI AF structure would look like for a host called SRVTEST and an interface service called PI_UFL2. It is one of three instances of installed PI Interfaces.
The static attributes of the aforementioned elements are shown in this table and the screenshot that follows:
Static OMF Health data attributes
|
Attribute |
Data Type |
Description |
|---|---|---|
|
Data Source |
String |
The point source of the interface for which health data is being collected. |
|
Description |
String |
A description of the data collector. |
|
End Point |
String |
The name of the host machine where the interface is sending data. |
|
Host |
String |
The machine on which the interface is running. |
|
Type |
String |
The type of interface for which health data is being collected. |
|
Version |
String |
The version of the interface for which health data is being collected. |
Note: In the example image above, three additional fields _id, _indexPropertyIndexer, and _namePropertyIndexer can be seen. These attributes are used for internal purposes only and can safely be ignored. Additionally, these attributes are created as hidden attributes by default, and viewing of them can be disabled if so desired. Refer to the PI System Explorer User Guide for further instruction, specifically the section on how to disable the viewing of hidden attributes.