Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1447790

Summary: Collect /var/log/messages (or journal output) from Engine as well
Product: [oVirt] ovirt-log-collector Reporter: Yaniv Kaul <ykaul>
Component: CoreAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0.0CC: bugs, stirabos, ykaul, ylavi
Target Milestone: ovirt-4.1.3Flags: rule-engine: ovirt-4.1+
rule-engine: exception+
pstehlik: testing_ack+
Target Release: 4.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-06 13:15:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1455781    

Description Yaniv Kaul 2017-05-03 20:20:53 UTC 
Description of problem:
I don't see it included, and I believe it times it might be helpful to pinpoint issues (such as connectivity, memory, CPU issues, etc.)
Comment 1 Sandro Bonazzola 2017-06-01 07:05:56 UTC 
(In reply to Yaniv Kaul from comment #0)
> Description of problem:
> I don't see it included, and I believe it times it might be helpful to
> pinpoint issues (such as connectivity, memory, CPU issues, etc.)

both message and journal are collected by logs plugin which is enabled on both engine and hosts.
Can you please re-check? It works for me on 4.1.2.
Comment 2 Yaniv Kaul 2017-06-01 07:15:15 UTC 
(In reply to Sandro Bonazzola from comment #1)
> (In reply to Yaniv Kaul from comment #0)
> > Description of problem:
> > I don't see it included, and I believe it times it might be helpful to
> > pinpoint issues (such as connectivity, memory, CPU issues, etc.)
> 
> both message and journal are collected by logs plugin which is enabled on
> both engine and hosts.
> Can you please re-check? It works for me on 4.1.2.

I don't see it in multiple logs from customer tickets I've looked at.
I am seeing it in hypervisor logs, exactly where I expect them to be:
[ykaul@ykaul sosreport-mmoser.01859573-20170530085809]$ find . -name messages
./var/log/messages
Comment 3 Sandro Bonazzola 2017-06-01 07:20:59 UTC 
(In reply to Yaniv Kaul from comment #2)
> (In reply to Sandro Bonazzola from comment #1)
> > (In reply to Yaniv Kaul from comment #0)
> > > Description of problem:
> > > I don't see it included, and I believe it times it might be helpful to
> > > pinpoint issues (such as connectivity, memory, CPU issues, etc.)
> > 
> > both message and journal are collected by logs plugin which is enabled on
> > both engine and hosts.
> > Can you please re-check? It works for me on 4.1.2.
> 
> I don't see it in multiple logs from customer tickets I've looked at.
> I am seeing it in hypervisor logs, exactly where I expect them to be:
> [ykaul@ykaul sosreport-mmoser.01859573-20170530085809]$ find . -name messages
> ./var/log/messages

I could reproduce, preparing a patch
Comment 4 Lucie Leistnerova 2017-06-20 08:08:31 UTC 
In sosreport from engine is /var/log/messages* secure* maillog and others.

verified in ovirt-log-collector-4.1.3-1.el7ev.noarch