What it monitors
A UPS can expose status, battery charge, runtime remaining, load, input/output voltage, temperature, and alarms through a network-management card or other interface. MayaUPS also brings PDU, ATS, and environmental sensors into the same power-edge view when those devices expose usable SNMP data.
Why SNMP matters
In professional LAN environments, SNMP is the common monitoring path. MayaUPS supports SNMP v1/v2c/v3, sealed credential profiles, SNMPv3 authentication and privacy, Test connection per device, and operator-initiated read-only discovery bounded to a /24.
Why RFC-1628 matters
RFC-1628 defines the standard UPS MIB, which gives monitoring tools a common baseline across brands. MayaUPS uses that standard data where available and layers vendor-specific decoding on top when a profile exposes richer bitmasks or flags.
Why battery data matters
Battery service-life data helps plan replacement before the battery fails during the event it was meant to cover. MayaUPS tracks install date, nominal life, preventive-maintenance date, temperature-adjusted estimates, and battery_due / pm_due alarms roughly 30 days ahead.
Why shutdown safety matters
Monitoring should not jump straight into live shutdown. MayaUPS uses Observe → Dry-run → Armed so policies can be evaluated, rehearsed, and proven before action. SNMP-SET and the mTLS host agent are part of that controlled path; live-action paths still require final bench approval.
What a good dashboard should show
For daily operation, the software should show readable alarm states, current fleet status, history charts for 24 h / 7 d / 30 d windows, CSV export, grouped email alerts, and role-appropriate access. Those are the practical signals that turn raw UPS telemetry into maintenance and incident decisions.