- observium - lists.observium.org

Sensor limit nominal and delta OIDs need different scaling
by Corwin Ziegler Hunts 18 Sep '24

18 Sep '24

Hi, We are trying to set appropriate limits for a frequency sensor. There are OIDs for the nominal frequency and the acceptable deviation from it. The problem is the nominal OID needs 0.1 scaling while the deviation OID needs 1 scaling (the measured value needs 0.1 scaling). Is there a way to handle this? We tried using 'limit_scale' but that applies the same scaling to both the nominal and delta limits. The specific device is a CyberPower ATS PDU. The OIDs are ePDU2SourceStatusSourceAFrequency, ePDU2SourceStatusSourceBFrequency, ePDU2SourceStatusNominalFrequency and ePDU2SourceConfigFrequencyDeviation. Corwin

1 0

API Error 500
by Nicolas Korten 18 Sep '24

18 Sep '24

Hello dear Observium Team, I'm trying to add a device using the API and get an error 500 message instead of the expected notice that the device is not respondig to snmp. > curl -u korten:secret https://observium.domain.net/api/v0/devices/ -X POST -d '{"hostname":"pe-lab02.domain.net", "snmp_community":"test", "ping_skip":"on"}' <h1>500 Internal Server Error</h1><h3>flight\Engine::_json(): Argument #2 ($code) must be of type int, string given, called in /opt/observium/libs/flight3/core/Dispatcher.php on line 86 (0)</h3><pre>#0 /opt/observium/libs/flight3/core/Dispatcher.php(86): flight\Engine->_json() #1 /opt/observium/libs/flight3/core/Dispatcher.php(50): flight\core\Dispatcher->runEvent() #2 /opt/observium/libs/flight3/Engine.php(113): flight\core\Dispatcher->run() #3 [internal function]: flight\Engine->__call() #4 /opt/observium/libs/flight3/core/Dispatcher.php(287): call_user_func_array() #5 /opt/observium/libs/flight3/Flight.php(143): flight\core\Dispatcher::invokeMethod() #6 /opt/observium/html/api/v0/includes/devices.inc.php(133): Flight::__callStatic() #7 [internal function]: api_add_device() #8 /opt/observium/libs/flight3/core/Dispatcher.php(250): call_user_func_array() #9 /opt/observium/libs/flight3/core/Dispatcher.php(237): flight\core\Dispatcher::callFunction() #10 /opt/observium/libs/flight3/Engine.php(508): flight\core\Dispatcher::execute() #11 /opt/observium/libs/flight3/core/Dispatcher.php(86): flight\Engine->_start() #12 /opt/observium/libs/flight3/core/Dispatcher.php(50): flight\core\Dispatcher->runEvent() #13 /opt/observium/libs/flight3/Engine.php(113): flight\core\Dispatcher->run() #14 [internal function]: flight\Engine->__call() #15 /opt/observium/libs/flight3/core/Dispatcher.php(287): call_user_func_array() #16 /opt/observium/libs/flight3/Flight.php(143): flight\core\Dispatcher::invokeMethod() #17 /opt/observium/html/api/v0/index.php(66): Flight::__callStatic() #18 {main}</pre> As far as I can see, the error is in: api/v0/includes/devices.inc.php at line 133: >Flight::json($json, '400'); should be: Flight::json($json, 400); Agree? Thank you and have a nice day, Nico -- Nicolas Korten Dipl.-Ing. Systemtechnik und Dienste/EDV komro GmbH Am Innreit 2 DE-83022 Rosenheim Telefon: +49 8031 365 7913 Telefax: +49 8031 365 7699 Mail: korten(a)komro.net / http://www.komro.net __________________________________________________________________________________________________________ Geschäftsführer: Dipl. Ing. Gert Vorwalder Vorsitz im Aufsichtsrat: Oberbürgermeister Andreas März Sitz der Gesellschaft: Rosenheim Registergericht: Traunstein, HRB-Nr. 10689 USt.-IdNr.: DE 188814299 Hinweise zur Verarbeitung Ihrer personenbezogenen Daten gem Art. 13 DSGVO: Verantwortlich für die Verarbeitung Ihrer personenbezogenen Daten im Rahmen des vorliegenden Kontakts ist die komro GmbH Weitere Informationen zur Verarbeitung Ihrer Daten, insbesondere zu den Ihnen zustehenden Rechten, können Sie unserer Homepage unter https://www.komro.net/datenschutz entnehmen oder auf jedem anderen Wege unter den o.g. Kontaktdaten bei uns erfragen.

