[ovirt-devel] oVirt log analyzer

[Barak Korren]

On 3 April 2018 at 12:55, Milan Zamazal <mzamazal at redhat.com> wrote:
> Barak Korren <bkorren at redhat.com> writes:
>
>> On 29 March 2018 at 21:11, Tomas Jelinek <tjelinek at redhat.com> wrote:
>>
>>>
>>>
>>> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta <gshereme at redhat.com>
>>> 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 <mzamazal at redhat.com>
>>>> 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, single or multiple log files) it tries
>>>>> to identify and classify important lines from the logs and present them
>>>>> in a structured form.  Its primary purpose is to get a quick and easy
>>>>> overview of actions and errors.
>>>>>
>>>>
>>> I would add that it can correlate more log files (from
>>> engine/vdsm/libvirt/quemu) and show a unified view of them.
>>> It can follow the life of one entity (such as a VM) and show what was
>>> going on with it across the system. I have used it a lot to look for races
>>> and it was pretty useful for that.
>>>
>>
>>
>> I wonder if we can automate running it on OST failures to get automated
>> failure analysis.
>
> Well, ovirt-log-analyzer doesn't provide failure analysis, it just tries
> to extract more important lines from the logs and add some information
> to them.  It may or may not be useful to add its output to OST failures
> in future, but some feedback and testing are needed first, I assume
> there are still bugs and things to improve.
>

I'll try to be more specific about the use case we're lookin at.

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 API
call that had been made, and use it to extract relevant information
about the call from the vdms and engine logs,

Can ovirt-log-analyzer be used for that?




-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted