-
Problem report
-
Resolution: Won't fix
-
Trivial
-
None
-
5.0.28
-
None
-
VM, OS Centos 8, php7.4, mysql 8.0, zabbix-server 5.0.28
Hello!
Steps to reproduce:
- Create an item analysis of the log for the presence of the text "error" (
{host:log[file.log,,,50,skip]). Update interval every 1 hour, but new text is rarely written to the log, 1 time in 3 months (if the program is successfully executed) , and if the error is in the log, then re-recording after 1 day.
# Create trigger, problem expression: \{host:log[file.log,,,50,skip].str(error)}
=1
- Recovery expression to close the issue if there are no errors in the last 22 hours: {host:log[file.log,,,50,skip].nodata(22h)}=1 or {host:log[file.log,,, 50,skip].str(error,22h)}=0
Result:
But for some reason, the restore trigger does not close after 22 hours or more, when nothing new is written in the log.
Expected:
Issue will close after 22 hours when there is no new log item data.
What could be the reason? The nodata function has a time limit?