PI Nexus+ / Reference
PI Adapter Monitoring Statuses
This reference lists the source statuses on Admin > PI Adapters, the Runtime statuses of PI Adapter Collectors, the service issues and the fixed thresholds.
Overview
This reference lists the source statuses on Admin > PI Adapters, the Runtime statuses of PI Adapter Collectors, the service issues and the fixed thresholds.
AF source
| Column | Values |
|---|---|
| Discovery | Complete, Partial, Failed, Not attempted, with the time of the last attempt |
| Health reads | As above, for the last health read |
| Adapters | Active adapter services found |
| Status | Enabled; Disabled; Parent disabled (its AF database or AF server is disabled) |
| Action | Effect |
|---|---|
| Add AF source | Offers enabled AF databases not yet selected; Test reads without saving; Save disabled saves |
| Test AF source (play button) | Repeats the test: adapters, components, resolved bindings, readable diagnostics |
| Enable monitoring (power button) | Starts the reads and queues an AF scan of the database for discovery |
| Disable monitoring (power button) | Stops the reads; Collectors stay with their last evidence, shown as disabled |
A failed or partial discovery never marks Collectors missing; only a complete one can. A source cannot be removed from the page; disable it instead.
Collector Runtime
| Status | Meaning |
|---|---|
| Good | Device status good and heartbeat on time for every component |
| Warning | The adapter reports Starting, ConnectedNoData, NotConfigured or AttemptingFailover |
| Error | The adapter reports DeviceInError, Shutdown or Removed, or its heartbeat is overdue |
| Unknown | Health signals unbound, unreadable or bad quality, or an unrecognized device status |
| Unknown / Monitoring stalled | No health read has succeeded for 3 poll intervals, at least 10 minutes. A monitoring condition, not proof of an adapter failure |
| Not Evaluated | Monitoring disabled, or the first read after enabling has not finished |
Other evaluations
| Evaluation | Rule |
|---|---|
| Configuration | Checks the recognized DataCollectorHealth / OmfEgressHealth structure, bindings and types; not the adapter's own settings. An unrecognized structure is Not Evaluated with Unsupported monitoring structure |
| Data Health | PI Points whose OMF data source matches the Collector's, on scanned PI Data Archives. Always partial coverage. Not Evaluated when no point matches exactly |
| Check health on a Collector | Reads the health signals of its AF database's Collectors once, without an AF inventory scan (Operator) |
Service issues
Raised on the adapter service, not in a Collector's Runtime.
| Issue | Severity | Raised when | Resolves when |
|---|---|---|---|
| Restart loop | Warning | 3 or more process starts within 24 hours, from the service's System.StartTime PI Point | Fewer than 3 starts remain in the last 24 hours |
| Low storage | Warning below 10 % free, Error below 5 % | The disk the adapter stores data on, from its System storage diagnostics | First read above 10 % |
Restarts can be under-counted, never over-counted, when System.StartTime is not archived or compression drops start times. The start-time history is read only for a service that started within the last 24 hours.
Fixed values
| Value | Setting |
|---|---|
| Runtime poll interval | Interface and adapter runtime poll, Admin > Scan Automation, 1 to 15 minutes, default 1 |
| Heartbeat overdue | The published next-expected-message time passed by more than 2 minutes |
| Stalled after | 3 poll intervals without a successful read, at least 10 minutes |
| Restart loop | 3 starts in 24 hours |
| Low storage | 10 % (Warning), 5 % (Error) |
Monitoring is verified with the DNP3, Modbus, MQTT, OPC UA and RDBMS adapters; adapter failover and several OMF destinations per adapter are not yet qualified.
A source whose AF database is being scanned is skipped for that poll. Runtime alerts are configured under Admin > Notifications > Delivery Rules > PI Adapter runtime, off by default; opened, escalated and recovered PI Adapter issues follow the health-issue email settings.
