[Nut-upsuser] how do you test (nagios) that upsmon is connected?
spike at drba.org
Mon Apr 3 17:28:09 UTC 2017
thank you all for your input. Roger, I'm a nut noob and only marginally
understand the implementation (from your other email), but I really like
the idea of a heartbeat and design wise it makes a lot of sense. I'll see
if I can implement it some time soon.
On Sat, Apr 1, 2017 at 1:54 PM Roger Price <roger at rogerprice.org> wrote:
> On Sat, 1 Apr 2017, Stuart Gathman wrote:
> > On 04/01/2017 03:14 PM, Dan Craciun wrote:
> >> On my Nagios monitoring system I use check_nut_plus (that in turn
> >> calls upsc) to monitor the status (ups.status), load (ups.load),
> >> battery charge (battery.charge) and runtime (battery.runtime).
> >> If these return "unknown", it means upsd is no longer monitoring the
> >> UPS. As long as you get data, upsd is working.
> > That's great, but Spike wants to know whether *upsmon* is working. He
> > already has a way to check that upsd is working.
> How about using a dummy ups to set up a regular end-to-end heart beat.
> As long as the heart beats, there is no news, but if it stops,
> upssched-cmd sends out an e-mail or other warning.
> In ups.conf, add
> driver = dummy-ups
> port = heartbeat.dev
> desc = "Dummy ups sends heart beat to upssched-cmd"
> In heartbeat.dev, write
> ups.status: REPLBATT
> TIMER 300
> In upsmon.conf, write
> NOTIFYFLAG REPLBATT SYSLOG+EXEC
> In upssched.conf, add
> # Heatbeat from dummy ups every 5 minutes, re-start 6 minute timer
> AT REPLBATT heartbeat CANCEL-TIMER heatbeat-timer
> AT REPLBATT heartbeat START-TIMER heatbeat-timer 360
> In upssched-cmd, if heatbeat-timer completes, then send "UPS heatbeat
> failure" message to sysadmin.
> If this works, let me know, and I will use it myself :-)
> It would be nice to have a HEARTBEAT status instead of using REPLBATT.
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser