Multi UPS Monitoring Guide

Multi-UPS Monitoring Guide

This page is dedicated to Multi-UPS operations in Nutify. It explains how multi-target monitoring works, how target context is resolved, and how to operate safely day-to-day.

1) What Multi-UPS Means in Nutify

Multi-UPS mode lets one Nutify instance monitor multiple UPS targets, local and/or remote, with independent target configuration.

Typical use cases:

• home lab with multiple UPS devices
• branch/remote UPS monitoring from one dashboard
• mixed topology (local primary + remote additional targets)

2) Key Concepts

• Target: one UPS endpoint (ups@host).
• Primary target: default fallback target.
• Active target: current UI context selected in TopBar.
• Fleet view: aggregate overview across all targets.

3) Target Context Resolution

Target-aware pages/APIs resolve context in this order:

1. explicit target_id request override
2. session active target
3. primary enabled target fallback

Operational best practice:

• when scripting APIs, pass explicit target_id

4) TopBar Behavior in Multi Mode

When multiple enabled targets exist:

• topbar target selector is active
• values in topbar represent selected target
• target-scoped tabs (Notify, Reporter, PowerFlow) follow selected target

Daily rule:

• verify target in TopBar before any write action

5) Fleet View Page

Open Multi-UPS Monitoring from topbar action.

Use fleet view to:

• compare target health quickly
• detect offline/degraded targets
• triage where to investigate first

Do not use fleet view as replacement for per-target detailed configuration.

6) Polling Model

Multi polling runs per target.

Behavior goal:

• one target failure should not block polling of other targets

Practical impact:

• partial fleet incidents remain isolated
• healthy targets continue updating normally

7) Multi-Target Lifecycle (NUT Manager)

Use System -> Advanced -> NUT Manager to:

• add/edit/remove targets
• enable/disable targets
• set primary target
• force poll-now

After target changes:

1. verify target appears in topbar selector
2. switch target and verify page data updates
3. validate notifications/reports routing per target

8) Multi-Target Notify and Reporter Pattern

Use this pattern:

1. configure global providers once (System -> Provider)
2. select target A and configure Notify/Reporter
3. switch to target B and configure Notify/Reporter
4. repeat for all critical targets

Never assume target B inherits target A routing automatically.

9) Mixed Local + Remote Operational Pattern

In mixed scenarios:

• primary target is local
• additional targets are often remote

Best practice:

• validate local target first
• add remote targets one by one
• test each target immediately after save

10) Common Multi APIs

State and inventory:

• GET /api/multi-nut/state
• GET /api/multi-nut/targets

Target control:

• POST /api/multi-nut/targets/<id>/poll-now
• POST /api/multi-nut/targets/<id>/primary

Context session:

• GET /api/multi-nut/active-target
• POST /api/multi-nut/active-target

Reports:

• GET /api/multi-nut/report

11) Daily Multi-UPS Checklist

1. open fleet view and check status summary
2. switch through critical targets in topbar
3. inspect Power/Battery/Voltage for anomalies
4. inspect Events for each critical target
5. validate delivery channels on high-priority targets

12) Incident Triage Workflow (Multi)

If one target is failing:

1. confirm only that target is degraded
2. run poll-now for affected target
3. inspect connection credentials and host reachability
4. verify events/logs for target-specific errors
5. keep other targets running and monitored

13) Common Mistakes

• editing target-scoped settings on wrong active target
• confusing fleet view with active-target detailed context
• not setting a reliable primary target fallback
• adding remote target with wrong UPS identifier format

14) Validation Checklist After Multi Setup

Multi setup is healthy when:

• all expected targets appear in topbar selector
• target switching refreshes dashboard context correctly
• fleet page reflects consistent status per target
• target-specific Notify/Reporter settings are persisted and working