<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello Massimo,<br>
<br>
Thank you very much for your reply.<br>
<blockquote type="cite">You can anyway force to open the
measurement in ms (the same goes for all the other parameters)
if you embed the widget in your html page/monitor/dashboard.</blockquote>
That's exactly what I'm doing: I've created a web-page on my
internal web-server that contains the widget. However, I still
cannot find neither parameter nor API that would allow me to
select milliseconds. I've read through both documentation page you
pointed and poked JavaScript object returned by initLatencymon,
but still don't see it.<br>
<br>
That said, reference point in milliseconds appeared on charts
recently, that somewhat makes it less of a problem for me.<br>
<br>
<blockquote type="cite">
<div>The relative representation allows the user to focus on
change in the RTT over time and geographic space, instead of a
pure comparison among milliseconds of the various probes.</div>
<div>Following the user requests and according also to our
internal use, this is the most common use case, especially in
case of outage analysis.</div>
</blockquote>
My (mis)use case is different: I'm trying to monitor one
particular link that's important for me, using a single probe and
multiple nearby destinations. In this case absolute values matter:
relative charts may look absolutely normal while absolute values
are elevated from 1..2 to 10+ milliseconds because to link
overload which is not good.<br>
<br>
<div class="moz-signature"><!-- signature start -->
--<br>
<br>
With Best Regards,<br>
Marat Khalili<br>
<br>
<!-- signature end --></div>
On 09/05/16 18:25, Massimo Candela wrote:<br>
</div>
<blockquote cite="mid:779A20A4-8F75-497C-A44C-4F57B58C07B9@ripe.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="">Hi Marat,</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 13 Apr 2016, at 10:23, Marat Khalili <<a
moz-do-not-send="true" href="mailto:mkh@rqc.ru" class=""><a class="moz-txt-link-abbreviated" href="mailto:mkh@rqc.ru">mkh@rqc.ru</a></a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="content-type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""> I'm using <a
moz-do-not-send="true"
href="https://atlas.ripe.net/docs/tools-latencymon/"
class="">LatencyMON</a> widget to monitor my network
performance. It's very convenient. Unfortunately, it
always loads with latency shown in %% (of what?), not in
milliseconds, so I have to make one extra click in order
to view actual milliseconds. Is there some hidden switch
that would make milliseconds the default? Shouldn't it be
initially default in the first place?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div><br class="">
</div>
<div>Thanks for your comment, I will try to answer and give my
opinion.</div>
<div><br class="">
</div>
<div>Here you can find the documentation: <a
moz-do-not-send="true"
href="https://atlas.ripe.net/docs/tools-latencymon/"
class=""><a class="moz-txt-link-freetext" href="https://atlas.ripe.net/docs/tools-latencymon/">https://atlas.ripe.net/docs/tools-latencymon/</a></a></div>
<div>According to it: "The relative representation shows, in
percentages, how the values behave compared to the baseline,
which is the minimum latency collected in the time range for
the specific graph. Note that outliers have been removed.</div>
<div>For example, if the latencies collected oscillate between
30 and 90 ms, the y-axis will have a range between 0 and 200%,
as 30 ms will be considered the baseline and 90 ms represents
an increase of 200% over 30 ms.”</div>
<div><br class="">
</div>
<div>The relative representation allows the user to focus on
change in the RTT over time and geographic space, instead of a
pure comparison among milliseconds of the various probes.</div>
<div>Following the user requests and according also to our
internal use, this is the most common use case, especially in
case of outage analysis.</div>
<div>For example if you have a probe in Canada and one in Italy
and the target used in the measurement is in Germany, you
would expect to have some ms more from the one in Canada: this
information it’s just going to pollute the graphs.</div>
<div>Probably if something happens on the network you would like
to know which probes were affected and how. So what is the
difference in RTT compared to what is considered “normal” from
that source.</div>
<div><br class="">
</div>
<div>You can anyway force to open the measurement in ms (the
same goes for all the other parameters) if you embed the
widget in your html page/monitor/dashboard.</div>
<div><br class="">
</div>
<div>Sorry for the delay of the answer, for more information
feel free to contact me personally.</div>
<div><br class="">
</div>
<div>Ciao,</div>
<div>Massimo</div>
<div><br class="">
</div>
<div><br class="">
</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-signature"><br class="">
<!-- signature start --> --<br class="">
<br class="">
With Best Regards,<br class="">
Marat Khalili<br class="">
<!-- signature end --></div>
</div>
</div>
</blockquote>
</div>
<br class="">
</blockquote>
<br>
</body>
</html>