Hello Toby,

After merging the files, certain columns are missing. These columns also cannot be selected manually, as they are missing from the selection options as well.
For example, I have a column "TgmName" that is missing in the merged files and also cannot be selected.
I would expect the structure of the columns in the merged files to be the same as in the individual files.

Single file:


Merged files:



Best regards,
Stefan

Hi Stefan,

That's very strange behaviour.  I have just merged some CSV files locally and I can see the the columns are merging as expected.  What version of LogViewPlus are you using?

LogViewPlus stores column information as part of the parser configuration.  It looks like the columns being shown are standard columns that LogViewPlus shows even when the BasicParser is used.  Are all of your files are using the same parser configuration?  Is this behaviour repeatable after restarting LogViewPlus?

Thanks for reporting this issue,

Toby

Hi Toby

I have the latest version 3.1.15.
Yes, all files use the same parser "mm.ClcLib.log"
Refernce Name: mm.ClcLib.log
File Name Pattern: *_MmClc.csv
Parser: DsvParser
Arguments: %d{yyyy-MM-ddT%H:mm:ss.fff};%p;%S{Direction} ;%S{TgmName} ; %S{TgmCtr} ;%s{Data}%n



Example of a csv:
2024-10-29T17:53:54.233;TRACE;APP->CLC;MmClcSpeeds;3905;Data=[3,6.75,7.13889,ok]
2024-10-29T17:53:54.816;TRACE;APP->CLC;MmClcCycleEvent;21198;Data=[1,2,2147485470,0,467565000019,BCRS_READ,PRD_STATE_OK,COUNTTYPE_PRODUCTIVE,0.0.0.0,ok,A:2,PRS:CPRS_RUNNING_PRODUCTIVE]
2024-10-29T17:53:55.273;TRACE;APP->CLC;MmClcSpeeds;3906;Data=[3,6.75,7.05556,ok]
2024-10-29T17:53:56.313;TRACE;APP->CLC;MmClcSpeeds;3907;Data=[3,6.75,7.11111,ok]
2024-10-29T17:53:56.979;TRACE;APP->CLC;MmClcCycleEvent;21255;Data=[2,45,2147485470,0,467565000026,BCRS_READ,PRD_STATE_OK,COUNTTYPE_PRODUCTIVE,0.0.0.0,ok,A:45,PRS:CPRS_RUNNING_PRODUCTIVE]
2024-10-29T17:53:57.353;TRACE;APP->CLC;MmClcSpeeds;3908;Data=[3,6.75,7.05556,ok]
2024-10-29T17:53:57.873;TRACE;APP->CLC;MmClcSpeeds;3909;Data=[3,6.75,7.11111,ok]

I have always this behavior, also after restart.
Regards Stefan

Those log entries are parsing OK for me.  I pasted two entries into four separate log files.



If you right click on a file, you can see the file properties which confirm the parsing being used:



Are all four files using the same parser?  Maybe you have another configuration which is a direct match for a given file?

Hi Toby
I have deleted all my Parser Mappings and reconfigured them with the same settings as bevor. Now it is working. Strange, but it is ok for me by now.

Thanks Stefan

Thanks for letting me know Stefan. 

I think you might have unknowningly had a parser configuration which was causing a conflict.  With automatic parser configuration, this is easilly done by clicking 'OK' to accept the suggested configuration.  Sometimes suggested configurations can differ significantly based on the data found in the file.

Thanks again,

Toby