- observium - lists.observium.org

Question about port desr on Fortigate
by MORDAC, Benoit 06 Dec '16

06 Dec '16

Hi, I'm using the Observium professional edition, and I monitor a lot of things, including some Fortigate firewalls. I have upgraded one of them from FortiOS 5.2.x to 5.4.2 release, After this upgrade, observium don't show interfaces names or description. When calling the discovery.php script we should see the port name. ##### Module Start: ports ##### o Caching OIDs ifDescr ifAlias ifName ifType ifOperStatus o Caching DB 46 ports o Discovering ports .............................................. +---------+---------+----------+----------+----------+-------------+---------+ | ifIndex | ifDescr | ifName | ifAlias | ifType | Oper Status | Ignored | +---------+---------+----------+----------+----------+-------------+---------+ | 1 | ... | port1 | ... | ethernet | up | no | | | | | | Csmacd | | | | 2 | ... | port2 | ... | ethernet | down | no | | | | | | Csmacd | | | | 3 | ... | port3 | ... | ethernet | up | no | | | | | | Csmacd | | | ... But it's not visible in the web UI. Maybe it's possible to force Observium to use ifName instead of ifDescr attribute ? I have made a "svn update" on my observium install, the problem is still present. Thanks for your help. Best Regards,

3 2

Intel True Scale Fabric Switch 12800 support
by Jesper Frank Nemholt 05 Dec '16

05 Dec '16

Hi! I wonder if anyone are working on adding support for these devices ? They are QLogic (now Intel) InfiniBand switches and are used on most larger Isilon clusters. The OID is enterprises.10222 I've previously monitored Mellanox IB switches like the SX6036 and these have a good integration, but the Intel ones only report on the management interfaces and nothing else....and I prefer not to spend a day adding support myself if someone else already have done most of the work. snmpwalk -v 2c -c public foo.bar system SNMPv2-MIB::sysDescr.0 = STRING: Intel True Scale Fabric Switch 12800-040 (Master) SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.10222.7.1.2 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (30516852) 3 days, 12:46:08.52 SNMPv2-MIB::sysContact.0 = STRING: SNMPv2-MIB::sysName.0 = STRING: QLogic 12800-040-254 SNMPv2-MIB::sysLocation.0 = STRING: Main Chassis Unit, Slot 254 SNMPv2-MIB::sysServices.0 = INTEGER: 79 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORID.1 = OID: SNMPv2-SMI::mib-2 SNMPv2-MIB::sysORID.2 = OID: SNMPv2-SMI::mib-2.17 SNMPv2-MIB::sysORID.3 = OID: SNMPv2-MIB::snmpMIB SNMPv2-MIB::sysORID.4 = OID: IF-MIB::ifMIB SNMPv2-MIB::sysORID.5 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIB SNMPv2-MIB::sysORID.6 = OID: SNMP-MPD-MIB::snmpMPDMIB SNMPv2-MIB::sysORID.7 = OID: SNMP-TARGET-MIB::snmpTargetMIB SNMPv2-MIB::sysORID.8 = OID: SNMP-NOTIFICATION-MIB::snmpNotificationMIB SNMPv2-MIB::sysORID.9 = OID: SNMPv2-SMI::transmission.7 SNMPv2-MIB::sysORID.10 = OID: SNMPv2-SMI::mib-2.17.6 SNMPv2-MIB::sysORID.11 = OID: SNMPv2-SMI::mib-2.17.7 SNMPv2-MIB::sysORDescr.1 = STRING: RFC 1213 - (AT, IP, ICMP, TCP, UDP groups) SNMPv2-MIB::sysORDescr.2 = STRING: RFC 1493 - BRIDGE-MIB SNMPv2-MIB::sysORDescr.3 = STRING: RFC 1907 - SNMPv2-MIB (SYSTEM, SNMP) SNMPv2-MIB::sysORDescr.4 = STRING: RFC 2233 - IF-MIB (IF) SNMPv2-MIB::sysORDescr.5 = STRING: RFC 2571 - SNMP-FRAMEWORK-MIB SNMPv2-MIB::sysORDescr.6 = STRING: RFC 2572 - SNMP-MPD-MIB SNMPv2-MIB::sysORDescr.7 = STRING: RFC 2573 - SNMP-TARGET-MIB SNMPv2-MIB::sysORDescr.8 = STRING: RFC 2573 - SNMP-NOTIFICATION-MIB SNMPv2-MIB::sysORDescr.9 = STRING: RFC 2665 - EtherLike-MIB SNMPv2-MIB::sysORDescr.10 = STRING: RFC 2674p - P-BRIDGE-MIB SNMPv2-MIB::sysORDescr.11 = STRING: RFC 2674q - Q-BRIDGE-MIB SNMPv2-MIB::sysORUpTime.1 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.2 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.3 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.4 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.5 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.6 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.7 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.8 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.9 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.10 = Timeticks: (1883) 0:00:18.83 SNMPv2-MIB::sysORUpTime.11 = Timeticks: (1883) 0:00:18.83 /Jesper

