The IBM CORAL project requires that we take the console log and coorelate events in it along with all other logs in the system. this requires timestamps on every line.
Looking in conserver.pm in the xcat source I see this hard coded:
push @newheaders,"default * {\n";
push @newheaders," logfile /var/log/consoles/&;\n";
push @newheaders," timestamp 1hab;\n";
push @newheaders," rw *;\n";
push @newheaders," master localhost;\n";
We need the ability to be able to control the contents of the timestamp value and change it to "timestamp 1l;".
Is it possible to add this is a feature for future releases.
We are replacing conserver with a xCAT-developed tool named confluent, but I think this is a reasonable requirement for both conserver based console and confluent based console.
Victor, could you help on this bug? Thanks.
I did some quick experiment, changing the timestamp line in /etc/conserver.cf to be "timestamp 1lab" does trigger the conserver to log timestamp for each line.
We might need to evaluate if this will bring in any performance overhead by enabling the per-line timestamp in the console log.
Needs to verify replaycons also works with the per line timestamp
I am out of the office until 07/20/2015.
I will respond to your message when I return.
Note: This is an automated response to your message "[xcat:bugs] #4581
conserver always configures for 1 hour timestamps. we need timestamps per
line." sent on 07/06/2015 4:45:47 AM.
This is the only notification you will receive while this person is away.