Adam,

  Here is the poller output, I notice that on line 528, there seems to be an indication of a failure…

 

Tony Guadagno

O +1 585 577 1003

C +1 585 703 6700

E tonyg@guadagnoconsulting.com

cid:image001.jpg@01D84DD6.FC9912E0

 

From: Adam Armstrong via observium <observium@lists.observium.org>
Sent: Monday, December 19, 2022 8:30 AM
To: Tony Guadagno via observium <observium@lists.observium.org>
Cc: Adam Armstrong <adama@observium.org>
Subject: [Observium] Re: not detecting failed test on cyberpower ups

 

Those walks aren't really useful here, since I can't read numerical OIDs, and have no idea what the OIDs of those status indicators are. :D

You probably want the output of :

./poller.php -h <device_id> -m status -dd

We can only really act on the data the device provides. It looks like the device isn't providing the correct status.

The timestamps in the descriptions are just handled as descriptions, they'll only be updated during discovery, so they're not really reliable. (you can force discovery with ./discovery.php -h <device_id> -m sensors,status -dd

adam.

Tony Guadagno via observium

19 December 2022 13:09

Hi, I noticed that one of my ups’ has failed its selftest on 12/19…however…Observium is reporting a successful test (but from the previous week 12/12). 

From the ups:

And

 

How can we tell if the issue is with the UPS not reporting properly, or Observium not recognizing?  I have attached some snmp walks.

Thanks

 

 

 

Tony Guadagno

O +1 585 577 1003

C +1 585 703 6700

E tonyg@guadagnoconsulting.com

cid:image001.jpg@01D84DD6.FC9912E0

 



_______________________________________________
observium mailing list -- observium@lists.observium.org
To unsubscribe send an email to observium-leave@lists.observium.org

 

--

Sent from Postbox