<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 29, 2019 at 7:17 PM Sankarshan Mukhopadhyay <<a href="mailto:sankarshan.mukhopadhyay@gmail.com">sankarshan.mukhopadhyay@gmail.com</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">On Mon, Apr 29, 2019 at 9:05 PM Jonathan Holloway <<a href="mailto:jholloway@redhat.com" target="_blank">jholloway@redhat.com</a>> wrote:<br>
<br>
> In a nutshell, no. Glusto itself only sets up a main Python logger for the Glusto library to write to, typically when a test is run via /usr/bin/glusto.<br>
> Above that, the gluster libraries either write to the main Glusto log or create their own logger for the tests themselves.<br>
> For collection of those and logs at the system layer (syslog, Gluster, etc), the automation is handled at the Jenkins level.<br>
><br>
<br>
I think this leads to a design decision around how a Glusto instance<br>
for Gluster would need to have a centralized logging or, at the very<br>
least, rsyslog configured. Logs resulting from failed tests are a good<br>
place to start for patterns and identify remedial approaches.<br></blockquote><div><br></div><div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">Is the question about Gluso logging or Gluster? I thought the latter...</div></div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">It's also a feature of Gluster, to log to syslog, so would be good to add the capability to test that.</div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">I believe it should be easy(TM) to add to the client (1st client) such configuration.</div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">I'll add it to the queue.</div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> A centralized solution for test and log analysis is on the CCIT roadmap in QE, and I'm working with Data Hub for the Log File Analysis aspect using their Elastic.<br>
> Framework (PyTest, Glusto, etc.) and test logs generated by the gluster-specific libraries would be included in logs collected by the system, but setup for collation of that log data would be a level higher.<br>
><br>
> Someone can correct me, but I think the closest we have right now is the sosreport generated and stored after the test downstream.<br>
<br>
I'm not sure who can respond to this.<br>
_______________________________________________<br>
automated-testing mailing list<br>
<a href="mailto:automated-testing@gluster.org" target="_blank">automated-testing@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/automated-testing" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/automated-testing</a><br>
</blockquote></div></div>