- observium - lists.observium.org

Re: [Observium] Alerting...
by Adam Armstrong 05 Nov '13

05 Nov '13

There is a page on the wiki explaining the basics. Its still a bit of a work in progress, but some people already find it useful... Adam. Thomas Raabo - Zitcom A/S <tr(a)zitcom.dk> wrote: >Is there any documentation on the new alerting system? > >Is there a way to turn off all the old alerting stuff and start using the new stuff? > >/Thomas >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Alerting...
by Thomas Raabo - Zitcom A/S 05 Nov '13

05 Nov '13

Is there any documentation on the new alerting system? Is there a way to turn off all the old alerting stuff and start using the new stuff? /Thomas

2 1

Fwd: Regarding developers attitude...
by Doychin Dokov 05 Nov '13

05 Nov '13

Hi all, I would just like to share my experience with the attitude of Adam towards general minor web-interface issue reported by a paying customer (me). I've reported that the OSPF stats look very confusing and provided a screenshot which shows the issue. The inital response I got was "jira is not for general complaining". My answer was: "Where do we do so, then? 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." Which resulted in these comments from Tom Laermans and Adam Armstrong: "I believe you are confused about what exactly it is that you paid for." "You're definitely doing the right thing to make sure we add the features you want..." And then the issue was completely deleted.... So, I'd like to point these things: * why do we get such an attitude against the money kindly "asked" from us? Being a kickstarter supporter for the alerting system, I kind of felt being lied to, since the Observium developers decided that one has to get a license to receive the full functionality which the funding was raised for in the first place... Anyways, I understand the need for more revenue, but not the attitude at all. * this is in no way requesting a new feature. Is just a report, plus marked as of minor importance, which shows a feature already available in Observium being kind-of unusable. This makes me completely not understand the way developers behaved. * i've asked Adam in a personal e-mail what's the reason for this attitude. Since he did not get the guts to reply, I hope he does it here. I'd very much want to know what I've done wrong to provoke such an attitude. * this is not the first time one of the developers would say "idiot" to a (paying) user. So go ahead, shoot me. Thank you for your time and sorry about the need to post this here. Kind regards, - D. ---------- Forwarded message ---------- From: Adam Armstrong (JIRA) <jira(a)observium.org> Date: 2013/11/3 Subject: [OBS-JIRA] (OBSERVIUM-571) OSPF stats are a mess To: dokov(a)silistra.tv Adam Armstrong<http://jira.observium.org/secure/ViewProfile.jspa?name=adama>deleted [image: Bug] OBSERVIUM-571 *OSPF stats are a mess* <http://jira.observium.org/browse/OBSERVIUM-571> This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 32

Help troubleshooting auto discovery
by Jason Lixfeld 05 Nov '13

05 Nov '13

I added a new box to my network last week, but Observium hasn't seemed to have picked it up yet. I'm trying to troubleshoot it, but short of proving ping, CDP and snmpwalk on the box work fine and manually running the discovery cron job, I'm not sure what else to do in terms of troubleshooting. Can anyone lend a pointer? CentOS 6.3 (Final) Observium 0.13.11.4743 [root@monitor01 observium]# /opt/observium/discovery.php -d -h new DEBUG! Observium v0.13.11.4743 Discovery Schema update disabled by -h new, run with -h none to perform it manually. SQL[SELECT * FROM `devices` WHERE status = 1 AND disabled = 0 AND (`last_discovered` IS NULL OR `last_discovered` = '0000-00-00 00:00:00') ORDER BY device_id DESC] /opt/observium/discovery.php new November 5, 2013, 8:16 - 0 devices discovered in 0.002 secs MySQL: Cell[0/0s] Row[0/0s] Rows[1/0s] Column[0/0s] Update[0/0s] Insert[0/0s] Delete[0/0s] [root@monitor01 observium]# mysql> select hostname from devices where hostname like 'bfr01.905king%'; Empty set (0.00 sec) mysql> RP/0/RSP0/CPU0:bfr01.151FrontStW01.YYZ#sh cdp neigh te0/2/0/14 detail Tue Nov 5 08:09:06.390 EST ------------------------- Device ID: bfr01.905KingStW01.YYZ SysName : bfr01.905KingStW01.YYZ Entry address(es): IPv4 address: * Platform: cisco ASR9K Series, Capabilities: Router Interface: TenGigE0/2/0/14 Port ID (outgoing port): TenGigE0/1/0/0 Holdtime : 166 sec Version : Cisco IOS XR Software, Version 4.3.2[Default] Copyright (c) 2013 by Cisco Systems, Inc. advertisement version: 2 Duplex: full RP/0/RSP0/CPU0:bfr01.151FrontStW01.YYZ# [root@monitor01 observium]# snmpwalk -v2c -c * bfr01.905KingStW01.YYZ sysDescr SNMPv2-MIB::sysDescr.0 = STRING: "Cisco IOS XR Software (Cisco ASR9K Series), Version 4.3.2[Default] Copyright (c) 2013 by Cisco Systems, Inc." [root@monitor01 observium]# ping -c 1 bfr01.905KingStW01.yyz PING bfr01.905KingStW01.yyz (10.219.49.22) 56(84) bytes of data. 64 bytes from bfr01.905KingStW01.YYZ (10.219.49.22): icmp_seq=1 ttl=253 time=0.862 ms --- bfr01.905KingStW01.yyz ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 1ms rtt min/avg/max/mdev = 0.862/0.862/0.862/0.000 ms [root@monitor01 observium]# Thanks in advance, eh! ;)

3 7

Re: [Observium] :-)
by Rob VanHooren 05 Nov '13

05 Nov '13

it’s Canada. Everybody knows everybody. He’s in the next igloo a few streets over. :-P On Nov 5, 2013, at 8:04, observium-request(a)observium.org wrote: > know eachother? :P > > adam.

2 1

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