- observium - lists.observium.org

Setting up Observium as a Virtual Directory
by Norris Ward 05 Nov '13

05 Nov '13

Hi all, I am trying to setup Observium in a proof of concept environment. When I try to make it a virtual directory on the linnux Debian server, the attached webpage is what I get compared to when i make the web root that of the observium html path. How can I fix this?

3 2

Re: [Observium] Error drawing Graph
by Adam Armstrong 05 Nov '13

05 Nov '13

I monitor devices with 100ms+ latency, so that isn't a problem. More of a problem is badly written SNMP stacks :-( Adam Roman <rromanyak(a)squarespace.com> wrote: >Thanks Adam for your feedback, I'll upgrade observing yo the latest version, if it still doesn't work than I'll just install it locally in the remote data center and see if it works there > >Roman > >Sent from my iPhone > >> On Oct 30, 2013, at 9:11 PM, Adam Armstrong <adama(a)memetic.org> wrote: >> >>> On 2013-10-30 17:44, Roman Romanyak wrote: >>> Hello everyone, >>> I'm having strange issue, and spend a lot of time troubleshooting this >>> without any success. >>> Getting error 'error drawing graph' only for some devices only - >>> EX4200 switches, which are located in the remote datacenter. After I >>> started seeing issue, I install another switch here in local >>> datacenter and added it to observium and its working good. Could be >>> the issue in latency - the delay is about 30ms? >>> discovery and poller scripts run good, the only thing I noticed that >>> for the devices that don't work I in rrd/<device_name>/ files >>> port-###.rrd are missing. The CPU and Memory graphs are working good, >>> only network graphs are having errors. >> >> Make sure you're running the latest version, there were some issues with a change earlier this week. >> >> JunOS is a special little butterfly and needs special attention sometimes... >> >> Latency won't really have that effect, the only thing that is likely to is failing to receive data from the switch, which may be fixed in the latest revisions. >> >> adam. >> _______________________________________________ >> 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

2 2

observium just stops after switching to subscription.
by Thomas Raabo - Zitcom A/S 04 Nov '13

04 Nov '13

If i run discovery.php -h none I get no output. The only way I could get it going again was to uncomment this line in common.php if (file_exists($config['install_dir']."/includes/debug/ref.inc.php")) { include($config['install_dir']."/includes/debug/ref.inc.php"); $ref_loaded = TRUE; } Whats my problem? I´am running centos. Thomas

3 8

new feature request
by Rob VanHooren 04 Nov '13

04 Nov '13

Tom/Mike I suggest to implement this new feature for Adam, ASAP: http://www.thewhiskyexchange.com/P-19856.aspx ;-) R. On Nov 3, 2013, at 17:13, observium-request(a)observium.org wrote: > Either read what's come before, or say nothing. > > FUCKING HELL.

4 3

Re: [Observium] observium Digest, Vol 40, Issue 9
by Corey Robertson 04 Nov '13

04 Nov '13

