- observium - lists.observium.org

Is building groups broken? Can't get it to work.
by Henrik Cednert (Filmlance) 03 Aug '18

03 Aug '18

Hello Running 18.8.9360 (3rd August 2018). Noticed that “groups” have gotten a sweet ass looking upgrade! =))) Nice one! But I have issues when building the groups. Thought it had to do with the “,” and “|” as separator, since that seems to have changed under the hood. So I tried to recreate an old rule and make the new one just like the old one. But when building it i end up at a blank page with the "Building groups memberships” heading. Nothing happens and when I refresh the page no sensors are in the group. Am I missing something? Picture of the old working group and the new one I made. What did I do wrong? [cid:6BC76FC6-6363-4298-A519-392F95B7C800] Old working rule. “|” as separator of hostnames under “association ruleset” but “,” once you enter the edit mode. Is this expeted behaviour? [cid:7E5BC9FB-7903-4C44-9913-9EAAE8A360C9] Cheers and thanks -- Henrik Cednert / + 46 704 71 89 54 / CTO / Filmlance Disclaimer, the hideous bs disclaimer at the bottom is forced, sorry. ¯\_(ツ)_/¯ Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

2 7

multiple pollers and poller-wrapper history
by Christian Eriksson 03 Aug '18

03 Aug '18

Hi, Is it possible to see graphs under /pollerlog/view=wrapper/ for each poller when using poller-wrapper with -g option? All pollers are polling their indivudal host group and putting the rrd's over rrdcached, but as of now the filename is the same, so either they will overwrite the files depending of the rrdcached settings, or nothing will happen if file exists ERROR: rrdcached: RRD Error: creating '/opt/observium/rrd/poller-wrapper.rrd': File exists ERROR: rrdcached: RRD Error: creating '/opt/observium/rrd/poller-wrapper_count.rrd': File exists Regards Christian

2 1

