<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:10px;"><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:10px;"><div></div>
<div>I realised the solution came about via direct emails with Andy so here is the solution for posterity:</div><div><br></div><div><span><div>Now the LOG config in analysis.cfg is simply :</div><div>LOG %/var/log/messages.*.log "XXXX" COLOR=yellow</div><div><br></div><div>And the accompanying client-local.cfg entry is :</div><div>[linux]</div><div>log:/var/log/messages:10240</div><div>log:`find /var/log -maxdepth 1 -type f -name messages-\*.log`:10240000000</div></span><br></div><div>The requirement was the regex wildcar .* not the glob of just *. <br><br>Next question...<br><br>I now see if I place the trigger word DIDDS in an appropriate logfile xymon does spot it and alert on it, and the GUI page shows the contents of the logfile as <br><CURRENT><br>DIDDS<br><br>But after 10 minutes... it drops the alert and the gui page no longer also lists those contents - in fact it shows nothing as the contents.<br><br>Anybody any ideas as to why this behaviour is seen. These tests are at the moment using dummy logfilesd which have no other info in them. It is literally only the line "DIDDS" which remains there.<br><br>If I add another line DIDDS once again it spots it and then alerts and shows it as <br><CURRENT><br>DIDDS.<br><br>For ten minutes - then it all drops again...<br><br>any ideas why this is occurring? <br></div><div><br></div><div>didds</div></div></div></body></html>