- observium - lists.observium.org

Unix agent alerting on Postfix mail queue size
by Attila Nagy 02 Mar '20

02 Mar '20

Hi Adam, Tom! We are currently facing the problem of having to alert on Postfix mail queue size coming from the Unix agent (thanks to "careful" users who let their e-mail passwords repeatedly stolen). As I've been trying to read about this in the archives, I see that this is a somewhat frequently upcoming but still unresolved topic. May I ask about the current status of this request?! Best regards, Attila

1 0

Supress Sensor Updated in Eventlog
by Klimek, Denis 02 Mar '20

02 Mar '20

Hi all, is there any method to supress the generation of "Sensor updated"-Eventlog entries if Observium is dynamicly changing the limit_low/high value? Our eventlog contains shitloads of entries for this kind of logs and they are not really useful from my opinion. So we would like to keep the sensors quiet. Currently we are running an external scripts triggered by cronjob to filter out those messages, but if we would supress the creation itself it would be much better Cheers, Denis Mit freundlichem Gruß Stadtwerke Norderstedt Denis Klimek Carrier Manager & Professional Network Engineer IP-Systemtechnik Tel: +49 (0) 40 / 521 04 - 1049 dklimek(a)stadtwerke-norderstedt.de<mailto:dklimek@stadtwerke-norderstedt.de> www.stadtwerke-norderstedt.de<http://www.stadtwerke-norderstedt.de/>

2 4

creating custom probe
by cody＠mail-server.cc 02 Mar '20

02 Mar '20

Hi, I wanted to create a custom probe to read two values from Cisco devices which aren't available via their SNMP agents. How do i get my probe included and What to i need to present the two values (current value, max value) in a graph and trigger an alert when the current value reaches 90% of the max value? Thanks, Cody

1 0

Re: [Observium] How to exclude "virtual Memory" from an alert checker (but keep all other memory metrics)?
by Thomas Stather 28 Feb '20

28 Feb '20

Hi I set the following Device Match / Entity Match: (device.type in server AND (mempool.mempool_descr notmatch *cache* OR mempool.mempool_descr notmatch *Virtual*)) However, the alert is still displayed (which is true since the virtual memory of one of our VMs is stil labove 80%). How can i reset the alert to test that the condition now works as expected? Best, Thomas Am 12.07.19 um 16:30 schrieb Hamilton, Kent: > Here is what I use for the "Entity Match": > mempool_descr notmatch *cache* > mempool_descr notmatch *Physical* > mempool descr notmatch *Virtual* > mempool desc notmatch *virtual* > mempool desc notmatch *Shared Real* > > > > > -----Original Message----- > From: observium <observium-bounces(a)observium.org> On Behalf Of Thomas Stather via observium > Sent: Thursday, July 4, 2019 9:57 AM > To: 'Observium' <observium(a)observium.org> > Cc: Thomas Stather <tstather(a)mr.mpg.de> > Subject: [Observium] How to exclude "virtual Memory" from an alert checker (but keep all other memory metrics)? > > Exegy Email Security > > WARNING This email originated from outside of Exegy. DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. > Remember Exegy ITS will never ask for user ID information via email communication. > > > > Hi > > > We are using Observium Professional: 19.6.9946 (rolling) > > > I have set up an alert check to check our servers for fully occupied memory ("mempool_perc greater 80"). > > I want to include the metrics "Memory buffers", "Physical Memory", "Swap space" but i want to exclude "Virtual memory". > > > Is there a way of doing so and if so, how? > > > > Best, > > Thomas > > > -- > Thomas Stather > IT Services > > VCP4, VCP6-DCV, VCP6.5-DCV > > Tel: +49 6221 486 628 > Fax: +49 6221 486 561 > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > ________________________________ > > This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others. -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561

2 4

Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph"
by Chris Macneill 27 Feb '20

27 Feb '20