I think the majority of these complaints have come from users who have forgotten this is a grassroots, homegrown effort, which single handedly out performs many other NMS systems albeit paid or free. If you expect answers and resolution to every minute detail which you don't like, put you money where your mouth is. The Observium team has been more than gracious to continue to develop such a great monitoring platform and keep it going while still maintaining the open source ideals. > On Nov 3, 2013, at 4:13 PM, observium-request(a)observium.org wrote: > > Send observium mailing list submissions to > observium(a)observium.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > or, via email, send a message with subject or body 'help' to > observium-request(a)observium.org > > You can reach the person managing the list at > observium-owner(a)observium.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of observium digest..." > > > Today's Topics: > > 1. Re: Fwd: Regarding developers attitude... (Adam Armstrong) > 2. Re: Fwd: Regarding developers attitude... (Adam Armstrong) > 3. Re: Fwd: Regarding developers attitude... (Doychin Dokov) > 4. Re: observium just stops after switching to subscription. > (Tom Laermans) > 5. Re: Fwd: Regarding developers attitude... (Tom Laermans) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 03 Nov 2013 21:43:01 +0000 > From: Adam Armstrong <adama(a)memetic.org> > To: Observium Network Observation System <observium(a)observium.org> > Subject: Re: [Observium] Fwd: Regarding developers attitude... > Message-ID: <fde9ac9c729e4be8f2eebf3be002bb08(a)memetic.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Fuck off, cuntmuppet. > > Either read what's come before, or say nothing. > > FUCKING HELL. > > >> On 2013-11-03 20:52, Tom Henderson wrote: >> Maybe take it offline gents? Of at least off list? http://xkcd.com/438/ >> [1] >> >> A simple "Hi $user, this is covered on the wiki here: $url. Thanks for >> using observium." would be trivial to implement with any email >> templating system. Even "Sorry, $feature is not currently in the >> timeline because of $reasons." would be better than getting in an >> argument. >> >> Cheers >> >> Tom >> >> -- >> >> ------------------------- >> >> If you are not the intended recipient of this email, you must not >> disclose, copy, or distribute any information contained in or attached >> to it, or take any action/inaction based on it. Please contact us >> immediately, and delete this email from your system. Any views or >> opinions presented in this email are solely those of the author and >> not of Pack & Company (NZ) Limited (the "Company"), however any >> intellectual property contained in or attached to this email is the >> property of the Company. Thank you. >> >> Links: >> ------ >> [1] http://xkcd.com/438/ >> >> _______________________________________________ >> observium mailing list >> observium(a)observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > > ------------------------------ > > Message: 2 > Date: Sun, 03 Nov 2013 21:44:16 +0000 > From: Adam Armstrong <adama(a)memetic.org> > To: Observium Network Observation System <observium(a)observium.org> > Subject: Re: [Observium] Fwd: Regarding developers attitude... > Message-ID: <80652049ab831e346e2bec554d8ee638(a)memetic.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > >> On 2013-11-03 21:40, Doychin Dokov wrote: >> As my first message says, I've tried to contact Adam on his personal >> e-mail to get an idea for the reason for this attitude, to no avail. >> >> One more time, I've not requested a new feature or anything else, I >> just reported an already-existing part of observium not looking >> correctly, asked if it's a leftover and planned to be reworked, as the >> similar BGP stats look fine, and even offered to work on it. >> >> There are no $reasons for such $attitude, and it's not the first time >> it happens, so I wanted to know why, and how is this considered >> normal? > > You did none of those things. > > So now i'm going to add liar to the list of reasons why we will no > longer accept any communication from you. > > adam. > > > ------------------------------ > > Message: 3 > Date: Mon, 4 Nov 2013 00:04:59 +0200 > From: Doychin Dokov <dokov(a)silistra.tv> > To: Observium Network Observation System <observium(a)observium.org> > Subject: Re: [Observium] Fwd: Regarding developers attitude... > Message-ID: > <CALD-xbC4JXP68OFZdJmCcwy-ysN=o3pHjstd=LpujhZADRFGow(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Adam, > > Everyone would have seen with their eyes what I have offered, if you have > not deleted the issue in jira! > > Also, I have pasted my exact reply in my first email, here it is once again: > > "Now that Observium is paid, we deserve some proper attention to problems, > at least.... Not just the close-it-as-fast-as-you-can attitude you have so > far.... > > Also, I'm more than willing to fix it myself by looking at the BGP code, so > was jast curios if there is any plan to already rework the OSPF pages, as > what is seen on the screenshot is really of no use - and I guess your > opinion is the same as well." > > > I'm very much sure you have read it, as you and Tom Laermans have replied > to it that i have no idea what I have paid for.... > > So, naming me a "liar" is completely inappropriate, and is a true > confirmation about your inability to communicate normally with people. You > are digging observium's grave. > > - D. > > > > > 2013/11/3 Doychin Dokov <dokov(a)silistra.tv> > >> As my first message says, I've tried to contact Adam on his personal >> e-mail to get an idea for the reason for this attitude, to no avail. >> >> One more time, I've not requested a new feature or anything else, I just >> reported an already-existing part of observium not looking correctly, asked >> if it's a leftover and planned to be reworked, as the similar BGP stats >> look fine, and even offered to work on it. >> >> There are no $reasons for such $attitude, and it's not the first time it >> happens, so I wanted to know why, and how is this considered normal? >> >> - D. >> >> >> 2013/11/3 Tom Henderson <tom(a)pack.co.nz> >> >>> Maybe take it offline gents? Of at least off list? http://xkcd.com/438/ >>> >>> A simple "Hi $user, this is covered on the wiki here: $url. Thanks for >>> using observium." would be trivial to implement with any email templating >>> system. Even "Sorry, $feature is not currently in the timeline because of >>> $reasons." would be better than getting in an argument. >>> >>> Cheers >>> >>> Tom >>> >>> >>> -- >>> >>> >>> ------------------------------ >>> If you are not the intended recipient of this email, you must not >>> disclose, copy, or distribute any information contained in or attached to >>> it, or take any action/inaction based on it. Please contact us immediately, >>> and delete this email from your system. Any views or opinions presented in >>> this email are solely those of the author and not of Pack & Company (NZ) >>> Limited (the "Company"), however any intellectual property contained in or >>> attached to this email is the property of the Company. Thank you. >>> >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >

1 0

Minor OSPF page fixes
by Sander Steffann 03 Nov '13

03 Nov '13

So, here are a few minor quick fixes to device/routing/ospf. I hope this lessens the tension here a bit. Index: html/pages/device/routing/ospf.inc.php =================================================================== --- html/pages/device/routing/ospf.inc.php (revision 4732) +++ html/pages/device/routing/ospf.inc.php (working copy) @@ -57,7 +57,7 @@ echo('</tr>'); echo('<tr bgcolor="'.$area_bg.'">'); - echo('<td colspan=7>'); + echo('<td colspan=4>'); echo('<table width=100% border=0 cellpadding=5>'); echo('<tr><th></th><th>Port</th><th>Status</th><th>Port Type</th><th>Port State</th></tr>'); @@ -80,6 +80,9 @@ $port_enabled = '<span style="color: #aaaaaa">disabled</span>'; } + // Fix label + $ospfport['label'] = $ospfport['ifDescr']; + echo('<tr bgcolor="'.$port_bg.'">'); echo(' <td width=15></td>'); echo(' <td><strong>'. generate_port_link($ospfport) . '</strong></td>'); Cheers, Sander

