Because the "OK" range for that sensor is between 31 and 41 degrees.

If the temp is between -10 and +31, you will get a "low warning" state.

If the temp is between +41 and +56, you will get a "high warning" state.

If your temp is lower than -10 or higher than +56, you'll get the respective alarm states.

I frequently find devices that don't report corerct ranges for temperature sensors, so I need to set my own. You can insert whatever values you like in these fields and then move the custom slider to activate them.

For inlet temp sensors, low values that are sensible for the room they are in is a good idea. If your DC runs at 24C, then you could in theory set a low warning of 20C and an alarm at 10C. If they were devices outside in the Norwegian winter, you might want different values.

Cheers,

M

On 17 Sep 2020, at 8:45 am, Shawn L via observium <observium@observium.org> wrote:

I have a strange one.  We recently added a cisco 3850 stack of three switches.  I'm now getting temperature alerts from Observium.  But when I look at the switches, the temps they report all look fine.

 

When I look in the sensors section, I can see that the temp is currently 25c, the low is -15 and the warn is 31.  But yet Observium is saying there's a temp issue.  I know I can turn it off, but I'm curious why it's alerting me.

 

 

<Screenshot from 2020-09-16 18-39-55.png>_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium