<div dir="ltr">I use the exact same setup along with Kapacitor for alerting (alerta as the dash). We have created have dozens of panels in Grafana that are very useful for troubleshooting bottlenecks with the OSS nodes, disks, as well as the clients. <div> </div><div>Can't go wrong with it I feel, easy to setup and fun to make graphs :-)</div><div><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Dec 20, 2018 at 12:15 PM Alexander I Kulyavtsev <<a href="mailto:aik@fnal.gov">aik@fnal.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div id="gmail-m_2137996345489770313divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir="ltr">
<p style="margin-top:0px;margin-bottom:0px">1) cerebro + ltop still work.</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">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:0px;margin-bottom:0px">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:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">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:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">Alex.</p>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_2137996345489770313divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> lustre-discuss <<a href="mailto:lustre-discuss-bounces@lists.lustre.org" target="_blank">lustre-discuss-bounces@lists.lustre.org</a>> on behalf of Laifer, Roland (SCC) <<a href="mailto:roland.laifer@kit.edu" target="_blank">roland.laifer@kit.edu</a>><br>
<b>Sent:</b> Thursday, December 20, 2018 8:04:55 AM<br>
<b>To:</b> <a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">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="gmail-m_2137996345489770313BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="gmail-m_2137996345489770313PlainText">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=" target="_blank">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 href="mailto:lustre-discuss@lists.lustre.org" target="_blank">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=" target="_blank">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>
</div>
_______________________________________________<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org" rel="noreferrer" target="_blank">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><br>
</blockquote></div>