Hi Henrik,
Sensors are all "gauges", so there's no real concept of spikes the way there is for ports (which are counters).
If we're getting a spike, it's either that the device is sending the wrong data, or that the device is sending a number which hasn't been adjusted for the scale the device uses. It'll be the first if the 1.6-1.9 doesn't have any relation to the "real" number, and the latter if it's just off by a few orders of magnitude.
It's pretty unlikely that we could do any bad maths, maths is easy, and such bugs would present much more regularly. These sorts of things are pretty common on many vendor's SNMP implementations. You might be able to see it in action by frequently polling the sensor in question's OID and logging the value.
adam.
Sent from Mailbird [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 10/06/2016 13:40:59, Henrik Cednert (Filmlance) henrik.cednert@filmlance.se wrote: Hello
Monitoring two APC in-row coolers. One of them gets some weird 1.6-1.9M watts spikes every now and then. Once a day or such, without regularity. I have started to monitor the same device in Schneider Data Center Expert just to see if it's a device or monitoring issue. There's no spikes there so I do think it's something with Observium and this particular unit. The other unit is fine and no spikes there. Only difference is that the load on this one is smaller and at times down to 0.
I do see that there's an option to log spikes in the config file. But not sure I can monitor a sensor with it since it says port and wants and ID. Can I debug these spikes in some way?
Cheers and thanks
-- Henrik Cednert cto | compositor
Filmlance International | www.filmlance.se mobile [ + 46 (0)704 71 89 54 ] skype [ cednert ]
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium