Hey Adam,
“I think something like this might work: LOG %/path/to/log/Log.File_ABC.*.log ERROR COLOR=red“
Having modified the line as mentioned by you in the above example did the trick. Thank you folks!
Regards Christian
Christian Becker IT-Services
Christian.Becker at rhein-zeitung.net<mailto:Christian.Becker at rhein-zeitung.net>
Mittelrhein-Verlag GmbH August-Horch-Straße 28 D-56070 Koblenz Verleger und Geschäftsführer: Walterpeter Twer Reg.-Gericht Koblenz HRB 121 Finanzamt Koblenz Str.Nr. 22 65 10 285 2 www.rhein-zeitung.de<http://www.rhein-zeitung.de/>
Von: Xymon [mailto:xymon-bounces at xymon.com] Im Auftrag von Adam Goryachev Gesendet: Dienstag, 14. Juni 2016 15:09 An: xymon at xymon.com Betreff: Re: [Xymon] Monitoring logfiles with changing names on a linux client
On 14/06/16 23:04, Becker Christian wrote: Hey Jeremy,
brilliant!
I decided to go with a mix of option 1 and option2.
This is what I’ve put in client-local.cfg:
log:ls /path/to/log/Log.File_ABC*.log| grep $(date +%Y%m%d):10240
Now i’m getting 6 logfiles in the msgs column -> great!
This is what I’ve put in analysis.cfg for the specific linux client: LOG %/path/to/log/Log.File_ABC*.log ERROR COLOR=red
However, this does NOT let the msgs column go red, although the files do contain the keyword ERROR, exactly matching the case. And I can see those keywords on the msgs page as well. What is going wrong here now? I think something like this might work: LOG %/path/to/log/Log.File_ABC.*.log ERROR COLOR=red
C* means zero or more of the letter C, while .* means 0 or more of any character....
Also, it isn't "anchored" at the beginning/end, so you shouldn't need to add a .* to the beginning/end....
Hope that helps.
Regards, Adam
Adam Goryachev Website Managers www.websitemanagers.com.au<http://www.websitemanagers.com.au>