Hi Adam, OK, read that page and here's what happens when I try to switch from stable to rolling as per documentation:- root@obs:/opt/observium# svn up Updating '.': At revision 10304. root@obs:/opt/observium# svn switch https://svn.observium.org/svn/observium/trunk svn: E155025: 'svn switch' does not support switching a working copy to a different repository svn: E155025: 'http://svn.observium.org/svn/observium/branches/stable' is not the same repository as 'https://svn.observium.org/svn' Regards Chris Macneill Zelan Ltd From: "observium" <observium(a)observium.org> To: "observium" <observium(a)observium.org> Cc: "Adam Armstrong" <adama(a)memetic.org> Sent: Thursday, 27 February, 2020 15:22:50 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Read that entire page. Sent from [ http://www.bluemail.me/r?b=15818 | BlueMail ] On 27 Feb 2020, at 02:06, Chris Macneill < [ mailto:cmacneill@zelan.co.nz | cmacneill(a)zelan.co.nz ] > wrote: Hi Adam, "svn update" is what I assumed I was supposed to use and it said successfully updated to 10304. Webpage says v20.2.10302 (stable) after update. I don't see any doucmentation in [ https://docs.observium.org/updating/#upgrading-the-subscription-edition-to-… | https://docs.observium.org/updating/#upgrading-the-subscription-edition-to-… ] that references any difference between latest "stable" and latest "rolling". How do I upgrade to "rolling" 10304? Why does "svn update" tell me it's updated to 10304 when it seemingly hasn't? Regards Chris Macneill Zelan Ltd From: "observium" <observium(a)observium.org> To: "observium" <observium(a)observium.org> Cc: "Adam Armstrong" <adama(a)memetic.org> Sent: Thursday, 27 February, 2020 14:51:35 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Is this, perchance, stable, and not rolling? Adam. Sent from [ http://www.bluemail.me/r?b=15818 | BlueMail ] On 27 Feb 2020, at 01:45, Chris Macneill via observium < [ mailto:observium@observium.org | observium(a)observium.org ] > wrote: BQ_BEGIN Hi Mike, Sorry, 20.2.10304 doesn't fix it. Fields still split on commas for port_descr_type = 'cust' and debug results exactly the same as previous:- SELECT * FROM `ports` AS I , `devices` AS D WHERE `port_descr_type` = 'cust' AND `port_descr_descr` = 'GDC Westland Recreation Centre' , ' 83 High St' , ' Greymouth' AND D . device_id = I . device_id Also, a new bug added, software version number at bottom of screen is now out of step with "svn update". Update said successfully updated to 10304, but webpage says 20.2.10302 I've had a hack at the code in html/includes/graphs/customer/bits.inc.php and put the following workaround in place:- Line 16 (Original v20.2.10304 Code) foreach (dbFetchRows("SELECT * FROM `ports` AS I, `devices` AS D WHERE `port_descr_type` = 'cust' AND `port_descr_descr` = ? AND D.device_id = I.device_id", array($vars['id'])) as $port) Replaced with:- // Copy id array directly for case where port_descr_descr was NOT previosuly split/exploded on commas. $pddstr = $vars['id']; if ( count($vars['id']) > 1 ) { // Impode id array addng commas where array size > 1, i.e. original id contained commas and WAS split/exploded. $pddstr = implode(",", $vars['id']); } foreach (dbFetchRows("SELECT * FROM `ports` AS I, `devices` AS D WHERE `port_descr_type` = 'cust' AND `port_descr_descr` = ? AND D.device_id = I.device_id", array($pddstr)) as $port) $vars['id'] is the result of splitting or exploding port_descr_descr string value somewhere earlier, but I can't locate that in the code and as Adam mentioned, changing this elsewhere might have undesirable consequences. The problem only happens for port_descr_type = "cust", for other port types, e.g. core, peering, transit, port_descr_descr isn't split or exploded despite containing commas, but I can't find the locaiton in the code where this conditional behaviour occurs. Regards Chris Macneill Zelan Ltd From: "Mike Stupalov" <mike(a)observium.org> To: "observium" <observium(a)observium.org>, "observium" <observium(a)observium.org> Cc: "Chris Macneill" <cmacneill(a)cmit.nz> Sent: Thursday, 27 February, 2020 12:59:52 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Hi Chris, try with latest revision (r10304, trunk). Issue should be fixed. Chris Macneill via observium wrote on 26.02.2020 20:25: BQ_BEGIN Hi Adam, Looks like data is being split on commas and causing an SQL syntax error. Debug for:- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} returns:- Error in query: (You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' 83 High St',' Greymouth' AND D.device_id = I.device_id' at line 1) 1064 I can obviously fix this short-term by removing commas from the Port Descriptions, but would be good to be able to support use of commas and other punctuation in the longer term or at least update the Help page to list characters to avoid. I had a quick look earlier at the Regex that was parsing the description data, but wasn't immediately obvious commas were an issue. At least I know where the problem lies and I'll take another look later. I guess semi-colons might work if commas don't. Regards Chris Macneill Zelan Ltd From: "observium" [ mailto:observium@observium.org | <observium(a)observium.org> ] To: "observium" [ mailto:observium@observium.org | <observium(a)observium.org> ] Cc: "adama" [ mailto:adama@observium.org | <adama(a)observium.org> ] Sent: Thursday, 27 February, 2020 04:50:22 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Do you get anything useful from showing rrd command on the graph browser page? (click on the graph) Do you get anything useful from adding &debug=1 on the end of the graph image url? Can you arrange ssh/http access to the install if those two things don’t show us what the problem is? Adam. From: observium [ mailto:observium-bounces@observium.org | <observium-bounces(a)observium.org> ] On Behalf Of Chris Macneill via observium Sent: 26 February 2020 05:22 To: observium [ mailto:observium@observium.org | <observium(a)observium.org> ] Cc: Chris Macneill [ mailto:cmacneill@cmit.nz | <cmacneill(a)cmit.nz> ] Subject: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Hi, We're currently using Observium v20.1.10233 and have a problem with "Error Drawing Graph" for all ports with a "Cust" prefix. Ports with "Core", "Peer" or "Transit" prefix correctly show graphs. The ports we're monitoring are VLANs, the Peer/Transit are simple 802.1q VLANs, the Core/Customer VLANs are QinQ, i.e. two layers of 802.1q headers. All port types are correctly detected by SNMP and listed against the Router. Given that "Core" displays graphs correctly, this doesn't seem to be related to QinQ, but specifically to the "Cust" prefix. Examples that correctly show graphs, 1st is 802.1q, 2nd is QinQ:- Peering: Datacom CHC<->Chorus [10Gbit] {Chorus SVID.100} Core: Zelan Workshop, 50 Palmerston St, Westport [1Gbit] {Chorus CVID.100} Example (QinQ) that gives "Error Drawing Graph":- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} All our routers are MikroTik, so can't determine if this is a router OS/hardware specific issue. Regards Chris Macneill Zelan Ltd. _______________________________________________ observium mailing list [ mailto:observium@observium.org | observium(a)observium.org ] [ http://postman.memetic.org/cgi-bin/mailman/listinfo/observium | http://postman.memetic.org/cgi-bin/mailman/listinfo/observium ] _______________________________________________ observium mailing list [ mailto:observium@observium.org | observium(a)observium.org ] [ http://postman.memetic.org/cgi-bin/mailman/listinfo/observium | http://postman.memetic.org/cgi-bin/mailman/listinfo/observium ] -- Mike Stupalov Observium Limited, [ http://observium.org/ | http://observium.org ] observium mailing list observium(a)observium.org [ http://postman.memetic.org/cgi-bin/mailman/listinfo/observium | http://postman.memetic.org/cgi-bin/mailman/listinfo/observium ] BQ_END _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium BQ_END _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph"
by Adam Armstrong 27 Feb '20

