- observium - lists.observium.org

Software raid
by Simon Mousey Smith 20 Dec '16

20 Dec '16

Hi All, Daft question, we have a voip server with software raid in (FreePBX) Does Observium monitor the software raid? I see in the Observium_agent script it does ‘cat /proc/mdstat’ But what does it do? I can’t see any graphs or sensors for the raid? Only the md IO graphs? Regards Simon

3 2

trial observium
by ridwanfi 20 Dec '16

20 Dec '16

hi all, has been using observium for few days and we need to test the trial alert or notification, i know you guys don't provide trial license http://observium.observium.narkive.com/Ra0jsd8Z/professional-version-on-tri… hence if i need to buy subscription or contact sales team whom should I wrote to rgds Ridwan

2 1

NET ISO Routing support
by ecmp 20 Dec '16

20 Dec '16

NET ISO Routing support, debain 8 install, Observium CE 0.16.10.8128 Hi, I'm having trouble getting ISIS to work in observium. I apoligize if this has already been a topic in the email archive, but I was unable to view the archive and I couldn't find anything online relating to this. bgp, ospf, eigrp are all show in the edit-->routing section of the webui. Not ISIS. I know under poller discover modules these exist // Poller/Discovery Modules $config['enable_bgp'] = 1; // Enable BGP session collection and display $config['enable_rip'] = 1; // Enable RIP session collection and display $config['enable_ospf'] = 1; // Enable OSPF session collection and display $config['enable_isis'] = 1; // Enable ISIS session collection and display $config['enable_eigrp'] = 1; // Enable EIGRP session collection and display $config['enable_syslog'] = 0; // Enable Syslog $config['enable_vrfs'] = 1; // Enable VRFs $config['enable_sla'] = 1; // Enable SLA/RPM collection and display $config['enable_pseudowires'] = 1; // Enable Pseudowires digging a bit further, I found that uncommenting this section of the file ./includes/config-variables.inc.php would enable this setting on the webui. However isis data is still not collected and does not show up under device>routing. /// ROUTING ////////////////////////////////////////////////////////// $config_sections['routing']['text'] = "Routing"; $setting = 'enable_isis'; $config_variable[$setting]['section'] = "routing"; $config_variable[$setting]['subsection'] = "Protocols"; $config_variable[$setting]['name'] = "ISIS sessions"; $config_variable[$setting]['type'] = "bool"; $config_variable[$setting]['shortdesc'] = "Enable collection and display of ISIS data."; one thing I noticed is the bgp, ospf, and eigrp all have the name set to "<protocol> collection" while rip and isis have the name "<protocol> sessions." Finding these settings without a comment like "/* Unimplemented :)" makes me think that ISIS is supported, however I can't seem to find an existing module to support it within the CE. a quick grep of the observium directories seems to show that isis is lacking a poller module like: ./includes/polling/cisco-eigrp.inc.php ./includes/polling/ospf.inc.php ./includes/discovery/bgp-peers.inc.php grep -r 'isis' . (with a lot of output ommited) ./tests/HtmlIncludesFunctionsTest.php: array('isis', 'IS-IS'), ./includes/config-variables.inc.php:$setting = 'enable_isis'; ./includes/defaults.inc.php:$config['enable_isis'] = 1; // Enable ISIS session collection and display ./includes/definitions.inc.php:$config['routing_types']['isis'] = array('text' => 'ISIS'); Does anyone have ISIS working in observium? If so how? Thanks.

2 3

Problem with MIBs
by Xavier Bonell 16 Dec '16

16 Dec '16

Hello; I recently have installed the Community version of Observium on a CentOS 7 server, to test the functionalities and the configurations that gives; to decide if I it's worth to purchase for the Professional one. My question is about how can I select wich MIBs is going to use to obtain data. Because when I go to Devices -> Select Device -> Properties -> MIBs I find a list of MIBs that are used but not suitable for my device. How can I change it? Entering through the server's folders I have seen that are the MIBs that I need. How can I run it to get the appropiate data? Thanks!

2 3

Unable to sort rows by the last column for some data types
by Andy Lemin 15 Dec '16

15 Dec '16

Hi, At the risk of embarrassing myself again and making you laugh, for an obvious typo.. ;) And yes I have definitely checked this time I discovered this weekend that it is not possible to view some of the "Heath" charts in a sorted order. For example, Heath -> Temperature -> Click "Value". The rows seem to be sorted randomly for us. Is anyone else seeing this too? The following also all have the same problem 1) Health -> Processor -> Click "Processor" to sort by processor name, results in random sorting 2) Health -> Memory -> Click "Memory" to sort by Memory name, results in random sorting 3) Health -> Memory -> Click "Used" to sort by Used, results in very random sorting 4) Health -> Temperature -> Click "Value" to sort by temp, results in very random sorting 5) Health -> Fanspeed -> Click "Value" to sort by temp, results in very random sorting 6) Health -> Power -> Click "Value", results in random sorting Cheers, Andy.

4 5

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