Observe
Operators first watch what would happen without firing a shutdown action. Observe mode lets a site confirm that runtime, battery, and event signals are being interpreted as expected before any host or UPS shutdown command is allowed to run.
EXPLAINER
Automated UPS shutdown, done safely.
UPS shutdown software should not move straight from configuration to live action. MayaUPS uses Observe → Dry-run → Armed so shutdown policy is first visible, then rehearsed, and only then allowed to act.
Dry-run proof
A dry run records before/after proof, so the sequence is rehearsed before it is armed. That proof matters because shutdown is a high-consequence workflow: the operator needs evidence that the policy, trigger, target order, and communication path behave correctly.
Armed
Only after proof can a policy be armed. Triggers can be runtime-based or event-based, with SNMP-SET UPS shutdown and an mTLS host agent for ordered host shutdown. MayaUPS also includes a boot kill switch that can force armed policies back to Observe.
Host-agent role
The host agent is used for ordered shutdown on Linux and Windows hosts. mTLS keeps that channel distinct from ordinary monitoring and separates live action from read-only SNMP polling.
Alerting and audit trail
Shutdown readiness sits beside grouped SMTP alerts, return-to-normal notices, escalation, optional daily digest, roles, backups, restore, watchdog behaviour, graceful stop, and optional file logging. Those controls make the state of the shutdown workflow easier to review before and after an incident.
Accuracy note
Live-action shutdown paths are still awaiting final real-hardware bench approval and should not be described as generally released until that evidence is signed off.