Hi all,
I'm using a log item on Zabbix 3.2:
logrt[D:\log\myapp\^my_app*.log*,ThisWordMayNotAppear,,, skip,\0,]
to scan log files for some keywords.
The logfiles are written with a Java application using Log4j2 (Asynchronous logging) on a Windows Server 2012 machine.
A few times a day I see the messages:
2644:20161026:080435.068 the modification time of log file "D:\log\my_app\my_app.log" has been updated without changing its size, try checking again later
2644:20161026:080505.388 after changing modification time the size of log file "D:\log\my_app\my_app.log" still has not been updated, consider it to be a new file
Because of this the log file is re-scanned and triggers are activated unnecessary. I can understand the message that the mtime of the file is updated without changing the contents but is there a way to avoid this or is this a known problem using Zabbix with Log4j2?
Thanks for any help!
I'm using a log item on Zabbix 3.2:
logrt[D:\log\myapp\^my_app*.log*,ThisWordMayNotAppear,,, skip,\0,]
to scan log files for some keywords.
The logfiles are written with a Java application using Log4j2 (Asynchronous logging) on a Windows Server 2012 machine.
A few times a day I see the messages:
2644:20161026:080435.068 the modification time of log file "D:\log\my_app\my_app.log" has been updated without changing its size, try checking again later
2644:20161026:080505.388 after changing modification time the size of log file "D:\log\my_app\my_app.log" still has not been updated, consider it to be a new file
Because of this the log file is re-scanned and triggers are activated unnecessary. I can understand the message that the mtime of the file is updated without changing the contents but is there a way to avoid this or is this a known problem using Zabbix with Log4j2?
Thanks for any help!
Comment