[atlas] Permanent private measurement

Morning Lorenzo,

If I've understood your problem, you have already found a way to make the
measurements from your probe but you don't like how the results are plotted.

There is a GIT repository  from Atlas with examples about how to get the
results in json format and print them using rrdtool.

You can even use a nice JavaScript library or import them to nagios or
zabbix.

Regards,

Daniel
Am 08.10.2015 3:56 vorm. schrieb "Lorenzo Colitti" <lorenzo at google.com>:

> On Wed, Oct 7, 2015 at 4:01 PM, Robert Kisteleki <robert at ripe.net> wrote:
>
>> > It's strange that I can't send one ping every 15 seconds, but there you
>> are.
>> > Also, the visualization is not as nice as the built-in measurements
>> (why?)
>> > but it seems to do what I want.
>>
>> If you could be a bit more specific (which visualisation?) then we can
>> check
>> what we can do about it.
>
>
> What I am really trying to do is what the built-in measurements do - run
> continuous measurements, from my probe only, to relevant targets on the
> Internet. I want to do this so I can measure the performance and
> reliability of my last-mile connectivity without factoring in any peering
> latency or anything else.
>
> I think this is what the built-in "traceroute second hop" measurement is
> intended to do, but that doesn't work for me because I (and the rest of my
> ISP's customers) am a variable number of hops away from the Internet. This
> is because the NTT NGN, unlike most unbundled access networks which use
> tunneling technologies such as L2TP or PPPoE, uses native IPv6. So the
> number of hops between customer and ISP network depends on NGN topology and
> routing.
>
> I worked around this by setting up a UDM that sends pings, but that's a
> bit of a hacky substitute, and as you say, the UDM visualizations aren't
> really geared to this use case.
>
> Also, the newly introduced latencymon is probably your best choice for this
>> kind of viz. See
>>
>> https://labs.ripe.net/Members/massimo_candela/new-ripe-atlas-tool-latencymon
>
>
> Latencymon sort of works (as does seismograph), but it's definitely not as
> nice as the built-in measurement UI.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20151008/eec4a1d5/attachment.html>