- observium - lists.observium.org

Alerts not being sorted chronological manner
by Youssef BENGELLOUN - ZAHR 14 Dec '16

14 Dec '16

1 2

How to remove unwanted ports
by Ivan Biasi 14 Dec '16

14 Dec '16

Hi all is it possible to remove, or hide, from the "Ports" panel of a device the interfaces for which the polling was disabled ? Thanks, regards I. -- ing. Biasi Ivan Area Ingegneria di Rete Direzione Servizi e Reti TRENTINO NETWORK S.R.L. Via G.Pedrotti, 18 – 38121 - TRENTO Tel : (+39) 0461.020222 Fax : (+39) 0461.020201 Email: ivan.biasi(a)trentinonetwork.it Skype: ivanbiasi https://www.linkedin.com/in/ivanbiasi ________________________________________________________________________________ Società soggetta a direzione e coordinamento da parte della Provincia Autonoma di Trento. REG. IMP. C.F. e P. IVA 01904880224 ________________________________________________________________________________ CONFIDENZIALE: Questo messaggio e gli eventuali allegati sono confidenziali e riservati. Se vi è stato recapitato per errore e non siete fra i destinatari elencati, siete pregati di darne immediatamente avviso al mittente. Le informazioni contenute non devono essere mostrate ad altri, nè utilizzate, memorizzate o copiate in qualsiasi forma. CONFIDENTIAL: This e-mail and any attachments to it may be confidential and may contain private and confidential information. If you are not the intended recipient of this email please notify the sender immediately. Moreover, you must not disclose or distribute its contents to anyone nor copy, store or use its contents in any way.

1 0

Power Supply Status Alarm Check
by Sebastian Klute 14 Dec '16

14 Dec '16

Hi there, I'm getting a bit confused while trying to create an alarm checker for power supply. So it's located under Status with physical class powersupply. Using the actual name would be worthless if this changes. What I want to check is the status of the status. Meaning running or not. I would go for status_type "powersupply" and status_event "running". If this is not true then give me an alarm. But I'm very unsure about the status_type and the correct one to check be cause an event could be "OK" or "FAIL" as well. The purpose is to track if any of the power supplys of our switches fails, so you can do an exchange before the whole switch goes offline. Hope anyone can help me with that. Best regards Sebastian Klute -- Accelerated IT Services GmbH Kruppstraße 105 - 60388 Frankfurt - Germany sk(a)accelerated.de - http://www.accelerated.de/ Phone: +49 69 - 900 180 41 - Fax: +49 69 - 900 180 90 HRB: 60665 - Amtsgericht Ludwigshafen - VatID: DE253684415 Managing Directors: Nicolaj Kamensek & Ole Krieger

1 0

Alert not working
by Eduardo Schoedler 13 Dec '16

13 Dec '16

Hi, I'm not understanding why this alert isn't working. [image: Imagem inline 2] BGP Session state: [image: Imagem inline 1] Thank you. Regards, -- Eduardo Schoedler

3 6

Re: [Observium] OpsGenie Observium Integration
by Halit Okumuş 09 Dec '16

09 Dec '16

