[smokeping-users] Holes in graphs
Peter Kristolaitis
alter3d at alter3d.ca
Wed Apr 22 19:37:26 CEST 2009
What you would do is create additional FPing probes:
*** Probes ***
+ FPing
binary = /usr/sbin/fping
++ FPing1
++ FPing2
++ FPing3
(optional: use offset=0%, 10%, 20%, etc, for each probe)
Then use those 'sub'-probes on some of your targets. It's easiest to do
it by host subtrees so that you're not managing each host
individually... in your case I see you've already split it up by letter
(e.g. SIP-A-E), so those might be good candidates. Simply override the
'probe' setting for the host group:
*** Targets ***
slaves=nycvpn001 laxvpn001
probe = FPing
+ SIP_Trunking
menu = SIP Trunking
title = SIP Trunking Customers
++ SIP-A-E
menu = Customers A-E
title = Customers A-E
probe = FPing1 # This group will use probe #1
@include include/sip-ae.cfg
++ SIP-F-L
menu = Customers F-L
title = Customers F-L
probe = FPing2 # This group will use probe #2
@include include/sip-fl.cfg
++ SIP-M-R
menu = Customers M-R
title = Customers M-R
probe = FPing3 # This group will use probe #3
@include include/sip-mr.cfg
Each probe runs as a separate process on the operating system, which
means that you're pinging more hosts in parallel. This has the effect
of consuming a bit more CPU and more instantaneous bandwidth, but gets
the round of probing done faster.
- Peter
Eric Chatham wrote:
>
> Thank you, Peter. I'm still looking at the example you gave and
> trying to figure out how this would work for our config file. Here is
> an example of our config file. The "+ SIP_Trunking" area is where the
> bulk of our graphs are at. And, we use an "include" directory for
> these configs.
>
>
>
> *** Probes ***
>
>
>
> + FPing
>
>
>
> binary = /usr/sbin/fping
>
>
>
> *** Targets ***
>
>
>
> slaves=nycvpn001 laxvpn001
>
>
>
> probe = FPing
>
>
>
> menu = Top
>
> title = Network Latency Grapher
>
> remark = Welcome to the SmokePing website of xxx. \
>
> Here you will learn all about the latency of our network..
>
> .
>
> .
>
> .
>
>
>
> ++LAX2NYC2
>
>
>
> menu = Combined PoP
>
> remark = Latency to VIPs on nyc6506-01 and lax6506-01
>
> alerts = someloss
>
> host = /Sonus/LAX2 /Sonus/NYC2
>
>
>
> ++LAX1NYC1
>
>
>
> menu = Combined Layer 2
>
> remark = Latency to VLAN IPs
>
> alerts = someloss
>
> host = /Sonus/LAX1 /Sonus/NYC1
>
>
>
> + TestCustomers
>
> menu = Prospect Customers
>
> title = SIP trunking prospect customers latency test
>
>
>
> @include include/siptr-customers.cfg
>
> @include include/config-temporary.txt
>
>
>
> + SIP-Term
>
> menu = SIP Term IP
>
> title = SIP termination carriers
>
>
>
>
>
> @include include/sip-term
>
>
>
> + SIP-Cust
>
> menu = SIP Customers
>
> title = SIP Customers
>
>
>
> @include include/sip-cust
>
>
>
> + SIP_Trunking
>
> menu = SIP Trunking
>
> title = SIP Trunking Customers
>
>
>
> ++ SIP-A-E
>
> menu = Customers A-E
>
> title = Customers A-E
>
>
>
> @include include/sip-ae.cfg
>
>
>
> ++ SIP-F-L
>
> menu = Customers F-L
>
> title = Customers F-L
>
>
>
> @include include/sip-fl.cfg
>
>
>
> ++ SIP-M-R
>
> menu = Customers M-R
>
> title = Customers M-R
>
>
>
> @include include/sip-mr.cfg
>
>
>
> ++ SIP-S-Z
>
> menu = Customers S-Z
>
> title = Customers S-Z
>
>
>
> @include include/sip-sz.cfg
>
>
>
> + Temporary
>
> menu = Temporary
>
> title = Temporary
>
>
>
> @include include/temporary
>
>
>
> + Broadvox_Employees
>
> menu = Employees
>
> title = Broadvox Employees
>
>
>
> @include include/employees.cfg
>
>
>
> /Eric Chatham/
>
> /Broadvox MIS Department/
>
> /(216) 373-4683/
>
> /echatham at broadvox.net/
>
>
>
> *From:* Peter Kristolaitis [mailto:alter3d at alter3d.ca]
> *Sent:* Wednesday, April 22, 2009 10:26
> *To:* Eric Chatham
> *Cc:* smokeping-users at lists.oetiker.ch
> *Subject:* Re: [smokeping-users] Holes in graphs
>
>
>
> For multiple pollers, check out example #3 at
> http://oss.oetiker.ch/smokeping/doc/smokeping_examples.en.html
>
> Smokeping typically uses syslog for its logging, so the specific
> configuration is highly dependent on your environment. Check your
> Smokeping config file to see if logging is even enabled, and if so,
> what facility and priority are being used. From there you should be
> able to figure out what log file things are going to.
>
>
>
>
> Eric Chatham wrote:
>
> Hi Peter,
>
>
>
> Where is the Smokeping logfile located at? I tried /var/log/messages,
> but I don't see anything in there for Smokeping.
>
>
>
> Also, how would I setup multi-pollers, as you suggested? If I did
> reset the step/ping configurations, how would that affect the RRD
> files? How would I modify them?
>
>
>
> Thanks, again. :)
>
>
>
> /Eric Chatham/
>
>
>
> *From:* Peter Kristolaitis [mailto:alter3d at alter3d.ca]
> *Sent:* Wednesday, April 22, 2009 09:51
> *To:* Eric Chatham
> *Cc:* smokeping-users at lists.oetiker.ch
> <mailto:smokeping-users at lists.oetiker.ch>
> *Subject:* Re: [smokeping-users] Holes in graphs
>
>
>
> Hi Eric;
>
> Check your SmokePing logs to see if you're getting a message similar
> to "1 round of polling was longer than step" (or something similar, I
> can't remember the exact error at the moment).
>
> If you are getting that message, then there are a few ways to fix it:
>
> - Increase step time
> - Decrease ping count
> - Run multiple pollers and split up the hosts to use them.
>
> Running multiple pollers if you're not already is probably the easiest
> fix, because changing the step or ping count will require modifying
> your RRD files.
>
> - Peter
>
>
>
> Eric Chatham wrote:
>
> Hello,
>
>
>
> Is there any way to minimize -- if not get rid of -- the holes in the
> graphs? I've noticed that when a customer is no longer reachable with
> the FPing probe, we start seeing holes consistent in all the graphs.
> Would increasing the step help correct this? Right now, I have the
> step set at 120, and pings set to 20. We monitor over 100 customers
> with Smokeping and we use two slaves (one slave in NY and the other
> LA). Thank you for any advice on how to correct this.
>
>
>
> Sincerely,
>
> /Eric Chatham/
>
>
>
> ------------------------------------------------------------------------
>
> CONFIDENTIAL. This e-mail and any attached files are confidential and
> should be destroyed and/or returned if you are not the intended and
> proper recipient.
>
>
>
>
> ------------------------------------------------------------------------
>
>
>
>
>
>
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch <mailto:smokeping-users at lists.oetiker.ch>
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> CONFIDENTIAL. This e-mail and any attached files are confidential and
> should be destroyed and/or returned if you are not the intended and
> proper recipient.
>
>
>
>
> ------------------------------------------------------------------------
> CONFIDENTIAL. This e-mail and any attached files are confidential and
> should be destroyed and/or returned if you are not the intended and
> proper recipient.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20090422/bb52a427/attachment-0001.html
More information about the smokeping-users
mailing list