4 7

Group section not working in Status Summary widget
by Ricardo Puig 16 Sep '24

16 Sep '24

Dear Observium Team, The group section in Status Summary widget is pointing to nowhere (javascript:void(0)) Regards.

1 0

NAT Counters Cisco
by Arnoldo Vidal Bravo 12 Sep '24

12 Sep '24

Hi. How can I get a NAT's sessions total from Cisco ASR-1002X? We get SNMP results by snmp v2 and Observium version is 23.8.12.912. I must enable NAT MIB, but ¿where is an example? NAT MIB can be enable after add the device? -- Saluda cordialmente

2 1

Hello.
by Bar Russo 12 Sep '24

12 Sep '24

I want to subscribe because I need some help with the metrics of the Observium. [cid:image001.png@01DB04FB.F42B1C50] בר רוסו | מערכות מידע מייל: barr(a)mgrp.co.il<mailto:barr@mgrp.co.il> קבוצת Mgroup | אריאל שרון 8, אור יהודה www.mgrp.co.il<http://www.mgrp.co.il>

2 2

Alert Checker association "Storage Description" major problem
by kalafus＠energotel.sk 10 Sep '24

10 Sep '24

Hello, Creating storage alert checker using entity association "Storage Description" renders page https://observium.xxx.sk/alert_checks/ totally unavailable (just blank whole page). Deleting that alert makes it work again. Looking for a solution...

3 4

Unix agent not working on non-default port
by ricardo＠banak.com 10 Sep '24

10 Sep '24

We have several devices behind a NAT that require using an agent_port other than 36602. Even though I have changed the port in the GUI, the poller seems to continue using the standard port. It seems to me that $device['attribs']['agent_port'] has not been populated. Running 24.9.13634 Pro on debian 12. Thank you. Ricardo Puig

2 2

The graphs for few network devices not getting displayed
by Renuka Arya 09 Sep '24

09 Sep '24

Hi Team! We are running Observium pro version Observium 24.6.13582(stable). Lookslike the memory,processor and network graphs are seeing a draw error. You can still the values beside but it wont draw the graphs. It says "Draw error"/nan I looked into the permissions for the rrd folders for these devices and did change a non-working one similar to a working one as root:observium but that did not fix the issue. I also tried deleting (which was not ideal) a device and adding it back but that did not work as well. Please guide! Thanks! Regards Renuka Arya

3 4

Incorrect sensor limits caused by duplicate unit conversion
by Corwin Ziegler Hunts 04 Sep '24

04 Sep '24

The definition for the temperature sensor on a CyberPower PDU (or UPS) environmental sensor accessory defines both "unit" and "limit_unit" as "F". This seems to cause the limit values to get converted (to Celsius) twice: first in "entity_limits_definition" using "limit_unit" and then in "discover_sensor_ng" using "sensor_unit" which is set from "unit". For us, the SNMP read limits of 59 and 90 F end up as -9.44 and 0.12 C on the sensor in Observium. This is on version r13629. Simply not setting "limit_unit" is a workaround if both the sensor and limit values use the same unit (maybe that is preferred when defining sensors?). If the units are different a proper fix is needed. Also, is this the preferred method for reporting this kind of issue? Corwin

2 3

How to add a device which only responds to ping/icmp?
by Thomas Stather 23 Aug '24

23 Aug '24

Hi How can i add a device which cannot (!) speak any snmp and only responds to ping/icmp requests? We have an Aruba wlan setup (Mobility Master and two Mobility Controllers) and i want to add the aps to Observium, so that they are monitored but only by ping/icmp. (The MM and the two MCs are already added to Observium, but i cannot see if one AP went offline or came back online again) The aps cannot speak any snmp when managed by the MM or MC, thats why it fails when i try to add one via ./add_device.php I appreciate any help :) Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!

10 15