I could do with some help on this one...
Our systems generate various text based logs where the format is always "yyyy-mm-dd hh:mm:ss.xxx" (where xxx is msec.) and then followed by a null terminated message.
I think it should be possible to use BC to 'compare' two log files and make BC align them so that both logs are sorted in chronological order.
Or: only events that occured at exactly the same time would be aligned.
Successful alignments would be rather unlikely, but the comparison would still be very useful to us as it enables us to unfold the sequence of events.
Using the DataViewer plug-in, I was partly successful in the chronological alignment by using the 'Fixed Column Fields', creating two fields with the first field ending at column 23 (end of timestamp) and the second column - because the plug-in leaves no alternative - I gave a width of 255.
The first column (timestamp) was declared 'key', the second (message) was declared 'unimportant'.
With the option to 'sort tables by key columns' checked, BC had no problems getting the timestamps nicely aligned and sorted in chronological order
However, the second column was rendered illegible due to the fixed width of 255 chars.
Is there any other way of getting timestamped lines aligned in chronological order without garbling the message?
Perhaps even by using a different plug-in?
Iwar
Our systems generate various text based logs where the format is always "yyyy-mm-dd hh:mm:ss.xxx" (where xxx is msec.) and then followed by a null terminated message.
I think it should be possible to use BC to 'compare' two log files and make BC align them so that both logs are sorted in chronological order.
Or: only events that occured at exactly the same time would be aligned.
Successful alignments would be rather unlikely, but the comparison would still be very useful to us as it enables us to unfold the sequence of events.
Using the DataViewer plug-in, I was partly successful in the chronological alignment by using the 'Fixed Column Fields', creating two fields with the first field ending at column 23 (end of timestamp) and the second column - because the plug-in leaves no alternative - I gave a width of 255.
The first column (timestamp) was declared 'key', the second (message) was declared 'unimportant'.
With the option to 'sort tables by key columns' checked, BC had no problems getting the timestamps nicely aligned and sorted in chronological order
However, the second column was rendered illegible due to the fixed width of 255 chars.
Is there any other way of getting timestamped lines aligned in chronological order without garbling the message?
Perhaps even by using a different plug-in?
Iwar
Comment