- observium - lists.observium.org

Temperature sensor question
by Kleber Cristiano Santilli Coelho 30 Sep '22

30 Sep '22

Good Morning! I hope you're all well. I apologize if the question is inappropriate. I'm developing an IOT module and I use the "ENTITY" MIB for the sensors. I saw that Observium handles this MIB automatically, using the entPhySensorType OID to distinguish the sensor types and it works great, except for the temperature sensor, entPhySensorType value 8. I would like to understand if this has any special reason to adapt my code. Thank you, congratulations on the software. -- Kleber Coelho Campus Fernando Costa Universidade de São Paulo (19) 3565-4321

3 10

APC's universal I/O (UPS temp/humidity sensors) not showing in
by Steve Costaras 26 Sep '22

26 Sep '22

Have observium polling various APC ups's (AP9631 NMC cards). Observium correctly polls the battery temperatures, but when adding in probes to the universal I/O ports on the AP9631 (just trying with the temp sensor currently) I do not see the data being plotted on observium. Is this supposed to work? I don't have the humidity sensor currently (was trying to test with the temp sensor first before buying the temp/humidity combined sensors for the units). Would really like to get this data tracked for environmental data logging per rack (have a ups per rack). The data does show up in an snmpwalk: # snmpbulkwalk -v2c -c xxx yy.yy.yy.yy .1.3.6.1.4.1.318.1.1.25.1 iso.3.6.1.4.1.318.1.1.25.1.1.0 = INTEGER: 2 iso.3.6.1.4.1.318.1.1.25.1.2.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.2.1.1.2.1 = INTEGER: 2 iso.3.6.1.4.1.318.1.1.25.1.2.1.2.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.2.1.2.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.2.1.3.1.1 = STRING: "Port 1 Temp 1" iso.3.6.1.4.1.318.1.1.25.1.2.1.3.2.1 = STRING: "Port 2 Temp 2" iso.3.6.1.4.1.318.1.1.25.1.2.1.4.1.1 = STRING: "Port 1" iso.3.6.1.4.1.318.1.1.25.1.2.1.4.2.1 = STRING: "Port 2" iso.3.6.1.4.1.318.1.1.25.1.2.1.5.1.1 = INTEGER: 75 iso.3.6.1.4.1.318.1.1.25.1.2.1.5.2.1 = INTEGER: 90 iso.3.6.1.4.1.318.1.1.25.1.2.1.6.1.1 = INTEGER: 24 (Port 1 temp 1 sensor in C) iso.3.6.1.4.1.318.1.1.25.1.2.1.6.2.1 = INTEGER: 32 (port 2 temp 2 sensor in C) iso.3.6.1.4.1.318.1.1.25.1.2.1.7.1.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.2.1.7.2.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.2.1.8.1.1 = INTEGER: 0 iso.3.6.1.4.1.318.1.1.25.1.2.1.8.2.1 = INTEGER: 0 iso.3.6.1.4.1.318.1.1.25.1.2.1.9.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.2.1.9.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.2.1.10.1.1 = INTEGER: 2 iso.3.6.1.4.1.318.1.1.25.1.2.1.10.2.1 = INTEGER: 2 iso.3.6.1.4.1.318.1.1.25.1.3.0 = INTEGER: 2 iso.3.6.1.4.1.318.1.1.25.1.4.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.1.2.1 = INTEGER: 2 iso.3.6.1.4.1.318.1.1.25.1.4.1.2.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.2.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.3.1.1 = STRING: "Port 1 Temp 1" iso.3.6.1.4.1.318.1.1.25.1.4.1.3.2.1 = STRING: "Port 2 Temp 2" iso.3.6.1.4.1.318.1.1.25.1.4.1.4.1.1 = STRING: "Port 1" iso.3.6.1.4.1.318.1.1.25.1.4.1.4.2.1 = STRING: "Port 2" iso.3.6.1.4.1.318.1.1.25.1.4.1.5.1.1 = INTEGER: 0 iso.3.6.1.4.1.318.1.1.25.1.4.1.5.2.1 = INTEGER: 0 iso.3.6.1.4.1.318.1.1.25.1.4.1.6.1.1 = INTEGER: 10 iso.3.6.1.4.1.318.1.1.25.1.4.1.6.2.1 = INTEGER: 10 iso.3.6.1.4.1.318.1.1.25.1.4.1.7.1.1 = INTEGER: 40 iso.3.6.1.4.1.318.1.1.25.1.4.1.7.2.1 = INTEGER: 40 iso.3.6.1.4.1.318.1.1.25.1.4.1.8.1.1 = INTEGER: 60 iso.3.6.1.4.1.318.1.1.25.1.4.1.8.2.1 = INTEGER: 60 iso.3.6.1.4.1.318.1.1.25.1.4.1.9.1.1 = INTEGER: 0 iso.3.6.1.4.1.318.1.1.25.1.4.1.9.2.1 = INTEGER: 0 iso.3.6.1.4.1.318.1.1.25.1.4.1.10.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.10.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.11.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.11.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.12.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.12.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.13.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.13.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.14.1.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.14.2.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.15.1.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.15.2.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.16.1.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.16.2.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.17.1.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.17.2.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.18.1.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.18.2.1 = INTEGER: -1 iso.3.6.1.4.1.318.1.1.25.1.4.1.19.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.19.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.20.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.20.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.21.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.21.2.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.22.1.1 = INTEGER: 1 iso.3.6.1.4.1.318.1.1.25.1.4.1.22.2.1 = INTEGER: 1

