There is a new version on http://beta.woodstone.nu were you will get extra logging within debugview.
Logging will look like: [8048] Formula : (sa_currentresult - sa_previousresult) < 20000000 [8048] sa_currentresult : 811496258 [8048] sa_previousresult : 811484686 [8048] sa_currenttimeinms : 59146491 [8048] sa_previoustimeinms : 59145083 [8048] Formula result : TRUE Dirk Bulinckx Servers Alive - http://www.woodstone.nu StellarDNS (DNS Hosting) - http://www.stellardns.com -----Original Message----- From: Servers Alive Discussion List [mailto:[email protected]] On Behalf Of dirk Sent: Wednesday, April 24, 2013 5:01 PM To: Servers Alive Discussion List Subject: RE: [SA-list] snmp bandwith monitoring The result of the formula is a TRUE/FALSE as we evaluate the expression (within an "external" part of SA). dirk. On Wed, 24 Apr 2013 15:30:43 +0200, Lau Daniels wrote: > Dirk, > > Thanks, appreciate it. > > We had a slow build up of DDos requests over one of our internet > lines. We didn't monitor the usage of the internet lines, just trying > to implement it now in SA so we can be warned if a line is going to > be > flooded. > > I think it would be a great feature if it's possible to store it also > in RRD, so you could watch the trend of bandwidth over time in RRD. > Maybe an "SA buildin check" on SNMP that checks a OID twice in a row > and gives the result back? > > Lau > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[email protected]] On > Behalf Of dirk > Sent: woensdag 24 april 2013 14:46 > To: Servers Alive Discussion List > Subject: RE: [SA-list] snmp bandwith monitoring > > Only the current result is stored in the RRD db. > I'll see if I can add some logging so the result of the formula is > also logged (not in RRD sorry) so you can see what it gives and why > you get the "wrong" result. > > > dirk > > On Wed, 24 Apr 2013 14:15:52 +0200, Lau Daniels wrote: >> Dirk, >> >> I was sure i missed it somewhere ;-) >> >> But anyway, did some testing and I >> donÃÆââââ¬Å¡Ã¬Ã¢ââ¬Å¾Ã¢t get it to work. >> >> I get snmp data back from the firewall with SNMP check oid - >> 1.3.6.1.2.1.2.2.1.10.8 = Total Downloaded in Bytes >> >> I made it really simple, just a formula (sa_currentresult - >> sa_previousresult) < 20000000 is false >> >> I gives me as sa_previousresult: 937675260 and sa_currentresult: >> 944442813 should result in 6767553 >> The response of SA is: 944442813 should be: (sa_currentresult - >> sa_previousresult) < 20000000 >> >> Even if I enter 200 it still gives "down". Missing something again? >> >> And also another question: >> Is there a way to store the result of the formula in the RDD >> database >> or only the sa_currentresult? >> >> Regards, >> Lau >> >> >> >> >> -----Original Message----- >> From: Servers Alive Discussion List [mailto:[email protected]] On >> Behalf Of dirk >> Sent: dinsdag 23 april 2013 9:16 >> To: Servers Alive Discussion List >> Subject: Re: [SA-list] snmp bandwith monitoring >> >> You can use a formula for this. >> >> For example: >> >> (sa_currentresult - sa_previousresult) / (sa_currenttimeinms - >> sa_previoustimeinms) <5 >> >> Would give an alert if the currentresult - previous result devided >> by >> the (current time in ms -previous time in ms) would be smaller then >> 5 >> >> >> In the doc under the part of the SNMP CHECK TAB there is this >> example >> too >> >> Hope this helps >> >> >> >> dirk >> >> >> On Mon, 22 Apr 2013 16:15:38 +0200, Lau Daniels wrote: >>> Hi Dirk, >>> >>> Just finished searching for a decent document about bandwidth >>> monitoring using Serversalive. Nothing >>> foundÃÆââââ¬Å¡Ã¬Ãâæ.. >>> >>> I know I can do a snmp query for ifInOctets for interface 8 with >>> 1.3.6.1.2.1.2.2.1.10.8. >>> This gives me the The total number of octets received on the >>> interface. >>> >>> Nice to know but I want the difference between two poll cycles. >>> Average_Input=Total_Input (in BITS)/ Time (in SEC) >>> >>> Dirk, is this possible with Serversalive? >>> >>> Regards, >>> >>> Lau >>> >>> ------------------------- >>> >>> This email and any files transmitted with it are >>> confidentialÃÆââ¬Å¡Ãâà andÃÆââ¬Å¡Ãâà >>> intended solely for the use of the individual or entity to whom >>> theyÃÆââ¬Å¡Ãâà >>> are addressed.ÃÆââ¬Å¡Ãâà If you have received this email in error >>> please >>> notifyÃÆââ¬Å¡Ãâà the sender. >>> Any views or opinions presented in this email are solely those of >>> the >>> author and do not necessarily represent those of the company. >>> >>> This footnote also confirms that this email message has been swept >>> by >>> MIMEsweeper for the presence of computer viruses but we cannot >>> accept >>> responsibility for any loss or damage arising from the use of this >>> email and/or attachment(s). >>> >>> To unsubscribe send a message with UNSUBSCRIBE in the subject line >>> to [email protected] If you use auto-responders (like >>> out-of-the-office messages), make sure that they are not sent to >>> the >>> list nor to individual members. >>> Doing so will cause you to be automatically removed from the list. >> >> To unsubscribe send a message with UNSUBSCRIBE in the subject line >> to >> [email protected] If you use auto-responders (like >> out-of-the-office >> messages), make sure that they are not sent to the list nor to >> individual members. >> Doing so will cause you to be automatically removed from the list. >> >> >> >> To unsubscribe send a message with UNSUBSCRIBE in the subject line >> to >> [email protected] If you use auto-responders (like >> out-of-the-office >> messages), make sure that they are not sent to the list nor to >> individual members. >> Doing so will cause you to be automatically removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > [email protected] If you use auto-responders (like > out-of-the-office > messages), make sure that they are not sent to the list nor to > individual members. Doing so will cause you to be automatically > removed from the list. > > > ************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please > notify > the sender. > Any views or opinions presented in this email are solely those of the > author and do not necessarily represent those of the company. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses but we cannot accept > responsibility for any loss or damage arising from the use of this > email and/or attachment(s). > > > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > [email protected] > If you use auto-responders (like out-of-the-office messages), make > sure that they are not sent to the list nor to individual members. > Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