1 0

OpsGenie Observium Integration
by Çağla Arıkan 05 Dec '16

05 Dec '16

Hi there, I am a software engineer at OpsGenie. We have developed an integration specific to Observium. Thus, we would be very pleased if you can fix your integration so that it uses /v1/json/observium endpoint rather than /v1/json/alert endpoint. Observium Integration works similar to generic Webhook integration but we customised it for Observium. You can check our Observium Integration document for more information which can be found at https://www.opsgenie.com/docs/integrations/observium-integration <https://www.opsgenie.com/docs/integrations/observium-integration>. Best Regards, Çağla Arıkan

2 5

Interface errors Observium Subscription version
by Afzaal Shabbir 03 Dec '16

03 Dec '16

Dear All, Will it be possible for anyone to help me understand about attached error message on Access Points Wifi interfaces, what they mean and how to fix these errors or where to look for answers regarding these errors. Both interface graphs attached. These are graphs unifi access points wifi0 and wifi1 interfaces. There are no error messages on it's physical interface. Thanks, A

1 0

Minute storage changes causing storm of "Storage Size Change" messages
by Cody Cook 02 Dec '16

02 Dec '16

I am on 0.16.12.8277 and noticed that I am getting new alerts on the eventlog. Just this week alone, there are 82.8k items about storage changing. My volumes are generally zfs with many subvolumes, and as a result, all entries are coming up in the eventlog. This also wipes away any other important changes that might be overlooked. [image: Inline image 1]

1 0

OpenConfig Telemetry?
by Johann Mallet 02 Dec '16

02 Dec '16

Hello, Do you know if exist an plan for integrate Openconfig Telemetry in Observium in the future? A few reference links: http://www.openconfig.net/projects/streaming-telemetry/ https://github.com/openconfig/reference/tree/master/telemetry Juniper (and Cisco?) will integrate this technology in the next release. Thanks! Johann

1 0

No polling
by Martin Snygg 02 Dec '16

02 Dec '16

Hi I just discovered that my install stopped polling since a couple of days, I think it´s because a svn switch I did. When running the poller-wrapper.py I get the following: Traceback (most recent call last): File "./poller-wrapper.py", line 306, in <module> if instances_count > 1 and instance_number >= 0 and (instance_number < instances_count): NameError: name 'instances_count' is not defined Where do I define "instance_count" and how? /Martin Snygg

3 13

Memory alerting false positives
by Musall, Maik 01 Dec '16

01 Dec '16

Hi, I have an alert on a linux server configured for "mempool_perc gt 90", which is firing all the time because of irrelevant caching use. Memory on Linux is always used. I'm more interested in the orange part of this graph: The device is called ucd_memory. Is there a metric I can use to get the value that's at 61% in this graph, to catch spikes like the one at 14:00 time? Thanks Maik

2 1

Re: [Observium] poller duration
by Youssef BENGELLOUN - ZAHR 01 Dec '16

01 Dec '16

5 5

poller duration
by Vater, Wolfgang 01 Dec '16

01 Dec '16

Is there a way to see which module is taking all the time when polling a device? I have Nexus 5000 switches with lots of ports, so I assume it the ports that take most of the time, but I would like to see what else takes a lot of time and if I can live without that information and disable the polling for it (like fdbcount). My N5Ks take 400 sec on average. Wolfgang Vater | Lead Client Architect | Enterprise Services Unisys Deutschland GmbH | +49 162 255 9338 | wolfgang.vater(a)unisys.com | Philipp-Reis-Str. 2 | 65795 Hattersheim [unisys_logo]<http://www.unisys.com/> Unisys Deutschland GmbH | Geschäftsführer: Sandro Lindner & Dr. Uwe Heckert | Sitz der Gesellschaft: Hattersheim | Amtsgericht: Frankfurt/Main HRB 7929 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. DIESE E-MAIL IST AUSSCHLIESSLICH FÜR DEN ADRESSATEN BESTIMMT UND KANN VERTRAULICHE INFORMATIONEN ENTHALTEN. Sollten Sie nicht der Adressat dieser Informationen sein, bitten wir Sie, sich mit dem Absender in Verbindung zu setzen und die Informationen von Ihren Endgeräten zu entfernen. [Grey_LI]<http://www.linkedin.com/company/unisys> [Grey_TW] <http://twitter.com/unisyscorp> [Grey_GP] <https://plus.google.com/+UnisysCorp/posts> [Grey_YT] <http://www.youtube.com/theunisyschannel> [Grey_FB] <http://www.facebook.com/unisyscorp> [Grey_Vimeo] <https://vimeo.com/unisys> [Grey_UB] <http://blogs.unisys.com/>

2 1