I went through the git repository and it seems that the "rotated" options is really only in place for the deprecated windows logfile, and that part doesn't apparently work with agent 1.6 anymore. Not good.
So if windows process outputs like logfile2020-12-15.log, logfile2020-12-16.log, the globbing rule with "rotated" flag is currently a feature that has gone away...
From: checkmk-en <firstname.lastname@example.org> On Behalf Of Antti Mäkelä
Sent: tiistai 17. joulukuuta 2019 11.26
To: 'email@example.com' <firstname.lastname@example.org>
Subject: Re: [Check_mk (english)] Text logfiles and spaces in glob patterns
...a workaround for this apparently was to use short names in patterns. You know,
c:\progra~1 and so on.
However, we have another problem, because the service in question is using log rotation. In the deprecated setting, we can just specify
"Rotated log" option:
If this is ticked, files matching the pattern are treated as one service and the agent will read them from oldest to newest. It should also correctly handle file renames.
However, there is no such thing in the new logfile parser configuration. How can this functionality be achieved. Right now we get a dozen services due to every archived log file appearing in the list...
From: Antti Mäkelä
Sent: tiistai 17. joulukuuta 2019 10.52
Subject: Text logfiles and spaces in glob patterns
We have a problem in defining text logfile check for an agent.
We get error "File patterns must not contain spaces" when attempting to define configuration.
Ok, great. How I'm supposed to define files like "C:\Program Files (x86)\...." if spaces are not permitted?
The "deprecated" text file rules does not seem to generate the rules in YAML format anymore. ( As it says, 1. The section 'logfiles' is not supported anymore by New Agent. Please, use corresponding check_mk plugin).
checkmk-en mailing list
Manage your subscription or unsubscribe
The mailing list will be shut down by 31.12.2019. Sign up at the Checkmk Community forum: https://forum.checkmk.com.