How to accommodate different parser patterns for duplicate filenames / patterns


How to accommodate different parser patterns for duplicate filenames /...
Author
Message
scottyjay
scottyjay
New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)New Member (27 reputation)
Group: Forum Members
Posts: 3, Visits: 18
Apologies if this has been asked previously, my search doesn't yield results for this,

I have multiple applications that log to application.log or some derivation.  By necessity they have different variables in their output format (not vastly different, but different). 

As there is no difference in the filename (the path does differ) the parser mapping must be selected everytime. 
Well being able to select the parser would be a boon, instead I'm prompted with a new default parsing wizard dialog when I open the subsequent differing application.log file.  I've played around with ordering, but this doesn't seem to yield a result.

I.e. two different applications log to
/var/logs/application_logs/[application-name]/application-2024-05-29.log
My parser mappings can only be application-*.log, but if I open one application's logs after setting up for another that differs in format, LogViewPlus fails to use the "best" previously configured parser.

A workaround is probably to open a file WITH a specific filter, but that means hard-coding I believe, and a level of verbosity I don't care for.

Am I missing something?

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Login

Explore
Messages
Mentions
Search