PI Nexus+ / Reference
Scanning Page Reference
This reference lists the cards, tabs, columns, filters and actions of the Scanning page. Kinds of work, triggers, scopes and outcomes are in Scan Runs Reference; cadences and the heavy-work window in Scan Automation Reference.
Overview
This reference lists the cards, tabs, columns, filters and actions of the Scanning page. Kinds of work, triggers, scopes and outcomes are in Scan Runs Reference; cadences and the heavy-work window in Scan Automation Reference.
Access
| Item | Role |
|---|---|
| See the page (scan status entry in the navigation) | Operator |
| Refresh health, Reconcile inventory, Retry, Run now, Cancel, Remove from queue, Refresh health now, CSV export | Operator |
| Recover, Permanently delete, Open diagnostics | Admin |
The page always shows the whole estate.
Inventory scan and health refresh
| Aspect | Inventory scan | Health refresh |
|---|---|---|
| Answers | What exists, and what changed? | Is what we know still healthy? |
| Reads | The full object catalogue in scope | Current values and state of known objects |
| Writes | Inventory, missing markers, references, change history, health | Health and issues |
| Finds new or deleted objects | Yes | No |
| Typical duration | Minutes to hours | Seconds to minutes |
| Target types | PI Data Archives, AF databases, PI Vision instances | PI Data Archives, AF databases |
| Advances | Inventory and health freshness | Health freshness only |
A successful inventory scan also stamps health freshness and retires a health refresh already queued for the target. A target without a completed inventory scan reports awaiting inventory and gets no health refresh.
Status card
The first matching row applies.
| Value | When | Subline |
|---|---|---|
| Loading… | The page is still loading the scanning status | Loading scanning status |
| Unavailable | The scanning status could not be loaded | Scanning status could not be loaded |
| Running / Waiting | A scan is running / work is queued | Trigger, kind of work, target and progress, or the number queued |
| No targets | No target is included in scanning | No targets are included in scanning |
| Needs action | A condition needs attention, or a health target is failing | Monitoring mode and the number needing action |
| Paused | Automatic scanning is paused | Since when, by whom, and the health age |
| Needs action | Inventory or health is due and automatic monitoring is off | Monitoring mode and what is due |
| Catching up | Inventory or health is due and automatic monitoring is on | Monitoring mode and what is due, for example 3 inventory due |
| Up to date | Nothing is due | Monitoring mode · Nothing due |
The monitoring mode reads Automatic monitoring on, Automatic monitoring paused or Automatic monitoring is off. A target never scanned is inventory due, so the estate is then never Up to date.
Health and Inventory cards
| Card | Value | Subline |
|---|---|---|
| Health | Targets with current health / targets with health refreshes | N failing, else N awaiting inventory, then Last refresh and oldest target |
| Inventory | Included targets not inventory due / included targets | Last scan and oldest target |
Last refresh and Last scan are the latest success anywhere in the estate; oldest target is the stalest included target (never refreshed or never scanned if one never succeeded). Hover for exact times.
Needs attention card
Counts targets and conditions needing action, listed in this order: health failing, health due, inventory failing, inventory due, failed, completed with errors, awaiting retry, and SQL pressure (while SQL Server reports memory pressure). A change-feed alert is counted too. With a zero count it reads Nothing requires action, or N failures in 24 h, all recovered when earlier failures have since recovered.
Last 24 hours
| Element | Click opens |
|---|---|
| N runs | History for the last 24 hours |
| succeeded, with errors, failed, canceled (shown when not zero; failed includes skipped) | History filtered to that outcome |
| Typical | Nothing (median duration) |
| Longest | That run |
Banner
Health refreshes take as long as the freshness cadence appears with a custom cadence when a target's last health refresh took at least 80 % of the cadence. The achievable period is about the cadence plus the refresh duration.
Work tabs
The page opens on Active when a scan runs, else Needs attention when anything needs attention, else History. A tab you choose stays selected.
| Tab | Rows | Actions |
|---|---|---|
| Needs attention | Due or failing targets, failed work, change-feed alerts, SQL pressure. Show: All, Health, Inventory | Refresh health / Reconcile inventory (Queued when already queued), Retry (Retry queued), dismiss, Scan now (change feed), Open diagnostics (SQL) |
| Active | The running scan with progress | Details, Cancel, Recover |
| Queued | Waiting work in execution order, with its source | Run now (automatic work waiting for the heavy-work window), Remove from queue |
| Targets | Every enabled target | Row menu: Open target history, Refresh health now (PI Data Archives and AF databases) |
| History | Every finished run | Row menu: Open run details, Permanently delete |
Targets tab
| Column | Content |
|---|---|
| Target | Name and type |
| Inventory | Outcome and age of the last inventory scan; Never with No inventory scan yet |
| Health | Outcome, age and duration of the last health refresh; Failing N times in a row; — with No health refresh for PI Vision instances |
| Coverage | Activity strip (one mark per period, coloured by the worst outcome, sized by duration) and an outcome summary such as All N succeeded or No runs in this range. Never scanned when no inventory scan ever completed. Notes: Paused, Excluded from automatic monitoring, Not enrolled in automatic monitoring |
Both columns show the last run of that kind whenever it happened, not only within the range. Activity: Last 24 hours, Last 7 days, Last 30 days.
Sort order, worst first: never inventoried; failing; stale against the freshness objectives; oldest success; then type and name. Pages of 25 (Load 25 more).
History tab
| Item | Values |
|---|---|
| Columns | Target, Type, Trigger, Started (with duration), Result |
| Type badge | Inventory, Health, Inventory update, Maintenance |
| Type filter | All types, Health (includes object checks and inventory updates), Inventory |
| Trigger filter | All triggers, Automatic (includes System), System, Manual (includes Run now), Configuration, Schedule |
| Outcome filter | All outcomes, Succeeded, Completed with errors, Failed or skipped, Skipped, Canceled |
| Range filter | Last 24 hours, Last 7 days, Last 30 days, Retained history |
| Order | Newest completion first; pages of 25 |
| Result | The run's message and notes, such as objects no longer found at the source |
| CSV export | Every stored run, regardless of the filters |
Manual work dialogs
| Row | Reconcile inventory | Refresh health |
|---|---|---|
| First row | Full inventory: PI Points, Asset Framework and PI Vision | All operational health: PI Points and Asset Framework |
| PI Points | Targets, and All rules or chosen enabled inventory PI Point rules | Targets (always all rules) |
| Asset Framework | AF servers and All databases or chosen ones; each database is its own run | Same |
| PI Interfaces | Offered | Not offered |
| PI Vision | Offered | Not offered |
Every row has Add to queue. A duplicate shows Already queued; for Asset Framework only the databases not already waiting are added. A run narrowed to PI Point rules is named Rule: Compression, Rule: Compression (PISRV01) when it covers one archive, or 2 PI Point rules.
Checks on one object
| Action (detail dialog) | Objects | Effect |
|---|---|---|
| Check health | PI Points, AF Attributes, AF Analyses, PI Interfaces, PI Adapters | Re-reads current health. A PI Point also refreshes its known AF Attributes and PI Vision displays; an AF Attribute its displays; an AF Analysis only itself. No historical recalculation; inventory and freshness unchanged |
| Update inventory | PI Points, AF Attributes, AF Analyses, AF Elements, AF Element Templates, PI Vision displays | Reloads the object from its source (structure, references, health) as a manual Inventory update run. An attribute or analysis reloads its element; a template its derived elements. Joins an update or full scan already queued for the target |
Both need the Operator role and are hidden in the Evaluation edition.
Retention
Old runs leave History by retention: routine health history after 30 days and inventory and diagnostic history after 180 days by default. The settings are in Retention and Maintenance Reference.
