PI Buffered Logical Servers statistics
- Last UpdatedJul 15, 2025
- 3 minute read
PI Buffered Logical Servers counters record the buffering status of logical servers. For the purposes of these counters, a logical server is any Data Archive server you can connect to (for example, using Connection Manager). That means it can be either a Data Archive collective or a single Data Archive server. Logical counters include counters that apply only to logical servers, and counters that represent aggregated values of all physical servers that comprise a specific logical server.
|
Attribute |
Description |
|---|---|
|
Buffer Sessions Active |
Number of active buffer sessions* for all physical servers in this logical server to which PI Buffer Subsystem is connected and sending data. |
|
Buffer Sessions Offline |
Number of inactive buffer sessions* for physical servers in this logical server to which PI Buffer Subsystem is unable to send data. |
|
Buffer Sessions Total |
Total number of active and offline buffer sessions* for this logical server. |
|
Compressed Events/sec |
Rate of events marked for archiving (does not include Out-Of-Order events). |
|
Events In Error |
Number of events not processed locally by the Buffer Subsystem, including:
|
|
Events Received/sec |
Rate of events received. |
|
Events Rejected |
Number of events rejected by the Buffer Subsystem, including:
|
|
Health |
Health of this server (0 = OK, 1 = Warning, 2 = Error, 3=Critical) |
|
Out-Of-Order Events/sec |
Rate of out-of-order events received. |
|
Point Count |
Numbers of local points with cached configuration (on disk). |
|
Point Edits/sec |
Rate of new points and point edits received from the Data Archive server. |
|
Points With Post Error |
Total number of points that received errors when posting, for all servers. |
|
Queue> Capacity |
The estimated time (in seconds) that PI Buffer Subsystem can buffer data for this logical server (collective) if connection to all the physical servers (collective members) is lost. |
|
Queue> File Count |
Total number of queue files for all physical servers in this logical server. |
|
Queue> Reset Folder Count |
Number of buffer queue reset folders currently in storage. If PI Buffer Subsystem detects the queue is corrupted and is not able to recover it, a new queue is created so that data can flow. Each time that happens, the old corrupted queue files are saved in a separate folder under the configured queue path. |
|
Queue> Write Errors |
Number of events that failed to be written to the buffer queue for all physical servers in this logical server. |
|
Total API Buffered Events |
Number of events in all API buffers (including APIBUF*.DAT files). |
|
Total Events Sent/sec |
Rate of events sent to all physical servers in this logical server. |
|
Total Queue Writes Exclusive/sec |
Rate of events written to a buffer queue but not other queues in the same collective (no fanning mode). |
|
Total Queue Writes/sec |
Rate of events written to buffer queues for all physical servers in this logical server. |
|
Total Queued Events |
Total number of buffered events for all physical servers in this logical server. |
|
Total Snapshot Posts/sec |
Rate of data posts to all physical servers in this logical server. |
|
Unresolved Cache Points |
Numbers of local points with unknown configuration. |
* When PI Buffer Subsystem establishes buffering to a physical server, it creates a buffer session. The session persists as long as PI Buffer Subsystem is buffering to this server.