We have a template that monitors folders and if there are files in the Error folder, an alarm is generated. When a file is deleted from the Error folder, the alarm is automatically closed. The same template is used in all our hosts. Now in one host, an alarm is generated from one Error folder, but it does not close even though the file has been deleted from that Error folder. All other alarms from other Error folders close normally. I removed the host from Zabbix and added it again. When the alarm from that same Error folder came again, the same thing, it just never closes. What on earth can I do with this? It´s driving me grazy!
Ad Widget
Collapse
Alarm won´t be closed
Collapse
This topic has been answered.
X
X
-
Alarm won´t be closed
We have a template that monitors folders and if there are files in the Error folder, an alarm is generated. When a file is deleted from the Error folder, the alarm is automatically closed. The same template is used in all our hosts. Now in one host, an alarm is generated from one Error folder, but it does not close even though the file has been deleted from that Error folder. All other alarms from other Error folders close normally. I removed the host from Zabbix and added it again. When the alarm from that same Error folder came again, the same thing, it just never closes. What on earth can I do with this? It´s driving me grazy!
Tags: None -
Answer selected by SQ_AM at 06-08-2025, 09:30.
-
What configuration you mean? The template config?
Item
Trigger has an expression
last(/Solteq template File Check/FileCount[{#ERRORPATH}])>0
On the app server we have a scheduled task which runs this script every day, this creates list of folders we want to monitor
The agent has user parameters
UserParameter=FileCount[*],cscript C:\Zabbix2\scripts\FileCount.vbs //nologo "$1"
UserParameter=Folder.Discovery,powershell -NoProfile -ExecutionPolicy Bypass -File "C:\Zabbix2\scripts\ReadFileList.ps1"
This template has been working fine and it works in this host with all other folders but when file comes to \\SAF\\El\\Error path, the alarm won´t close even there is no files in that path. In any other path it works fine.
Comment
-
If you say that the problem does not clear, it means that the item either still receives a positive integer, or there is no new value at all. See the latest values data and the timestamps for the item to see what is happening. Zabbix server/proxy/agent log is also useful if there is something unexpected happening with the item.Trigger has an expression
last(/Solteq template File Check/FileCount[{#ERRORPATH}])>0
Markku
Comment
Comment