Hello all. I'm testing out some log file monitoring tools on a Windows Server 2008 machine using a Zabbix 2.2.4 server and Zabbix 2.2.5 agent.
I have a log file on my system at C:/awesome_log.log, containing a bunch of lines. I have a Zabbix Agent/Server pair correctly configured already monitoring various routine things from the Windows OS template. I add an item to Zabbix with the key log["C:/awesome_log.log"]. The item shows on the UI as enabled, and the contents of the log file are recorded in the item's history.
After a few minutes, however, the item becomes unsupported and its history vanishes from the UI - the "Latest Data" page still lists the last line in the file, but when looking at the item's history no information appears. The zabbix_agentd.log file reports cannot stat 'C:/awesome_log.log': [2] No such file or directory, even though the file is definitely still there. The UI also shows a big red X with the error ZBX_NOTSUPPORTED in the item config page.
If I then edit awesome_log and add a few more lines to it, after a few minutes the item becomes enabled again, and the new lines re-appear in the item's history correctly. Despite the ZBX_NOTSUPPORTED everything seems fine.
Running a similar experiment on a Linux machine does not cause this issue - the log file item remains error-free.
It seems as though, when running on Windows Server 2008, if a log file item has nothing new to report for some amount of time, the agent assumes that the file no longer exists. This behavior seems bizarre, and I'm wondering if anyone can help shed some light on why this might be happening.
I have a log file on my system at C:/awesome_log.log, containing a bunch of lines. I have a Zabbix Agent/Server pair correctly configured already monitoring various routine things from the Windows OS template. I add an item to Zabbix with the key log["C:/awesome_log.log"]. The item shows on the UI as enabled, and the contents of the log file are recorded in the item's history.
After a few minutes, however, the item becomes unsupported and its history vanishes from the UI - the "Latest Data" page still lists the last line in the file, but when looking at the item's history no information appears. The zabbix_agentd.log file reports cannot stat 'C:/awesome_log.log': [2] No such file or directory, even though the file is definitely still there. The UI also shows a big red X with the error ZBX_NOTSUPPORTED in the item config page.
If I then edit awesome_log and add a few more lines to it, after a few minutes the item becomes enabled again, and the new lines re-appear in the item's history correctly. Despite the ZBX_NOTSUPPORTED everything seems fine.
Running a similar experiment on a Linux machine does not cause this issue - the log file item remains error-free.
It seems as though, when running on Windows Server 2008, if a log file item has nothing new to report for some amount of time, the agent assumes that the file no longer exists. This behavior seems bizarre, and I'm wondering if anyone can help shed some light on why this might be happening.