We use a simple bat file to monitor our wan links at work. It basically checks the wan link and compares to last known state and logs any difference and emails. <span></span>Then it repeats this in a loop. You could do something similar with the scripting language of your choice. <br>
<br>On Friday, December 13, 2013, Gregory Sloop wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You can shorten the polling time - I typically use 60 seconds. But if<br>
the outages are shorter than a minute on average, say 10 seconds, then<br>
SP probably isn't the tool to use.<br>
<br>
I've looked at a few tool to handle corner cases sort of like yours,<br>
and there's not a lot out there - and I don't recall what I found.<br>
<br>
In Windows, pathping works pretty well. There's a similar tool for<br>
*nix, and I've thought about using a |pipe script to kick it off when<br>
smokeping kicks off an alert.<br>
<br>
...ah MTR - that's what I was thinking of. Again, MTR isn't a perfect<br>
tool for you either.<br>
<br>
Anyway - I think in general you're headed in the right direction. If<br>
the outages are very transient and quick, SP and Nagios are poor tools<br>
to monitor those with.<br>
<br>
The python idea sounds good, though I'd probably just log to a flat file,<br>
which seems easier.<br>
<br>
-Greg<br>
<br>
<br>
B> Hi Greg,<br>
<br>
B> first of all thanks for your answer!<br>
B> My problem is that my router looses its DSL synchronism to the Outdoor<br>
B> DSLAM. (I can see that from the router logs)<br>
B> It the needs about 30 Seconds to reconnect. Sometimes it takes hours,<br>
B> but that's not often the case.<br>
B> The short disconnects usually happen in short intervals which makes it<br>
B> impossible to watch a youtube video or something like that.<br>
<br>
B> But i think i write some small python script that pings some servers,<br>
B> store the binary result and generate graphs from it using RRDtool.<br>
<br>
B> But anyway, Smokeping works nice if it is used for what it is supposed<br>
B> to do :)<br>
<br>
B> Am 13.12.2013 16:56, schrieb Gregory Sloop:<br>
>> Sorry - forgot to send to the list:<br>
>> ---<br>
>> That's the very nature of SP.<br>
>><br>
>> It doesn't really give only a binary state, unless the connection is<br>
>> totally down - that's, again, the point of smokeping - where there's<br>
>> smoke, there's usually fire.<br>
>><br>
>> If you're sending 20 fpings that all have different RTT, some are lost<br>
>> some aren't etc - how do I give you a binary state? If I lost 5% of<br>
>> the packets, should I tell you the thing is down?<br>
>><br>
>> No, you look at the colors of the plot points to tell what packet loss<br>
>> is. You look at the smoke and the positioning of the plot to tell RTT<br>
>> and variances.<br>
>><br>
>> If you really want raw data, you can dump the RDD database with<br>
>> RDDDump [iirc] but it's not very useful, IMO.<br>
>><br>
>> If you really want black/white state data, then use Nagios. It will<br>
>> handle alerting better, and give you very straight-forward logs of<br>
>> what was up or down and when.<br>
>><br>
>> But Nagios is bad as a leading diagnostic indicator. It won't tell you<br>
>> about a connection that has RTT times that are trending up, or packet<br>
>> loss that, while not 100% is above some threshold and increasing.<br>
>><br>
>> So, IMO, you'll either have to live with SP and the way it "sees" the<br>
>> world, or use a tool that's more appropriate for your wants. Because<br>
>> right now, you've got the saw out and you're complaining about how it<br>
>> pounds nails badly.<br>
>><br>
>> And you're right. The saw does pound nails badly.<br>
>> But it saws nicely. I think you can accomplish the task at hand with<br>
>> the saw, but if you insist on pounding nails, well then you ought to<br>
>> switch to the hammer.<br>
>><br>
>> :)<br>
>><br>
>> -Greg<br>
>><br>
>> B> Hi,<br>
>><br>
>> B> i've set up smokeping successfully on a Raspberry Pi to monitor my<br>
>> B> internet connectivity at home.<br>
>> B> The reason is that i had a lot of disconnects during the last days<br>
>> and i<br>
>> B> want to show the graphs to my provider if this does not getting<br>
>> better.<br>
>> B> But the FPing graphs seems to be "antialiased" for me. Is there<br>
>> another<br>
>> B> probe or a way to show the graph as a clear line indicating whether<br>
>> a<br>
>> B> internet connection is available or not using ping time average and<br>
>> B> timeout?<br>
>><br>
>> B> Thanks<br>
>><br>
>> B> Elias<br>
>><br>
>> B> _______________________________________________<br>
>> B> smokeping-users mailing list<br>
>> B> <a>smokeping-users@lists.oetiker.ch</a><br>
>> B> <a href="https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users" target="_blank">https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users</a><br>
>><br>
>> --<br>
>> Gregory Sloop, Principal: Sloop Network & Computer Consulting<br>
>> Voice: 503.251.0452 x82<br>
>> EMail: <a>gregs@sloop.net</a><br>
>> <a href="http://www.sloop.net" target="_blank">http://www.sloop.net</a><br>
>> ---<br>
>><br>
>><br>
>> B> Hi,<br>
>><br>
>> B> i've set up smokeping successfully on a Raspberry Pi to monitor my<br>
>> B> internet connectivity at home.<br>
>> B> The reason is that i had a lot of disconnects during the last days<br>
>> and i<br>
>> B> want to show the graphs to my provider if this does not getting<br>
>> better.<br>
>> B> But the FPing graphs seems to be "antialiased" for me. Is there<br>
>> another<br>
>> B> probe or a way to show the graph as a clear line indicating whether<br>
>> a<br>
>> B> internet connection is available or not using ping time average and<br>
>> B> timeout?<br>
>><br>
>> B> Thanks<br>
>><br>
>> B> Elias<br>
>><br>
>> B> _______________________________________________<br>
>> B> smokeping-users mailing list<br>
>> B> <a>smokeping-users@lists.oetiker.ch</a><br>
>> B> <a href="https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users" target="_blank">https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users</a><br>
</blockquote>