<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Every time we measure and graph something new, we discover
something we never could have predicted by looking at the hing we
set out to graph.</p>
<p>--dave<br>
</p>
<div class="moz-cite-prefix">On 2021-02-26 7:36 p.m., Jason Iannone
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGL1wDRAbtD72Sb9fu9R4xT4gnMq6MHNyCN0BOiVCofR4v73qg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Beyond getting acquainted with a new dataset? I'm
a transit network that supports, among other traffic types,
science flows. I think new monitoring methods can help identify
targets for intervention.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Feb 26, 2021, 4:06 PM
Toke Høiland-Jørgensen <<a href="mailto:toke@toke.dk"
target="_blank" rel="noreferrer" moz-do-not-send="true">toke@toke.dk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">TJason
Iannone <<a href="mailto:jason.iannone@gmail.com"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">jason.iannone@gmail.com</a>>
writes:<br>
<br>
> I ended up cloning the pping repo and running make
locally.<br>
><br>
> Installing was a few steps:<br>
><br>
> 1. mkdir ~/src/libtins/build<br>
> 2. cd ~/src/libtins/build<br>
> 2. git clone <a
href="https://github.com/mfontanini/libtins.git"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/mfontanini/libtins.git</a><br>
> 3. make<br>
> 4. sudo make install<br>
> 5. cd ~/src<br>
> 6. git clone <a
href="https://github.com/pollere/pping.git" rel="noreferrer
noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/pollere/pping.git</a><br>
> 7. cd pping<br>
> 8. make<br>
> 9. ./pping<br>
><br>
> The promise of this, as Kathleen Nichols points out, is
that we can<br>
> passively monitor production flows to get a novel sense
of end to end<br>
> performance per flow. I don't know of any other passive
monitoring<br>
> technique, beyond a port mirror + a whole gang of
systems, that can provide<br>
> this level of detail. Please enlighten me if I'm wrong.
The only other<br>
> passive monitoring mechanisms I'm aware of are SNMP
polling, IPFIX/*Flow,<br>
> and Streaming Telemetry Interface. None of those systems
provide end to end<br>
> flow performance details. The standard in-band active
monitoring tools are<br>
> good for determining node to node and full path metrics,
but this provides<br>
> a more complete picture of end to end performance beyond
active<br>
> y.1731/802.3ag/OAM probes. I'm a little surprised that
I'm only learning<br>
> about it now.<br>
<br>
What's your use case? :)<br>
<br>
-Toke<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Bloat mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net</a>
<a class="moz-txt-link-freetext" href="https://lists.bufferbloat.net/listinfo/bloat">https://lists.bufferbloat.net/listinfo/bloat</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
<a class="moz-txt-link-abbreviated" href="mailto:davecb@spamcop.net">davecb@spamcop.net</a> | -- Mark Twain
</pre>
</body>
</html>