<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I use ltop heavily:</p>
<p><a class="moz-txt-link-freetext" href="https://github.com/LLNL/lmt">https://github.com/LLNL/lmt</a><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/20/18 9:15 AM, Alexander I Kulyavtsev wrote:<br>
</div>
<blockquote type="cite" cite="mid:CY4PR09MB1270A1862C2FE4479E9EA7A2CCBF0@CY4PR09MB1270.namprd09.prod.outlook.com">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">1) cerebro + ltop still work.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">2) telegraf + inflixdb (collector, time series DB ). Telegraf has input plugins for lustre ("lustre2"), zfs, and many others. Grafana to plot live data from DB. Also, influxDB integrates with Prometheus.</p>
<p style="margin-top:0;margin-bottom:0">Basically, each component can feed data to different output types through plugins; or take data from multiple type of sources so you can use different combination for your monitoring stack.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">For the simplest tool you may take a look if telegraf from influxdb stack has proper output plugin <span style="font-family: Calibri, Helvetica,
sans-serif, Helvetica, EmojiFont, "Apple Color
Emoji", "Segoe UI Emoji", NotoColorEmoji,
"Segoe UI Symbol", "Android Emoji",
EmojiSymbols; font-size: 16px;">(see
influxdata </span><span style="font-family: Calibri, Helvetica, sans-serif,
Helvetica, EmojiFont, "Apple Color Emoji",
"Segoe UI Emoji", NotoColorEmoji, "Segoe UI
Symbol", "Android Emoji", EmojiSymbols;
font-size: 16px;">on
github).</span></p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Alex.</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> lustre-discuss
<a class="moz-txt-link-rfc2396E" href="mailto:lustre-discuss-bounces@lists.lustre.org">
<lustre-discuss-bounces@lists.lustre.org></a> on behalf of Laifer, Roland (SCC) <a class="moz-txt-link-rfc2396E" href="mailto:roland.laifer@kit.edu">
<roland.laifer@kit.edu></a><br>
<b>Sent:</b> Thursday, December 20, 2018 8:04:55 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:lustre-discuss@lists.lustre.org">
lustre-discuss@lists.lustre.org</a><br>
<b>Subject:</b> [lustre-discuss] Command line tool to monitor Lustre I/O ?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Dear Lustre administrators,<br>
<br>
what is a good command line tool to monitor current Lustre metadata and<br>
throughput operations on the local client or server? Up to now we had<br>
used collectl but this no longer works for Lustre 2.10.<br>
<br>
Some background about collectl: The Lustre support of collectl was<br>
removed many years ago but up to Lustre 2.7 it was still possible to<br>
monitor metadata and throughput operations on clients. In addition,<br>
there were plugins which also worked for the server side, see<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.lustre.org_Collectl&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=23V5nhLj03jeTboyg6QveA&m=RpMjhssRJoiP3ANRP6Ze3_nBrliMMPOgQaewqEwRTn4&s=QmdmoNcRR5A0sOgiJimMo0KtZnc-ne44A4YY8aSWbuI&e=" moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.lustre.org_Collectl&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=23V5nhLj03jeTboyg6QveA&m=RpMjhssRJoiP3ANRP6Ze3_nBrliMMPOgQaewqEwRTn4&s=QmdmoNcRR5A0sOgiJimMo0KtZnc-ne44A4YY8aSWbuI&e=</a><br>
However, it seems that there was no update for these plugins to adapt<br>
them for Lustre 2.10.<br>
<br>
Regards,<br>
Roland<br>
_______________________________________________<br>
lustre-discuss mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lustre.org_listinfo.cgi_lustre-2Ddiscuss-2Dlustre.org&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=23V5nhLj03jeTboyg6QveA&m=RpMjhssRJoiP3ANRP6Ze3_nBrliMMPOgQaewqEwRTn4&s=SXbueuHkxyBAq95D_-bLmBayRVDMtR-l7t0XZfNXEXk&e=" moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lustre.org_listinfo.cgi_lustre-2Ddiscuss-2Dlustre.org&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=23V5nhLj03jeTboyg6QveA&m=RpMjhssRJoiP3ANRP6Ze3_nBrliMMPOgQaewqEwRTn4&s=SXbueuHkxyBAq95D_-bLmBayRVDMtR-l7t0XZfNXEXk&e=</a><br>
</div>
</span></font></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
lustre-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a>
<a class="moz-txt-link-freetext" href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a>
</pre>
</blockquote>
</body>
</html>