PI Nexus+ / Reference
Notifications Reference
This reference lists every email PI Nexus+ sends, its settings and defaults, and how delivery, retries and sites work. The Administration Guide chapter Notifications links here.
Overview
This reference lists every email PI Nexus+ sends, its settings and defaults, and how delivery, retries and sites work. The Administration Guide chapter Notifications links here.
Email types
An email is sent only when delivery is enabled, its rule is on under Delivery Rules, and the recipient has the email type ticked.
| Recipient email type | Delivery rule (Delivery Rules) | Subject starts with | Sent when |
|---|---|---|---|
| Manual scan completion | Manual scan completion | PI Nexus+ <scope> <outcome> | A manual, Run now or scheduled scan ends with a ticked outcome. One email per request, also for an AF request with several databases |
| Health issue changes | Operational health: New issues, Severity escalations, Recoveries after an alert | PI Nexus+ health alert / health recovery | An issue at or above Minimum severity opens, escalates, or recovers after an alert |
| Automatic monitoring failures | Automatic monitoring failures (under Operational health) | PI Nexus+ automatic monitoring needs attention | Automatic work for a target failed after its retries |
| PI Interface runtime | PI Interface runtime | PI Nexus+ interface alert / escalation / recovery | A PI Interface's runtime state changes to a ticked state, or recovers |
| PI Adapter runtime | PI Adapter runtime | PI Nexus+ adapter alert / recovery | A PI Adapter Collector's runtime state changes to a ticked state, or recovers |
| Host monitoring | Host monitoring | PI Nexus+ host alert / host recovery; PI Nexus+ scanner service is not running / is running again | See Host Monitoring Reference |
| Host monitoring escalations | Host monitoring (Escalation) | PI Nexus+ host escalation | See Host Monitoring Reference |
| Recalculation suggestions | Analysis recalculation: New recalculation suggestions | PI Nexus+ new recalculation suggestion(s) | New analysis recalculation suggestions, grouped every 5 minutes |
| Auto Tune | Auto Tune: Recommendations ready for review, Retry exhausted or restore-safety failure | PI Nexus+ Auto Tune recommendations ready / needs attention | An Auto Tune batch has recommendations, or needs attention |
| (no type) | Connection tab | PI Nexus+ email notification test | Send test, to the address entered |
Opened, escalated and recovered PI Adapter issues are also included in the health issue emails.
Default settings
| Setting | Default |
|---|---|
| Email delivery | Paused |
| Port | 25 |
| Use SSL/TLS | On |
| Manual scan completion | Succeeded, Failed, Canceled on; Skipped off |
| Operational health Enable | Off |
| Its New issues, Severity escalations, Recoveries after an alert, Automatic monitoring failures | On |
| Minimum severity (health and host) | Warnings and errors |
| PI Interface runtime Enable | Off; once on: Error, Unknown visibility, Recovery after an alert on, Warning off |
| PI Adapter runtime Enable | Off; once on, all four choices off until ticked |
| Host monitoring | Off (see Host Monitoring Reference) |
| Auto Tune choices | Off |
| New recalculation suggestions | Off |
| Issues CSV, Changes CSV | Off |
| Issue severities | Error,Warning |
| Max CSV size (MB) | 5 (1 to 25) |
| New recipient | Enabled; All sites; every email type except Host monitoring escalations |
Behaviour of each email
| Rule | |
|---|---|
| Scan completion | Automatic and configuration scans never send one. Completed with errors uses the Failed box. CSV attachments are cut to the recipient's sites |
| Health issues | The first completed scan after the rule is switched on sets a quiet baseline: existing issues are not mailed. Suppressed issues are not mailed |
| Automatic monitoring failures | One email per work item that stopped retrying; up to 3 delivery attempts, 5 minutes apart |
| Runtime alerts (PI Interfaces, PI Adapters) | A degraded state must last 2 minutes before it is mailed. Suppressed runtime issues are left out. An open alert is not repeated at the same severity; an escalation (Unknown, then Warning, then Error) sends one more email if the new severity is ticked. A drop to a lower severity waits for the recovery email. A recipient that received an alert also receives its recovery |
| Recalculation suggestions | Only suggestions created after the rule was switched on; older ones are not replayed. The email does not start a recalculation. Times are in the scanner server's local time |
Delivery and retries
| Situation | Behaviour |
|---|---|
| Any failed send | Retried on the email's own short schedule: health issues after 5 and 5 minutes; runtime alerts after 1, 5 and 15 minutes |
| Mail server unreachable, timeout, or a 4xx reply | Retried after that with growing waits of at most 30 minutes, for up to 24 hours from the change |
| 5xx reply, invalid address or message | Not retried beyond the short schedule |
| Server rejects some recipients | The others receive the message and are not sent it again; the rejected addresses are reported until they accept a later message |
| Send timeout | 100 seconds |
| Failures | Reported as active notification failures in Admin > Support > Readiness |
Sites
| Recipient scope | Receives |
|---|---|
| All sites | Every item, including items whose site is unknown, and all Auto Tune emails |
| Selected sites | Only items of those sites, with counts recalculated; nothing when no item concerns them. Scan-completion emails only when the scan touched one of its sites |
Recipients with the same scope share one message; recipients with different scopes never see each other's addresses. If delivery fails for one group, only that group is retried. A recipient whose last site is deleted is disabled with the reason shown, and cannot be enabled again until All sites or Selected sites is chosen.
Who can do what
| Action | Role |
|---|---|
| Everything under Admin > Notifications | Admin |