2 1

How to use the new alerting system.
by Thomas Raabo - Zitcom A/S 03 Nov '13

03 Nov '13

I would like to create a 80 % interface utilzation alarm. If the threshold hits 5 times the alert should be generated. Do we have any documentation on the new interface? Thomas

1 0

October Changelog
by Adam Armstrong 02 Nov '13

02 Nov '13

Hi Guys, Here's the condensed version of the changes for October: Also visible at http://www.observium.org/wiki/Changelog#October_2013 Major Improvements and Additions Extensive improvements to sensor display code and definitions. Extensive restructuring to sensor discovery including linking sensors to OSes via MIB simplifying the process of adding new OSes and sensor types. WMI-based poller for retrieving extra data from Windows. Improves CPU/Storage polling and adds Exchange and MSSQL metrics collection. Major rewrite to integrate and expand PowerNet-MIB support for APC devices Allow the use of max-reps on snmpbulkwalk. Vastly improves walking of large tables on supported devices, particularly IOS, Arista and Linux. New Google Maps API-based map complete with point clustering, auto-centring and zooming support to replace the old Google Charts API map Improvements and Additions Support for AVTECH RoomAlert 24E Detection of Toshiba eStudio printers Detection of DIGI USB servers Barracuda NG FW detection Support for airflow sensors. Support for state sensors on SensorProbe / Minkel SRMS. Allow device hostname as a parameter instead of device_id Support for processor and memory on Cisco QFP Collect Dell Service Tag from Dell PowerConnect devices HH3C memory pool and processor polling from HH3C-ENTITY-MIB RADLAN state sensors from RADLAN-HWENVIROMENT MIB Microsens OS and temperature sensors detection Procera detection NetAPP filesystem discovery and polling via the storage system Additional Dell PowerConnect sysObjectIDs Dell-Vendor-MIB sensors Netbotz support Support for two new sensors types; Capacity and Runtime. Primarily used for UPSes and other battery-related devices. Audiocodes Mediant detection Bugfixes Fix Cisco SLA support Some improvements to handling of invalid devices and graph types Improved limits for timeouts/retries on SNMP operations Applications with multiple instances are now accessed via a drop-down Warning if devices have never been polled/discovered now works correctly Fix API to correctly use the authentication system instead of hardcoded database authentication. Correctly use user id in LDAP auth to allow per-device and per-entity permissions Fix Cisco BGP session address formatting Make sure that the RRD directory is correctly renamed when renaming a device Debugging / Troubleshooting Add a page to output the data Observium holds about a port for debugging/troubleshooting purposes.

3 2

Re: [Observium] control device ports via SNMP
by Adam Armstrong 01 Nov '13

01 Nov '13

No, we don't have any features which allow control of the devices at all. Adam. Bogdan Ghita <bvghita(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

control device ports via SNMP
by Bogdan Ghita 01 Nov '13

01 Nov '13

Hello I've been looking through the features of Observium but couldn't find out whether it includes functionality to disable or enable individual ports on a (monitored) switch/router via SNMP. I understand that this lies outside the scope of the software, but I thought I'd ask just in case it's there (or can be enabled optionally) and I missed it. If it isn't, could anybody recommend a management/monitoring software able to provide this? Best regards Bogdan

2 2