[automated-testing] how does glusto based testing handle logging?

[Jonathan Holloway]

Hi Sankarshan,

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.
Above that, the gluster libraries either write to the main Glusto log or
create their own logger for the tests themselves.
For collection of those and logs at the system layer (syslog, Gluster,
etc), the automation is handled at the Jenkins level.

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.
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.

Someone can correct me, but I think the closest we have right now is the
sosreport generated and stored after the test downstream.

Cheers,
Jonathan


On Mon, Apr 29, 2019 at 12:20 AM Sankarshan Mukhopadhyay <
sankarshan.mukhopadhyay at gmail.com> wrote:

> This is practically a 2 part question:
>
> + negative scenarios in Glusto ie. where not-expected behavior happens
> + handling logging for such negative paths
>
> In summary, does setting up Glusto also set up an ELK (or, similar
> stack) for centralized logging?
> _______________________________________________
> automated-testing mailing list
> automated-testing at gluster.org
> https://lists.gluster.org/mailman/listinfo/automated-testing
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20190429/45966d60/attachment.html>