<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Marat,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 May 2016, at 09:20, Marat Khalili <<a href="mailto:mkh@rqc.ru" class="">mkh@rqc.ru</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">Hello Massimo,<br class="">
<br class="">
Thank you very much for your reply.<br class="">
<blockquote type="cite" class="">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 class=""></div></div></div></blockquote><div><br class=""></div><div>Option 1: Set the parameter in the embed code (more info at the end of the documentation page)</div><div><table class="table table-responsive table-striped" style="box-sizing: border-box; border-spacing: 0px; border-collapse: collapse; width: 1172px; max-width: 100%; margin-bottom: 20px; color: rgb(51, 51, 51); font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14.3px; line-height: 22.88px; widows: 1; background-color: rgb(255, 255, 255);"><tbody style="box-sizing: border-box;" class=""><tr style="box-sizing: border-box;" class=""><td style="box-sizing: border-box; padding: 8px; line-height: 1.42857; vertical-align: top; border-top-width: 1px; border-top-style: solid; border-top-color: rgb(221, 221, 221); background-color: rgb(249, 249, 249);" class="">dataFilter</td><td style="box-sizing: border-box; padding: 8px; line-height: 1.42857; vertical-align: top; border-top-width: 1px; border-top-style: solid; border-top-color: rgb(221, 221, 221); background-color: rgb(249, 249, 249);" class="">[string] The data filter name to be used (i.e. natural or relative).</td></tr></tbody></table><div class="">So practically you need something like:</div><div class="">{<br class=""> dataFilter: "natural",<br class=""> measurements:[MSM_ID1, MSM_ID2]<br class="">}</div><div class=""><br class=""></div><div class="">in your query options map (third parameter of initLatencymon).</div><div class="">In this way the widget will load the measurement with all the default parameters you set.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">If you want to change it at execution time:</div><div class="">- open your browser console;</div><div class="">- latencymon.shell().setDataFilter(“natural”), where latencymon is the object returned by initLatencymon()</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Be careful: don’t simply reload the page, remove all the parameters in the permalink. The permalink has priority so if in the permalink you have another filter, this will overwrite the one specified in the embed code.</div></div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><div class="moz-cite-prefix">
<br class="">
That said, reference point in milliseconds appeared on charts
recently, that somewhat makes it less of a problem for me.<br class=""></div></div></div></blockquote><div><br class=""></div><div>;)</div><div><br class=""></div><div>But anyway try the solution before, it will fit better your case.</div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><div class="moz-cite-prefix">
<br class="">
<blockquote type="cite" class="">
<div class="">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 class="">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 class="">
<br class=""></div></div></div></blockquote><div><br class=""></div>Let me know if everything is fine!</div><div><br class=""></div><div>Ciao,</div><div>Massimo</div><div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><div class="moz-cite-prefix">
<div class="moz-signature"><!-- signature start -->
--<br class="">
<br class="">
With Best Regards,<br class="">
Marat Khalili<br class="">
<br class="">
<!-- signature end --></div>
On 09/05/16 18:25, Massimo Candela wrote:<br class="">
</div>
<blockquote cite="mid:779A20A4-8F75-497C-A44C-4F57B58C07B9@ripe.net" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div class="">Hi Marat,</div>
<br class="">
<div class="">
<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><a class="moz-txt-link-abbreviated" href="mailto:mkh@rqc.ru">mkh@rqc.ru</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 class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Thanks for your comment, I will try to answer and give my
opinion.</div>
<div class=""><br class="">
</div>
<div class="">Here you can find the documentation: <a moz-do-not-send="true" href="https://atlas.ripe.net/docs/tools-latencymon/" class=""></a><a class="moz-txt-link-freetext" href="https://atlas.ripe.net/docs/tools-latencymon/">https://atlas.ripe.net/docs/tools-latencymon/</a></div>
<div class="">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 class="">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 class=""><br class="">
</div>
<div class="">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 class="">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 class="">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 class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">Sorry for the delay of the answer, for more information
feel free to contact me personally.</div>
<div class=""><br class="">
</div>
<div class="">Ciao,</div>
<div class="">Massimo</div>
<div class=""><br class="">
</div>
<div class=""><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 class="">
</div>
</div></blockquote></div><br class=""></div></body></html>