Hi Adam, The current integration was made, months ago, according to your old webhook content. And there are existing, in-use configurations in OpsGenie at the moment. We can't just throw them away and change that, can we? That's why we suggested the webhook content before. I don't care how crappy your payload was, we're just trying to make use of the two products together. Alright, cooling down, we can do a rewrite. We'll make a V2 integration which will make use of the fields you mentioned and deprecate our old one. Can you send an example of that request to http://4kmm916oxm9m.runscope.net ? Cheers, Halit On Mon, Dec 5, 2016 at 3:37 PM, Çağla Arıkan <cagla(a)opsgenie.com> wrote: > > > Begin forwarded message: > > *From: *"Adam Armstrong" <adama(a)memetic.org> > *Subject: **Re: [Observium] OpsGenie Observium Integration* > *Date: *5 December 2016 at 15:33:44 GMT+3 > *To: *"" <observium(a)observium.org> > *Reply-To: *Observium Network Observation System <observium(a)observium.org> > > Oh god. I hate when you start looking through contributed code and realise > it was written by someone who hadn't even bothered to make sure it does > what it's supposed to do. > > At the moment the integration sends this payload : > > $payload = array( > "apiKey" => $endpoint['api_key'], > "message" => $message_tags['TITLE'], > "description" => $message_tags['METRICS'] . PHP_EOL . PHP_EOL . > 'Conditions: '. PHP_EOL . $message_tags['CONDITIONS'], > "alias" => $message_tags['ALERT_ID'], > "entity" => $message_tags['DEVICE_HOSTNAME'], > "source" => php_uname('n'), > "details" => array( > "Alert URL" => $message_tags['ALERT_URL'], > "Duration" => $message_tags['DURATION'], > "Hardware" => $message_tags['DEVICE_HARDWARE'], > "OS" => $message_tags['DEVICE_OS'], > "Location" => $message_tags['DEVICE_LOCATION'], > ), > ); > > We're able to supply these fields from our alerting code : > > 'ALERT_STATE' > 'ALERT_URL' > 'ALERT_ID' > 'ALERT_MESSAGE' > 'CONDITIONS' > 'METRICS' > 'DURATION' > 'ENTITY_LINK' > 'ENTITY_NAME' > 'ENTITY_TYPE' > 'ENTITY_DESCRIPTION' > 'ENTITY_GRAPHS_ARRAY' // Json encoded images array > 'DEVICE_HOSTNAME' > 'DEVICE_LINK' > 'DEVICE_HARDWARE' > 'DEVICE_OS' > 'DEVICE_LOCATION' > 'DEVICE_UPTIME' > > The existing integration doesn't seem to provide the actual entity being > alerted information in a useful manner, so could probably do with being > rewritten itself so we can better match the capabilities of the two > platforms. > > adam. > > On 05/12/2016 12:24:21, Adam Armstrong <adama(a)memetic.org> wrote: > Please don't use the generic webhook crap. There's a reason it's marked as > "(Old)" now. > > I get 400 bad request when using either of those URLs. Our OpsGenie > integration (which was contributed a couple of weeks ago) currently sends : > > {"recipients":"","api_key":"2f79c4d5-7c26-4429-8e5b-6e2b936800cc"} > {"apiKey":"2f79c4d5-7c26-4429-8e5b-6e2b936800cc","message":"RECOVER: [ > omega.memetic.org] [processor] [Average] Processor usage is above > 80%","description":"processor_usage = 40\n\nConditions: > \n","alias":"46864","entity":"omega.memetic.org","source":"o > mega.memetic.org","details":{"Alert URL":"http:\/\/dev.observium.org:80 > \/device\/device=12\/tab=alert\/alert_entry=46864\/","Duration":"1m 26s > (2016-12-05 13:20:00)","Hardware":"Generic x86 [64bit]","OS":"Linux > 3.13.0-96-generic Ubuntu 14.04","Location":"Hetzner, Nuremberg, Germany"}} > > Trying to parse an arbitrary text field is a really bad idea when we can > provide that data in separate fields. > > adam. > > On 05/12/2016 12:18:29, Çağla Arıkan <cagla(a)opsgenie.com> wrote: > When you change the URL, the integration will work properly. To make the > integration work properly, we should get the same payload that you send for > generic webhook integration this can be found below: > > { > "originator": "observium sender", > "body": "ALERT: [localhost] [device] device is down\ndevice_status = 0" > } > > We will fix the documents as you described. > > Thanks, > Çağla Arıkan > > On 5 Dec 2016, at 15:12, Adam Armstrong <adama(a)memetic.org> wrote: > > The description for the "add integration" part of OpsGenie also references > to deprecated generic webhook from Observium. Please don't use that. > > Please rewrite your integration to use the specific OpsGenie integration > we provide. > > adam. > > On 05/12/2016 12:03:49, Çağla Arıkan <cagla(a)opsgenie.com> wrote: > 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. > > Best Regards, > Çağla Arıkan > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > >

3 3

Router stopped polling via Observium
by Youssef BENGELLOUN - ZAHR 06 Dec '16

06 Dec '16

3 7

Weathermap module for observium
by Youssef BENGELLOUN - ZAHR 06 Dec '16

06 Dec '16

6 9

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