3 4

HP A7510 JD238B and FDB count
by Kleber Cristiano Santilli Coelho 19 Sep '22

19 Sep '22

Hello everyone, everything good? I have an HP A7510 JD238B core switch that is not generating the FDB count graph in the observium. Does anyone have any tips for it to work? In the graphs section, the fdb_count graph does not appear. Thanks, -- Kleber Coelho Campus Fernando Costa Universidade de São Paulo (19) 3565-4321

1 0

Distro version changing continuously
by Simone Montagnani 19 Sep '22

19 Sep '22

Hi all, I'm writing because after the latest update I'm noticing that a lot of my servers Linux , specifically CentOS servers, are umping in the event log from CentOS to Redhat and viceversa. Is there something I can do to avoid this ? Simone

2 2

Huawei 6851 CPU Monitoring
by Farshid Abediny 14 Sep '22

14 Sep '22

Hello, My observium can not monitor Huawei 6851 CPU usages, is there any special settings for this? Thank you.

1 0

Huawei 6851
by Farshid Abediny 12 Sep '22

12 Sep '22

Hello, We have a pair of huawei 6851 but observium can not monitor the interface vlan traffics, What is the problem and how can we solve this problem? Thanks.

2 2

upgrading older versions
by Helmut Fritz 11 Sep '22

11 Sep '22

Hello, We have an instance of Observium running on Ubuntu 16.04. I would like to bring this OS somewhat current, say to 20.04 or maybe even 22.04. At the same time, our Observium version on this is 20.1.10233. Would there be an issue upgrading the OS with the current version of Observium running on them? I know a fresh install would be best, but then what is the migration procedure? Are all alerts and configurations moved in the migration (I would assume so, but want to understand this as it is a lot of work to recreate all of this). Is there an issue going in one jump from 20.1.10233 to latest, or should this be done in stages? Should Observium or the OS be dealt with first (concerned about php/mysql versions matching Observium versions, etc)? We are a Pro subscriber if it matters. Thx!

2 4

Prices / availibility
by Arnoldo Vidal Bravo 31 Aug '22

31 Aug '22

Hi, before a years ago we purchased a Professional edition, We have a question to get a Enterprise version. we need monitor much more devices. -- Saluda cordialmente

3 4

question about alert checker TEST
by Edvinas Kairys 27 Aug '22

27 Aug '22

Hello, I'm using alert checker with quite standard check: ifInOctets_perc ge 90 ifOutOctets_perc ge 90 But sometimes the SNMP returns incorrect value like 134651%, especially in Nexus devices. I would like to prevent that with inserting test value like: ifInOctets_perc le 100. But i'm wondering if it's possible to do this in single rule in Observium that would look like this: (ifInOctets_perc ge 90 and ifInOctets_perc le 100) or (ifOutOctets_perc ge 90 and ifOutOctets_perc le 100) Or i need to create separate rules for both groups ? Thanks

2 1

Stormshield issues
by Luca Sasdelli 27 Aug '22

27 Aug '22

Hi, on several Stormshield firewalls, I read some issues: * the firewalls are detected as Generic devices, while some time ago they were correctly detected as Stormshield firewalls * some ports report wrong speed: e.g. on 8 gigabit ports same appliance, some appears with 4Mbps, 20Mbps or 1Gbps, even by correcting them in its properties The second one isn't simply a cosmetic issue, because threshold alerts are generated with ordinary traffic. Best LS

2 2