OBS-2744: wrapper broke :(
by Stef Renders 03 Aug '18

03 Aug '18

Mike Please fix ☹ /opt/observium/observium-wrapper poller Traceback (most recent call last): File "/opt/observium/observium-wrapper", line 285, in <module> remote_rrd = false NameError: name 'false' is not defined Kind regards

1 0

rrdcached
by Christian Eriksson 02 Aug '18

02 Aug '18

Hi guys, Hope someone here can shed some light on my issue with rrdcached and observium. I am using a distributed setup with web/sql/poller on separate machines. Followed the guide here http://blog.best-practice.se/2017/10/scaling-observium-horizontally.html and currently using two pollers with great success overall What I can't seem to figure out is why some rrd files won't get created. It doesn't matter what poller I am using or what devices, it is always the following rrd-files ping.rrd ping_snmp.rrd status.rrd [cid:image002.png@01D42A5F.99A20960] [cid:image005.png@01D42A5F.99A20960] Some information regarding my system Observium 18.7.9354 (30th July 2018) OS Linux 4.4.0-130-generic [amd64] (Ubuntu 16.04) Apache 2.4.18 (Ubuntu) PHP 7.0.30-0ubuntu0.16.04.1 (OPcache: ENABLED) Python 2.7.12 MySQL 5.7.23-0ubuntu0.16.04.1 (extension: mysqli 5.0.12-dev) SNMP NET-SNMP 5.7.3 RRDtool 1.5.5 (rrdcached 1.5.5: unix:/var/run/rrdcached.sock) Fping 3.13 (IPv4 and IPv6) rrdcached settings $config['rrdcached'] = 'ip address'; $config['rrd']['no_local'] = TRUE; root@server:/home/user# ps aux | grep rrdcached observi+ 13596 1.6 0.5 1727784 45980 ? Ssl Aug01 15:07 /usr/bin/rrdcached -B, -F, -O, -R -L -w 1800 -z 1800 -t 8 -b /opt/observium/rrd/ -j /var/lib/rrdcached/journal/ -G www-data -U observium -p /var/run/rrdcached.pid -s www-data -m 0660 -l unix:/var/run/rrdcached.sock rrdcached journal file show no trace of the files Syslog errors on rrdcached server Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device1.net.ad.handels.se/status.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device1.net.ad.handels.se/ping.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device2/status.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device1.net.ad.handels.se/ping_snmp.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device2/ping.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device2/ping_snmp.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device3/status.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device3/ping.rrd) failed. Aug 2 13:01:01 server rrdcached[13596]: handle_request_update: stat (/opt/observium/rrd/device3/ping_snmp.rrd) failed. I can manually create a rrd file from the poller with success rrdtool create device/status.rrd --daemon ip-address RRA:AVERAGE:0.5:1:2016 DS:status:GAUGE:600:-20000:U Best regards Christian Eriksson

3 5

Performance issue with a Cisco C6807-XL
by Richard Kuhns 02 Aug '18

02 Aug '18

1 1

Re: [Observium] ifAlias Description notmatches multiple wildcard issue
by Adam Armstrong 31 Jul '18

31 Jul '18

Use attributes as attributes. You probably don't want to create permanent alert table entries just for this, and it's not time critical. Using attributes to match these non-valid descriptions, an alert table entry would only be created when it's necessary, and then you can just use an unrealistic metric condition to make it always trigger. adam. ------ Original Message ------ From: "Klimek, Denis" <DKlimek(a)Stadtwerke-Norderstedt.de> To: "'observium(a)observium.org'" <observium(a)observium.org> Sent: 2018-07-26 15:01:55 Subject: [Observium] ifAlias Description notmatches multiple wildcard issue >Hi all, > > > >I would like to setup a alert checker which checks configured Ethernet >ports if there is a “valid” Observium port description configured. I >tried it with following conditions “ifAlias notmatches >*:*[*Gbit]*{*}*(*)*:*:” but it’s reporting any port as “OK”. The “::” >got added by us for internal purposes. > > > >B: POP102-TBA [20Gbit] {} () ::-> get’s reported as “OK” which is >correct > >CERRZ2R_C_X670-> get’s reported also as “OK” but this is wrong > > > >Attached a screenshot of the complete rule set. > > > >Any ideas are welcome how to solve this J > > > >Mit freundlichem Gruß > >Stadtwerke Norderstedt > > > >Denis Klimek > > > >Professional Network Engineer > >IP-Systemtechnik > > > >Tel: 040 / 521 04 – 1049 > >Mobil: 0151 / 652 219 06 > > > >dklimek(a)stadtwerke-norderstedt.de > >www.stadtwerke-norderstedt.de > > >

3 2

Re: [Observium] ifAlias Description notmatches multiple wildcard issue
by Adam Armstrong 31 Jul '18

31 Jul '18

You are trying to use attributes as metrics, don't do that. adam. ------ Original Message ------ From: "Klimek, Denis" <DKlimek(a)Stadtwerke-Norderstedt.de> To: "'Observium'" <observium(a)observium.org> Sent: 2018-07-31 15:21:15 Subject: Re: [Observium] ifAlias Description notmatches multiple wildcard issue >Hi, > >would it be possible to add ifAlias too or the feature to support other >type of category description aswell to fill the port_descr_type, >port_descr_descr and the other ports_descr_* fields >We are using some custom types additional to "Core, Peering, >Server".... to separate those links better. > >Mit freundlichem Gruß >Stadtwerke Norderstedt > >Denis Klimek > >Professional Network Engineer >IP-Systemtechnik > >Tel: 040 / 521 04 – 1049 >Mobil: 0151 / 652 219 06 > >dklimek(a)stadtwerke-norderstedt.de >www.stadtwerke-norderstedt.de > >-----Ursprüngliche Nachricht----- >Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von >Adam Armstrong >Gesendet: Freitag, 27. Juli 2018 14:04 >An: Observium >Betreff: Re: [Observium] ifAlias Description notmatches multiple >wildcard issue > >ifAlias can't (currently) be used as an alerting metric. > >we could add it, but its perhaps better to just use the attribute in >the >association. > >adam. > >On 2018-07-26 08:01, Klimek, Denis wrote: >>Hi all, >> >>I would like to setup a alert checker which checks configured Ethernet >>ports if there is a "valid" Observium port description configured. I >>tried it with following conditions "ifAlias notmatches >>*:*[*Gbit]*{*}*(*)*:*:" but it's reporting any port as "OK". The "::" >>got added by us for internal purposes. >> >>B: POP102-TBA [20Gbit] {} () ::-> get's reported as "OK" which is >>correct >> >>CERRZ2R_C_X670-> get's reported also as "OK" but this is wrong >> >>Attached a screenshot of the complete rule set. >> >>Any ideas are welcome how to solve this J >> >>Mit freundlichem Gruß >> >>Stadtwerke Norderstedt >> >>DENIS KLIMEK >> >>Professional Network Engineer >> >>IP-Systemtechnik >> >>Tel: 040 / 521 04 - 1049 >> >>Mobil: 0151 / 652 219 06 >> >>dklimek(a)stadtwerke-norderstedt.de >> >>www.stadtwerke-norderstedt.de [1] >> >> >> >>Links: >>------ >>[1] http://www.stadtwerke-norderstedt.de/ >>_______________________________________________ >>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 >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

3 3

ifAlias Description notmatches multiple wildcard issue
by Klimek, Denis 31 Jul '18

31 Jul '18

Hi all, I would like to setup a alert checker which checks configured Ethernet ports if there is a "valid" Observium port description configured. I tried it with following conditions "ifAlias notmatches *:*[*Gbit]*{*}*(*)*:*:" but it's reporting any port as "OK". The "::" got added by us for internal purposes. B: POP102-TBA [20Gbit] {} () ::-> get's reported as "OK" which is correct CERRZ2R_C_X670-> get's reported also as "OK" but this is wrong Attached a screenshot of the complete rule set. Any ideas are welcome how to solve this :) Mit freundlichem Gruß Stadtwerke Norderstedt Denis Klimek Professional Network Engineer IP-Systemtechnik Tel: 040 / 521 04 - 1049 Mobil: 0151 / 652 219 06 dklimek(a)stadtwerke-norderstedt.de<mailto:dklimek@stadtwerke-norderstedt.de> www.stadtwerke-norderstedt.de<http://www.stadtwerke-norderstedt.de/>

2 2

Re: [Observium] VLANs and fdb-table on Cisco devices
by Mike Stupalov 30 Jul '18

30 Jul '18

http://docs.observium.org/faq/#all-my-hosts-seem-down-to-observium-snmp-doe… > todevnull(a)free.fr <mailto:todevnull@free.fr> > 28 July 2018 at 13:42 > Hi, > > Please find it in attached file. > With this debug on vlans module, i think there is my error : > > STDERR[ > add_mibdir: strings scanned in from > /var/www/observium/mibs/cisco/.index are too large. count = 703 > MIB search path: > /var/www/observium/mibs/rfc:/var/www/observium/mibs/net-snmp:/var/www/observium/mibs/cisco > Cannot find module (CISCO-VTP-MIB): At line 0 in (none) > vtpVersion.0: Unknown Object Identifier (Sub-id not found: (top) -> > vtpVersion) > ] > SNMP STATUS[FALSE] > SNMP ERROR[#997 - Wrong .index in mibs dir] > > > Don't really know how to solve this.... > > Thanks in advance for your help. > > Rds, > > Tarik. > > > 28 juillet 2018 07:51 "Mike Stupalov" <mike(a)stupalov.ru > <mailto:%22Mike%20Stupalov%22%20%3Cmike@stupalov.ru%3E>> a écrit: > > > Mike Stupalov <mailto:mike@stupalov.ru> > 28 July 2018 at 08:51 > Hi, > > please attach debug for discovery: > > ./discovery.php -d -m ports,vlans -h <device> > > -- Mike Stupalov Observium Limited, http://observium.org

2 1

Re: [Observium] Port groups unusable in alerts checks ?
by Thibault Richard 30 Jul '18

30 Jul '18

No feedback on this one ? De : Thibault Richard <thibs(a)thibs.com> Envoyé : mercredi 25 juillet 2018 15:50 À : 'observium(a)observium.org' <observium(a)observium.org> Objet : Port groups unusable in alerts checks ? Hello, Ive defined several port groups as you can see below : 1° First question I would like to add a condition equivalent to ifOperStatus equals up but this kind of condition doesnt exist in the pre-defined list. Am I missing something ? 2° Second question I would like to use this group in an Alert Checks but in the entity association ruleset, I can use a Device Group but not a Port Group No « Port Group » and if I try to use Device Group I see only groups related to devices Bug of misunderstanding from me ? Best Regards Thibault

1 0