The Curl probe has a 'forks' option which determines how many requests
are run concurrently. Depending on available processing power,
bandwidth, etc, you may be able to turn that up some so that more probes
are run at the same time. You just have to be careful not to overload
your available bandwidth, or you'll artificially inflate response times. :p
Your lowering of the timeout will probably help significantly as well,
at least if it's often the case where hosts take longer than that to
respond.
- Peter
Pete Hoffswell wrote:
Hi Peter and list -
My log says:
Sep 12 10:29:50 networker3 smokeping[23449]: Curl: WARNING: smokeping took 430 seconds to complete 1 round of polling. It should complete polling in 300 seconds. You may have unresponsive devices in your setup.
How about that! You called it right, Peter.
I see that
Sep 12 10:19:13 networker3 smokeping[23449]: Curl: probing 21 targets with step
300 s and offset 160 s.
I do not have offset configured for curl, and expect it must be doing a random
offset. I will configure the offset for 0% to get them started right away.
I've also lowered the curl timeout to 5 seconds.
I would like to stay in the 300 second step if possible.
Any other suggestions? I have 95 rrd files in my smokeping directory tree.
It's not huge....
Thanks for the quick response.
Pete Hoffswell 616-732-1101 (x1101)
Network Manager 616-510-1198 (Mobile)
IT Services [EMAIL PROTECTED]
Davenport University http://www.davenport.edu
http://www.youtube.com/watch?v=jyV_zLKth3I
<[EMAIL PROTECTED]> 9/12/2007 11:50 AM >>>
Hi Pete;
When an RRD graph is blank, it means null/no data (meaning no data at
all was entered, like a NULL in a database, rather than a zero). With
SmokePing, typically this would occur if the daemon was turned off
during that time period, or e.g. if the probe crashed. One other
possible cause would be if SmokePing is not able to complete all probes
within the allotted cycle time (e.g. if it takes 330 seconds to run all
of the probes, but you are on a 300 second scan cycle, then some hosts
will get missed). Check your SmokePing log files to see what's going on
-- it will warn you if cycles are overlapping.
The other thing to do is correlate the information against something
else. For example, if you're monitoring servers and there is a blank
spot in SmokePing, did the server actually go down during that time?
Are there helpdesk tickets for that system in that timeframe? If the
server WAS down but the SmokePing graphs are blank, it could be a bug in
the Curl probe. If the servers were up at those times, it's more likely
the problem described in my first paragraph.
Cheers,
- Peter
Pete Hoffswell wrote:
Good day!
I have been encountering blank sections within trending charts on some
CURL probes. I would have expected them to go red, if there was no
response.
What does this mean? I cannot find in the documentation or searching
the list.
I've posted a representative graph here:
http://www.flickr.com/photos/petehoffswell/1366734130/
Anyone know why this happens?
Pete Hoffswell 616-732-1101 (x1101)
Network Manager 616-510-1198 (Mobile)
IT Services [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
Davenport University http://www.davenport.edu
<http://www.davenport.edu/>
http://www.youtube.com/watch?v=jyV_zLKth3I
------------------------------------------------------------------------
_______________________________________________
smokeping-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
_______________________________________________
smokeping-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
_______________________________________________
smokeping-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
