Hello!
Currently log parser cannot expand single <file> entry into multiple files. You can use timestamp macros or external scripts to monitor files with changing names, but not changing set of files simultaneously.
You can safely ignore <logName> tag. It is purely cosmetic issue - instead of omitting it altogether if not set (as with other tags) code that generates XML always put it. This tag can be used to specify Windows event log name to filter by specific log (useful for Windows event synchronization).
Macros section moving to the bottom is a bug - we will fix it.
Best regards,
Victor
Currently log parser cannot expand single <file> entry into multiple files. You can use timestamp macros or external scripts to monitor files with changing names, but not changing set of files simultaneously.
You can safely ignore <logName> tag. It is purely cosmetic issue - instead of omitting it altogether if not set (as with other tags) code that generates XML always put it. This tag can be used to specify Windows event log name to filter by specific log (useful for Windows event synchronization).
Macros section moving to the bottom is a bug - we will fix it.
Best regards,
Victor