Sadly 3 is the minimum (and is configurable per probe).
For a while I thought of deducting 2 from pings and have the users set
pings=3 if they wanted just one, but it's counterintuitive.
I will think about checking the interval and allow multiple pings (3
pings/hour should be fine for youtube I guess)...
I believe the ultimate power should be the user's, so the plugin should
be as configurable as possible even if it allows the user to shoot
himself in the foot. But I can't find an optimal way to have the plugin
run just once.
Hmm, maybe an extra parameter could be set up to honor "pings" or not...
Yup, that sounds like it would be the best of both worlds...
Thanks for the advice :)
On 06/12/15 09:33, Tobias Oetiker wrote:
Hi Adrian,
Today Adrian Popa wrote:
Great :)
I will look into how to merge my project with yours. If not possible, I will
try to readup on github to see how to transfer the modules with their change
history intact.
Thanks for the feedback.
There is one thing that might be a problem - the fact that I ignore the
"pings" variable and "fake" the results. The way it works is that I do only
one test and copy the results in as many array entries as needed by the pings
variable. This way you get the data, but no variance in the test interval.
I could enable it - to do $pings tests and let the end user worry about
getting banned (especially if he tries 20 downloads from youtube in 5
minutes), or leave it as it is and leave the warning sign.
the number of pings is configurable ... or is this global ?
you could make your probe check that only 1 ping is configured. or
maybe 3 is the minimum, not quite sure ...
also you could check the the interval is not too tight and complain
otherwhise ...
cheers
tobi
What do you think?
Cheers,
Adrian
On 06/12/15 00:56, Tobias Oetiker wrote:
Today Adrian Popa wrote:
Hello everyone,
I'd like to share with you a new probe I've been working on - integrating
speedtest-cli project to work with smokeping. The idea was that we needed
to
run some tests to get the customer's "experience" when using speedtest.net
with different test servers. We developed this probe, and measure the
upload/download rate the client's connection supports.
Plugin description and examples are here:
https://github.com/mad-ady/smokeping-speedtest
There is a bit of a deviation from standard plugins - meaning it ignores
the
pings variable and does only one test. This was done in order to prevent
the
IP getting banned for too agressive behavior by the speedtest.net servers.
It
can be reactivated - I'm open to ideas.
Here's a sample graph from a slave probe (1 hour polling):
http://imgur.com/cTJdHCS
@tobi: if you feel this plugin could be useful and should be included in
the
main release, let me know and I'll see how I can merge it...
sure ... bring it on :) the youtube one as well
cheers
tobi
Feedback welcome,
Regards,
Adrian
_______________________________________________
smokeping-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
--
TELEKOM ROMANIA
Adrian Popa
Expert Engineer
Applications, Security & EMS
35-37 Calea Victoriei, Palatul Telefoanelor
Mobile: +40 766 673 290
Phone: +40 21 400 7567
_______________________________________________
smokeping-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