27 Feb '20

Read that entire page. ⁣Sent from BlueMail On 27 Feb 2020, 02:06, at 02:06, Chris Macneill <cmacneill(a)zelan.co.nz> wrote: >Hi Adam, > >"svn update" is what I assumed I was supposed to use and it said >successfully updated to 10304. > >Webpage says v20.2.10302 (stable) after update. > >I don't see any doucmentation in [ >https://docs.observium.org/updating/#upgrading-the-subscription-edition-to-… >| >https://docs.observium.org/updating/#upgrading-the-subscription-edition-to-… >] that references any difference between latest "stable" and latest >"rolling". > >How do I upgrade to "rolling" 10304? > >Why does "svn update" tell me it's updated to 10304 when it seemingly >hasn't? > >Regards > >Chris Macneill >Zelan Ltd > >From: "observium" <observium(a)observium.org> >To: "observium" <observium(a)observium.org> >Cc: "Adam Armstrong" <adama(a)memetic.org> >Sent: Thursday, 27 February, 2020 14:51:35 >Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error >Drawing Graph" > >Is this, perchance, stable, and not rolling? > >Adam. > >Sent from [ http://www.bluemail.me/r?b=15818 | BlueMail ] >On 27 Feb 2020, at 01:45, Chris Macneill via observium < [ >mailto:observium@observium.org | observium(a)observium.org ] > wrote: > > >Hi Mike, > >Sorry, 20.2.10304 doesn't fix it. Fields still split on commas for >port_descr_type = 'cust' and debug results exactly the same as >previous:- > >SELECT * FROM `ports` AS I , `devices` AS D WHERE `port_descr_type` = >'cust' AND `port_descr_descr` = 'GDC Westland Recreation Centre' , ' 83 >High St' , ' Greymouth' AND D . device_id = I . device_id > >Also, a new bug added, software version number at bottom of screen is >now out of step with "svn update". Update said successfully updated to >10304, but webpage says 20.2.10302 > >I've had a hack at the code in >html/includes/graphs/customer/bits.inc.php and put the following >workaround in place:- > >Line 16 (Original v20.2.10304 Code) >foreach (dbFetchRows("SELECT * FROM `ports` AS I, `devices` AS D WHERE >`port_descr_type` = 'cust' AND `port_descr_descr` = ? AND D.device_id = >I.device_id", array($vars['id'])) as $port) > >Replaced with:- > >// Copy id array directly for case where port_descr_descr was NOT >previosuly split/exploded on commas. >$pddstr = $vars['id']; >if ( count($vars['id']) > 1 ) { >// Impode id array addng commas where array size > 1, i.e. original id >contained commas and WAS split/exploded. >$pddstr = implode(",", $vars['id']); >} >foreach (dbFetchRows("SELECT * FROM `ports` AS I, `devices` AS D WHERE >`port_descr_type` = 'cust' AND `port_descr_descr` = ? AND D.device_id = >I.device_id", array($pddstr)) as $port) > >$vars['id'] is the result of splitting or exploding port_descr_descr >string value somewhere earlier, but I can't locate that in the code and >as Adam mentioned, changing this elsewhere might have undesirable >consequences. > >The problem only happens for port_descr_type = "cust", for other port >types, e.g. core, peering, transit, port_descr_descr isn't split or >exploded despite containing commas, but I can't find the locaiton in >the code where this conditional behaviour occurs. > >Regards > >Chris Macneill >Zelan Ltd > >From: "Mike Stupalov" <mike(a)observium.org> >To: "observium" <observium(a)observium.org>, "observium" ><observium(a)observium.org> >Cc: "Chris Macneill" <cmacneill(a)cmit.nz> >Sent: Thursday, 27 February, 2020 12:59:52 >Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error >Drawing Graph" > >Hi Chris, > >try with latest revision (r10304, trunk). > >Issue should be fixed. > >Chris Macneill via observium wrote on 26.02.2020 20:25: > >BQ_BEGIN > >Hi Adam, > >Looks like data is being split on commas and causing an SQL syntax >error. Debug for:- > >Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] >{Chorus CVID.113} > >returns:- > >Error in query: (You have an error in your SQL syntax; check the manual >that corresponds to your MariaDB server version for the right syntax to >use near '' 83 High St',' Greymouth' AND D.device_id = I.device_id' at >line 1) 1064 > >I can obviously fix this short-term by removing commas from the Port >Descriptions, but would be good to be able to support use of commas and >other punctuation in the longer term or at least update the Help page >to list characters to avoid. > >I had a quick look earlier at the Regex that was parsing the >description data, but wasn't immediately obvious commas were an issue. >At least I know where the problem lies and I'll take another look >later. I guess semi-colons might work if commas don't. > >Regards > >Chris Macneill >Zelan Ltd > > >From: "observium" [ mailto:observium@observium.org | ><observium(a)observium.org> ] >To: "observium" [ mailto:observium@observium.org | ><observium(a)observium.org> ] >Cc: "adama" [ mailto:adama@observium.org | <adama(a)observium.org> ] >Sent: Thursday, 27 February, 2020 04:50:22 >Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error >Drawing Graph" > > > >Do you get anything useful from showing rrd command on the graph >browser page? (click on the graph) > > > >Do you get anything useful from adding &debug=1 on the end of the graph >image url? > > > >Can you arrange ssh/http access to the install if those two things >don’t show us what the problem is? > > > >Adam. > > > > >From: observium [ mailto:observium-bounces@observium.org | ><observium-bounces(a)observium.org> ] On Behalf Of Chris Macneill via >observium >Sent: 26 February 2020 05:22 >To: observium [ mailto:observium@observium.org | ><observium(a)observium.org> ] >Cc: Chris Macneill [ mailto:cmacneill@cmit.nz | <cmacneill(a)cmit.nz> ] >Subject: [Observium] Port Description Parsing - Cust Graphs "Error >Drawing Graph" > > > > > >Hi, > > > > > >We're currently using Observium v20.1.10233 and have a problem with >"Error Drawing Graph" for all ports with a "Cust" prefix. Ports with >"Core", "Peer" or "Transit" prefix correctly show graphs. > > > > > >The ports we're monitoring are VLANs, the Peer/Transit are simple >802.1q VLANs, the Core/Customer VLANs are QinQ, i.e. two layers of >802.1q headers. > > > > > >All port types are correctly detected by SNMP and listed against the >Router. Given that "Core" displays graphs correctly, this doesn't seem >to be related to QinQ, but specifically to the "Cust" prefix. > > > > > >Examples that correctly show graphs, 1st is 802.1q, 2nd is QinQ:- > > > > > >Peering: Datacom CHC<->Chorus [10Gbit] {Chorus SVID.100} > > >Core: Zelan Workshop, 50 Palmerston St, Westport [1Gbit] {Chorus >CVID.100} > > > > > >Example (QinQ) that gives "Error Drawing Graph":- > > > > > >Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] >{Chorus CVID.113} > > > > > >All our routers are MikroTik, so can't determine if this is a router >OS/hardware specific issue. > > > > > >Regards > >Chris Macneill >Zelan Ltd. > > > > >_______________________________________________ >observium mailing list >[ mailto:observium@observium.org | observium(a)observium.org ] >[ http://postman.memetic.org/cgi-bin/mailman/listinfo/observium | >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium ] > > > >_______________________________________________ >observium mailing list [ mailto:observium@observium.org | >observium(a)observium.org ] [ >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium | >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium ] > > > >-- >Mike Stupalov >Observium Limited, [ http://observium.org/ | http://observium.org ] > > > > >observium mailing list >observium(a)observium.org >[ http://postman.memetic.org/cgi-bin/mailman/listinfo/observium | >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium ] > >BQ_END > > >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph"
by Chris Macneill 27 Feb '20

27 Feb '20

Hi Adam, Looks like data is being split on commas and causing an SQL syntax error. Debug for:- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} returns:- Error in query: (You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' 83 High St',' Greymouth' AND D.device_id = I.device_id' at line 1) 1064 I can obviously fix this short-term by removing commas from the Port Descriptions, but would be good to be able to support use of commas and other punctuation in the longer term or at least update the Help page to list characters to avoid. I had a quick look earlier at the Regex that was parsing the description data, but wasn't immediately obvious commas were an issue. At least I know where the problem lies and I'll take another look later. I guess semi-colons might work if commas don't. Regards Chris Macneill Zelan Ltd From: "observium" <observium(a)observium.org> To: "observium" <observium(a)observium.org> Cc: "adama" <adama(a)observium.org> Sent: Thursday, 27 February, 2020 04:50:22 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Do you get anything useful from showing rrd command on the graph browser page? (click on the graph) Do you get anything useful from adding &debug=1 on the end of the graph image url? Can you arrange ssh/http access to the install if those two things don’t show us what the problem is? Adam. From: observium <observium-bounces(a)observium.org> On Behalf Of Chris Macneill via observium Sent: 26 February 2020 05:22 To: observium <observium(a)observium.org> Cc: Chris Macneill <cmacneill(a)cmit.nz> Subject: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Hi, We're currently using Observium v20.1.10233 and have a problem with "Error Drawing Graph" for all ports with a "Cust" prefix. Ports with "Core", "Peer" or "Transit" prefix correctly show graphs. The ports we're monitoring are VLANs, the Peer/Transit are simple 802.1q VLANs, the Core/Customer VLANs are QinQ, i.e. two layers of 802.1q headers. All port types are correctly detected by SNMP and listed against the Router. Given that "Core" displays graphs correctly, this doesn't seem to be related to QinQ, but specifically to the "Cust" prefix. Examples that correctly show graphs, 1st is 802.1q, 2nd is QinQ:- Peering: Datacom CHC<->Chorus [10Gbit] {Chorus SVID.100} Core: Zelan Workshop, 50 Palmerston St, Westport [1Gbit] {Chorus CVID.100} Example (QinQ) that gives "Error Drawing Graph":- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} All our routers are MikroTik, so can't determine if this is a router OS/hardware specific issue. Regards Chris Macneill Zelan Ltd. _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

3 3

smokeping integration
by cody＠mail-server.cc 26 Feb '20

26 Feb '20

I installed smokeping, generated the targets file with the script and smokeping is running and updating the rrd's. I set the smokeping directory in the gui but i do not get the smokeping tab on the devices. Is there anything else to do? I'm not seeing something wrong - how do i troubleshoot/identify why the smokeping tab doesn't appear? thanks

2 2

Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph"
by adama＠observium.org 26 Feb '20

26 Feb '20

Aha, I see what it’s doing. You missed out the actual query, which makes it more obvious what’s happening /graph.php?type=customer_bits&id=herp,derp&debug=1 Generates: SELECT * FROM `ports` AS I, `devices` AS D WHERE `port_descr_type` = 'cust' AND `port_descr_descr` = 'herp','derp' AND D.device_id = I.device_id We have a bit of code in the URL parser that expands any argument with a comma into an array of arguments, it’s used when you put in a list of port_ids for example. It’s expanding this here, and we’re passing an array of values to the SQL query builder. I’m not sure how much would need to be changed to suppress this behaviour in this instance, so I’d recommend just not putting commas in port descriptions! Thanks, Adam. From: Chris Macneill <cmacneill(a)zelan.co.nz> Sent: 26 February 2020 17:22 To: observium <observium(a)observium.org> Cc: adama <adama(a)observium.org> Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Hi Adam, Looks like data is being split on commas and causing an SQL syntax error. Debug for:- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} returns:- Error in query: (You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' 83 High St',' Greymouth' AND D.device_id = I.device_id' at line 1) 1064 I can obviously fix this short-term by removing commas from the Port Descriptions, but would be good to be able to support use of commas and other punctuation in the longer term or at least update the Help page to list characters to avoid. I had a quick look earlier at the Regex that was parsing the description data, but wasn't immediately obvious commas were an issue. At least I know where the problem lies and I'll take another look later. I guess semi-colons might work if commas don't. Regards Chris Macneill Zelan Ltd _____ From: "observium" <observium(a)observium.org <mailto:observium@observium.org> > To: "observium" <observium(a)observium.org <mailto:observium@observium.org> > Cc: "adama" <adama(a)observium.org <mailto:adama@observium.org> > Sent: Thursday, 27 February, 2020 04:50:22 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Do you get anything useful from showing rrd command on the graph browser page? (click on the graph) Do you get anything useful from adding &debug=1 on the end of the graph image url? Can you arrange ssh/http access to the install if those two things don’t show us what the problem is? Adam. From: observium <observium-bounces(a)observium.org <mailto:observium-bounces@observium.org> > On Behalf Of Chris Macneill via observium Sent: 26 February 2020 05:22 To: observium <observium(a)observium.org <mailto:observium@observium.org> > Cc: Chris Macneill <cmacneill(a)cmit.nz <mailto:cmacneill@cmit.nz> > Subject: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph" Hi, We're currently using Observium v20.1.10233 and have a problem with "Error Drawing Graph" for all ports with a "Cust" prefix. Ports with "Core", "Peer" or "Transit" prefix correctly show graphs. The ports we're monitoring are VLANs, the Peer/Transit are simple 802.1q VLANs, the Core/Customer VLANs are QinQ, i.e. two layers of 802.1q headers. All port types are correctly detected by SNMP and listed against the Router. Given that "Core" displays graphs correctly, this doesn't seem to be related to QinQ, but specifically to the "Cust" prefix. Examples that correctly show graphs, 1st is 802.1q, 2nd is QinQ:- Peering: Datacom CHC<->Chorus [10Gbit] {Chorus SVID.100} Core: Zelan Workshop, 50 Palmerston St, Westport [1Gbit] {Chorus CVID.100} Example (QinQ) that gives "Error Drawing Graph":- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} All our routers are MikroTik, so can't determine if this is a router OS/hardware specific issue. Regards Chris Macneill Zelan Ltd. _______________________________________________ observium mailing list observium(a)observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Port Description Parsing - Cust Graphs "Error Drawing Graph"
by Chris Macneill 26 Feb '20

26 Feb '20

Hi, We're currently using Observium v20.1.10233 and have a problem with "Error Drawing Graph" for all ports with a "Cust" prefix. Ports with "Core", "Peer" or "Transit" prefix correctly show graphs. The ports we're monitoring are VLANs, the Peer/Transit are simple 802.1q VLANs, the Core/Customer VLANs are QinQ, i.e. two layers of 802.1q headers. All port types are correctly detected by SNMP and listed against the Router. Given that "Core" displays graphs correctly, this doesn't seem to be related to QinQ, but specifically to the "Cust" prefix. Examples that correctly show graphs, 1st is 802.1q, 2nd is QinQ:- Peering: Datacom CHC<->Chorus [10Gbit] {Chorus SVID.100} Core: Zelan Workshop, 50 Palmerston St, Westport [1Gbit] {Chorus CVID.100} Example (QinQ) that gives "Error Drawing Graph":- Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113} All our routers are MikroTik, so can't determine if this is a router OS/hardware specific issue. Regards Chris Macneill Zelan Ltd.

2 1