Re: [ovirt-devel] oVirt log analyzer

2018-04-04 Thread Milan Zamazal
Piotr Kliczewski writes: > On Wed, Apr 4, 2018 at 10:47 AM, Milan Zamazal wrote: >> Barak Korren writes: >> > >>> Right now, when a test fails in OST - al you get is the traceback from >>> nose of the oVirt API cll you've made. For some tests additional >>> information is provided by having nis

Re: [ovirt-devel] oVirt log analyzer

2018-04-04 Thread Piotr Kliczewski
On Wed, Apr 4, 2018 at 10:47 AM, Milan Zamazal wrote: > Barak Korren writes: > >> Right now, when a test fails in OST - al you get is the traceback from >> nose of the oVirt API cll you've made. For some tests additional >> information is provided by having nise collect it from STDOUT. >> >> It

Re: [ovirt-devel] oVirt log analyzer

2018-04-04 Thread Milan Zamazal
Barak Korren writes: > Right now, when a test fails in OST - al you get is the traceback from > nose of the oVirt API cll you've made. For some tests additional > information is provided by having nise collect it from STDOUT. > > It could be very useful if we could use some information about the

Re: [ovirt-devel] oVirt log analyzer

2018-04-03 Thread Barak Korren
On 3 April 2018 at 12:55, Milan Zamazal wrote: > Barak Korren writes: > >> On 29 March 2018 at 21:11, Tomas Jelinek wrote: >> >>> >>> >>> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta >>> wrote: >>> Nice! I think a nice RFE would be to surface this info in the UI. On Thu, Mar 2

Re: [ovirt-devel] oVirt log analyzer

2018-04-03 Thread Milan Zamazal
Barak Korren writes: > On 29 March 2018 at 21:11, Tomas Jelinek wrote: > >> >> >> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta >> wrote: >> >>> Nice! I think a nice RFE would be to surface this info in the UI. >>> >>> On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal >>> wrote: >>> Hi, du

Re: [ovirt-devel] oVirt log analyzer

2018-04-03 Thread Milan Zamazal
Yaniv Kaul writes: > On Thu, Mar 29, 2018 at 9:11 PM, Tomas Jelinek wrote: > >> >> >> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta >> wrote: >> >>> Nice! I think a nice RFE would be to surface this info in the UI. >>> >>> On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal >>> wrote: >>> Hi

Re: [ovirt-devel] oVirt log analyzer

2018-04-02 Thread Yaniv Kaul
On Thu, Mar 29, 2018 at 9:11 PM, Tomas Jelinek wrote: > > > On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta > wrote: > >> Nice! I think a nice RFE would be to surface this info in the UI. >> >> On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal >> wrote: >> >>> Hi, during last year Outreachy intern

Re: [ovirt-devel] oVirt log analyzer

2018-03-29 Thread Barak Korren
On 29 March 2018 at 21:11, Tomas Jelinek wrote: > > > On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta > wrote: > >> Nice! I think a nice RFE would be to surface this info in the UI. >> >> On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal >> wrote: >> >>> Hi, during last year Outreachy internship a

Re: [ovirt-devel] oVirt log analyzer

2018-03-29 Thread Tomas Jelinek
On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta wrote: > Nice! I think a nice RFE would be to surface this info in the UI. > > On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal > wrote: > >> Hi, during last year Outreachy internship a tool for analyzing oVirt >> logs was created. When it is provid

Re: [ovirt-devel] oVirt log analyzer

2018-03-29 Thread Greg Sheremeta
Nice! I think a nice RFE would be to surface this info in the UI. On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal wrote: > Hi, during last year Outreachy internship a tool for analyzing oVirt > logs was created. When it is provided with oVirt logs (such as SOS > reports, logs gathered by Lago, s

[ovirt-devel] oVirt log analyzer

2018-03-29 Thread Milan Zamazal
Hi, during last year Outreachy internship a tool for analyzing oVirt logs was created. When it is provided with oVirt logs (such as SOS reports, logs gathered by Lago, single or multiple log files) it tries to identify and classify important lines from the logs and present them in a structured for