resetting sensors doesn't work (Observium 17.5.8580)
Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2535/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2534/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2533/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2532/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas
It's not really clear what's happening, and you haven't told us what the "incorrect" thresholds are or why they're incorrect. Sensor thresholds are autogenerated as the returned value +/- a percentage when they're not supplied by the device.
The reset function just unsets any thresholds so that the next discovery process will either set them back to what the device supplies, or autogenerate them again.
The sensors in question should get their thresholds directly from the device :
// HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature.8 = INTEGER: 50 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperatureThreshold.8 = INTEGER: 85 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtCriticalTemperatureThreshold.8 = INTEGER: 95 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtLowerTemperatureThreshold.8 = INTEGER: -30 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtShutdownTemperatureThreshold.8 = INTEGER: 65535
What values is your device returning?
adam. On 2017-10-25 08:41:11, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote: Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] SubCard0 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] SubCard0 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] Board [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] Board [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas
-- Thomas Stather IT Services VCP4, VCP6-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
Hi
Please see the attached screenshot. The thresholds are always 0 even after having the reset switch set.
Best, Thomas
Am 25.10.2017 um 21:42 schrieb Adam Armstrong:
It's not really clear what's happening, and you haven't told us what the "incorrect" thresholds are or why they're incorrect. Sensor thresholds are autogenerated as the returned value +/- a percentage when they're not supplied by the device.
The reset function just unsets any thresholds so that the next discovery process will either set them back to what the device supplies, or autogenerate them again.
The sensors in question should get their thresholds directly from the device :
// HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature.8 = INTEGER: 50 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperatureThreshold.8 = INTEGER: 85 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtCriticalTemperatureThreshold.8 = INTEGER: 95 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtLowerTemperatureThreshold.8 = INTEGER: -30 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtShutdownTemperatureThreshold.8 = INTEGER: 65535
What values is your device returning?
adam.
On 2017-10-25 08:41:11, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote:
Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2535/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2534/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2533/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2532/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas -- Thomas Stather IT Services
VCP4, VCP6-DCV
Tel: +49 6221-486 628 Fax: +49 6221-486 561
Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
That's most likely because your device is sending thresholds of zero. You can either get the vendor to fix this, or set manual thresholds.
Resetting the threshold only causes it to set it back to what the device is supplying. I'm not sure what other outcome you'd reasonably expect.
adam. On 2017-11-02 10:25:20, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote: Hi
Please see the attached screenshot. The thresholds are always 0 even after having the reset switch set.
Best, Thomas
Am 25.10.2017 um 21:42 schrieb Adam Armstrong:
It's not really clear what's happening, and you haven't told us what the "incorrect" thresholds are or why they're incorrect. Sensor thresholds are autogenerated as the returned value +/- a percentage when they're not supplied by the device.
The reset function just unsets any thresholds so that the next discovery process will either set them back to what the device supplies, or autogenerate them again.
The sensors in question should get their thresholds directly from the device :
// HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature.8 = INTEGER: 50 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperatureThreshold.8 = INTEGER: 85 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtCriticalTemperatureThreshold.8 = INTEGER: 95 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtLowerTemperatureThreshold.8 = INTEGER: -30 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtShutdownTemperatureThreshold.8 = INTEGER: 65535
What values is your device returning?
adam. On 2017-10-25 08:41:11, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de [mailto:thomas.stather@mpimf-heidelberg.mpg.de] wrote: Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] SubCard0 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] SubCard0 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] Board [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] Board [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas
-- Thomas Stather IT Services VCP4, VCP6-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
-- Thomas Stather IT Services VCP4, VCP6-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
Hi
I thought that the thresholds are automatically calculated and set by Observium and that the device itself doesn't provide them (only the sensor data).
Best, Thomas
Am 02.11.2017 um 14:43 schrieb Adam Armstrong:
That's most likely because your device is sending thresholds of zero. You can either get the vendor to fix this, or set manual thresholds.
Resetting the threshold only causes it to set it back to what the device is supplying. I'm not sure what other outcome you'd reasonably expect.
adam.
On 2017-11-02 10:25:20, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote:
Hi
Please see the attached screenshot. The thresholds are always 0 even after having the reset switch set.
Best, Thomas
Am 25.10.2017 um 21:42 schrieb Adam Armstrong:
It's not really clear what's happening, and you haven't told us what the "incorrect" thresholds are or why they're incorrect. Sensor thresholds are autogenerated as the returned value +/- a percentage when they're not supplied by the device.
The reset function just unsets any thresholds so that the next discovery process will either set them back to what the device supplies, or autogenerate them again.
The sensors in question should get their thresholds directly from the device :
// HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature.8 = INTEGER: 50 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperatureThreshold.8 = INTEGER: 85 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtCriticalTemperatureThreshold.8 = INTEGER: 95 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtLowerTemperatureThreshold.8 = INTEGER: -30 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtShutdownTemperatureThreshold.8 = INTEGER: 65535
What values is your device returning?
adam.
On 2017-10-25 08:41:11, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote:
Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2535/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2534/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2533/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2532/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas -- Thomas Stather IT Services
VCP4, VCP6-DCV
Tel: +49 6221-486 628 Fax: +49 6221-486 561
Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Thomas Stather IT Services
VCP4, VCP6-DCV
Tel: +49 6221-486 628 Fax: +49 6221-486 561
Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
We calculate them when they're not provided, some mibs do this (usually the extended entity-mibs) and some don't.
You can usually spot observium's autogen'd ones because they'll be weird decimals because of the maths. If they're whole numbers, they're probably from the device itself.
adam. On 2017-11-02 15:09:19, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote: Hi
I thought that the thresholds are automatically calculated and set by Observium and that the device itself doesn't provide them (only the sensor data).
Best, Thomas
Am 02.11.2017 um 14:43 schrieb Adam Armstrong:
That's most likely because your device is sending thresholds of zero. You can either get the vendor to fix this, or set manual thresholds.
Resetting the threshold only causes it to set it back to what the device is supplying. I'm not sure what other outcome you'd reasonably expect.
adam. On 2017-11-02 10:25:20, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de [mailto:thomas.stather@mpimf-heidelberg.mpg.de] wrote: Hi
Please see the attached screenshot. The thresholds are always 0 even after having the reset switch set.
Best, Thomas
Am 25.10.2017 um 21:42 schrieb Adam Armstrong:
It's not really clear what's happening, and you haven't told us what the "incorrect" thresholds are or why they're incorrect. Sensor thresholds are autogenerated as the returned value +/- a percentage when they're not supplied by the device.
The reset function just unsets any thresholds so that the next discovery process will either set them back to what the device supplies, or autogenerate them again.
The sensors in question should get their thresholds directly from the device :
// HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature.8 = INTEGER: 50 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperatureThreshold.8 = INTEGER: 85 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtCriticalTemperatureThreshold.8 = INTEGER: 95 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtLowerTemperatureThreshold.8 = INTEGER: -30 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtShutdownTemperatureThreshold.8 = INTEGER: 65535
What values is your device returning?
adam. On 2017-10-25 08:41:11, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de [mailto:thomas.stather@mpimf-heidelberg.mpg.de] wrote: Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] SubCard0 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] SubCard0 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] Board [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=...] Board [https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric...] Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas
-- Thomas Stather IT Services VCP4, VCP6-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
-- Thomas Stather IT Services VCP4, VCP6-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
-- Thomas Stather IT Services VCP4, VCP6-DCV Tel: +49 6221-486 628 Fax: +49 6221-486 561 ------------------------------------------------------------------------ Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
Hi
thanks Adam, i think you fixed this some time ago! When i updated yesterday, the values are now processed correctly
------------------------------------------------------------------------ r8696 | adama | 2017-07-14 12:39:24 +0200 (Fri, 14 Jul 2017) | 2 lines
[IMPROVE] Improve threshold detection for HH3C-ENTITY-EXT-MIB.
Cheers
Thomas
Am 02.11.2017 um 16:11 schrieb Adam Armstrong:
We calculate them when they're not provided, some mibs do this (usually the extended entity-mibs) and some don't.
You can usually spot observium's autogen'd ones because they'll be weird decimals because of the maths. If they're whole numbers, they're probably from the device itself.
adam.
On 2017-11-02 15:09:19, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote:
Hi
I thought that the thresholds are automatically calculated and set by Observium and that the device itself doesn't provide them (only the sensor data).
Best, Thomas
Am 02.11.2017 um 14:43 schrieb Adam Armstrong:
That's most likely because your device is sending thresholds of zero. You can either get the vendor to fix this, or set manual thresholds.
Resetting the threshold only causes it to set it back to what the device is supplying. I'm not sure what other outcome you'd reasonably expect.
adam.
On 2017-11-02 10:25:20, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote:
Hi
Please see the attached screenshot. The thresholds are always 0 even after having the reset switch set.
Best, Thomas
Am 25.10.2017 um 21:42 schrieb Adam Armstrong:
It's not really clear what's happening, and you haven't told us what the "incorrect" thresholds are or why they're incorrect. Sensor thresholds are autogenerated as the returned value +/- a percentage when they're not supplied by the device.
The reset function just unsets any thresholds so that the next discovery process will either set them back to what the device supplies, or autogenerate them again.
The sensors in question should get their thresholds directly from the device :
// HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperature.8 = INTEGER: 50 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtTemperatureThreshold.8 = INTEGER: 85 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtCriticalTemperatureThreshold.8 = INTEGER: 95 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtLowerTemperatureThreshold.8 = INTEGER: -30 // HH3C-ENTITY-EXT-MIB::hh3cEntityExtShutdownTemperatureThreshold.8 = INTEGER: 65535
What values is your device returning?
adam.
On 2017-10-25 08:41:11, Thomas Stather thomas.stather@mpimf-heidelberg.mpg.de wrote:
Hi
I just noticed that one of our switches produces false positive errors because of incorrectly (auto) set thresholds for its sensors.
I then activated "reset sensors" on the sensors page of the device (there were no values for "min" and "max" set, the current temperature of the sensor is 44 degrees).
In the log i see:
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2535/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2535 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ SubCard0 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2534/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2534 SubCard0 [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2533/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2533 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
5m 42s swhp58-04 https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=logs/section=eventlog/ Board https://observium.mpimf-heidelberg.mpg.de/device/device=22/tab=health/metric=temperature/id=2532/ Sensor updated (custom): temperature hh3c-entity-ext-mib 2532 Board [L: Array][Lw: Array][Hw: Array][H: Array] (by user: tstather)
but the warnings are fired again. There is still no value for "min" or "max" for those sensors.
Attached is a screenshot.
What am i doing wrong here?
Thanks in advance!
Best, Thomas -- Thomas Stather IT Services
VCP4, VCP6-DCV
Tel: +49 6221-486 628 Fax: +49 6221-486 561
Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Thomas Stather IT Services
VCP4, VCP6-DCV
Tel: +49 6221-486 628 Fax: +49 6221-486 561
Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Thomas Stather IT Services
VCP4, VCP6-DCV
Tel: +49 6221-486 628 Fax: +49 6221-486 561
Max Planck Institute for Medical Research (MPImF) Jahnstrasse 29, 69120 Heidelberg Germany
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (2)
-
Adam Armstrong -
Thomas Stather