[smokeping-users] Pointers at code

[Gregory Sloop]

So, I had an odd case in the last couple of weeks.

Pretext:
---
In short, a particular host [it was the client's router] suddenly went into a state of VERY HIGH latency. Like 600-1000ms of latency. It stayed that way for days/weeks. Since most of my clients internet connections are essentially consumer grade connections and usage is pretty variable - I've tended to set the latency thresholds really high.

[I don't actually send alerts on latency with smokeping, I do that with Nagios/OMD. But you'll see how that applies in a bit.]

Even then, I've got the current latency thresholds set really high - because if the client starts uploading a huge set of files, latency is going to go through the roof, and I don't want alerts about "normal" conditions - especially if they're limited in duration. That big upload that lasts two hours is "normal." I don't want to get alerts about it. But if latency goes from 20ms to 60ms for 24 hours, then that would be worth knowing about. 

But there's no way to trigger in smokeping or Nagios on *average* data, only, really, on instantaneous measurements. [And yes I understand the triggers in smokeping are far more capable than those in Nagios - but even then, they still only get a small way there, IMO.]

Problem/solution:
---
So, where this brings me is that I realize that using the smokeping data, I could pull *average* latency over say 4/6/10/40 hours. That would be way more useful. Nagios could grab instantaneous latencies over say 4 hours, but not averages.

Yet, I'm a total hack when it comes to coding. So, I need all the help I can get.

I'm wanting to tweak a Nagios plug-in that uses the smokeping RRD's so that it queries average latencies.
Is there someone [Tobi!?!] who could point me at some code that shows me how to query the RRD to get average latencies? [A particular file+line-number in the current source, perhaps?]

And as I think about it more, average packet-loss and jitter would probably be really interesting things to look at too - not just latency.

---
Or perhaps someone has a better idea, that gets at the same general problem.

TIA!
-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20181105/53cf69cc/attachment.html>