Re: [ovirt-devel] oVirt log analyzer
Piotr Kliczewski <piotr.kliczewski(a)gmail.com> writes:
On Wed, Apr 4, 2018 at 10:47 AM, Milan Zamazal
<mzamazal(a)redhat.com> wrote:
> Barak Korren <bkorren(a)redhat.com> 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 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?
>
> Maybe, but not out of the box. It can parse logs and find some
> relations between Engine and Vdsm logs, so it might be extended to do
> that. However it's more focused on guess work. Depending on kind of
> the information to be provided there could be simpler ways to get it.
Is correlation id not enough to find the relations?
It is enough to find relations between API calls and something like grep
may be easier to use for that than ovirt-log-analyzer. Again, it
depends on what kind of information should be provided.