I just went through this exact exercise last week. A different method was recommended in IRC, and I built the following checker to suit:
Conditions:
sensor_event ne up
sensor_event ne ignore
Devices:
*
Entities:
sensor_class eq state
sensor_descr match *power supply*
This uses the built-in state logic to see if the power supply is alive or not. At the moment, I know that Brocade power supplies will go into ‘alert’ state
if they are missing or down. I’m assuming the same for Cisco, and that they’d also alert if there were max/min power violations as well. It might not be exact – as in “power supply undervolt!” – but I figure if a PSU is anything but “up” then it deserves to
be looked at.
From: observium [mailto:observium-bounces@observium.org]
On Behalf Of Jake Turner
Sent: Tuesday, September 02, 2014 4:43 AM
To: Observium Network Observation System
Subject: Re: [Observium] 6500 PSU Voltage Check
Hi,
After looking through the database it seems to make more sense. I've reconfigured it as:
Metric Condition Value
sensor_value
lt
220
In Associations I have * sensor_class equals voltage.
This still isn't working though.
Jake
From: observium [observium-bounces@observium.org]
on behalf of Jake Turner [Jake.Turner@turnerhouse.org.uk]
Sent: 02 September 2014 12:06
To: observium@observium.org
Subject: [Observium] 6500 PSU Voltage Check
Hi All,
I was wondering if I could configure alerts for the voltage on a couple of 6500 power supplies (to try and alert on power failures).
I've used the Entity Type of Voltage and this picks up the Enitity's from the 6500 (110/220v AC power supply, 2500 watt 2 - Power Supply 2 power-input) however
I'm unsure on how to configure the 'Check Conditions' and 'Associations'. The below is a guess for the check conditions:
Metric Condition Value
sensor_voltage
lt
220
In Associations I have simply put * * which I suspect is incorrect.
Has anybody else tried setting up checks on voltage?
Thanks
Jake