Consumer details
- Last UpdatedOct 04, 2024
- 2 minute read
- PI System
- PI Server 2023
- PI Server
|
Column |
Description |
|---|---|
|
Producer |
The source of update notifications. Currently there are five producers. PI Snapshot Subsystem is a producer of snapshot events. PI Base Subsystem is a producer of Point Database and Module Database changes. PI Archive Subsystem is a producer of archive changes. PI Batch Subsystem is a producer of Batch Database changes. |
|
Consumer |
An application that currently signed up as a consumer of specified producer. For PI API applications, the consumer name is usually the first four letters of the login name of the user running the application. These names are not unique so the PI Update Manager assigned ID is appended to the name. PI API applications also have the PI Network Manager ID appended. These integers are appended to help you find specific consumers. For the PI SDK, the consumer name is the complete application name with a colon and a PI SDK supplied identifier followed by a pipe character and a PI Update Manager assigned ID. |
|
Qualifier |
A producer specific integer. For example, Snapshots update stores the requested point ID in the qualifier. When the Query for additional information check box in the Options dialog is selected, this column displays the tag name (Tag point attribute). |
|
Flag |
A producer-specific value. |
|
Pending |
Number of events available for the consumer to retrieve. The value goes up and down as events come in and the consumer pulls them out. Values that increase continuously might indicate that the consumer is not working properly or disconnected. The Pending number shows a maximum of 50000 events, even if more events are in the queue. You can configure this limit with the MAXUPDATEQUEUE Tuning Parameter. The Update Manager might limit individual consumers from accumulating too many pending events. This is a display limitation and does not imply data loss. |