What I ultimately want is for a particular group of users to get an email when a particular partition (which is constantly filling with data) gets below a certain threshold, then get ANOTHER alert if the condition remains true for a certain period of time.
I know that repeating alerts do not exist in this version of Zabbix.
I tried to get around the problem by making two triggers. The first trigger has this for it's expression:
{Template_Data_On_D:vfs.fs.size[d:,free].last(0)}<3221225472
It works exactly as expected. It becomes true with <3GB of free space, and I have an action configured to send the email. In case it matters, since the data partition is different on different machines, I've got the action configured using "Trigger Description Like", and it looks for "data partition low", and of course value=true.
I have another expression which (for testing purposes) I have attempted to configure to go off only when it's been true for an hour. My understanding is that this is the purpose of the last number in (). Therefore, I have this:
{Template_Data_On_D:vfs.fs.size[d:,free].last(3600)}<3221225472
That trigger has a separate action linked to it, again using "Trigger Description Like", and this time it looks for "data partition low", AND "second warning", AND value=true.
I've been experimenting by pulling a file off and on the target machine which is just big enough to make me cross the threshold, causing the triggers to be true.
What happens is that both triggers become true at the same moment, and both actions fire off their emails. Even more confusing, I get TWO of the "second warning" emails, and one of the initial emails (total of 3) where it seems like I should be getting one email from each of the two actions. (total of 2).
In case it helps, I'm attaching a screenshot of my trigger and action configurations.
I know that repeating alerts do not exist in this version of Zabbix.
I tried to get around the problem by making two triggers. The first trigger has this for it's expression:
{Template_Data_On_D:vfs.fs.size[d:,free].last(0)}<3221225472
It works exactly as expected. It becomes true with <3GB of free space, and I have an action configured to send the email. In case it matters, since the data partition is different on different machines, I've got the action configured using "Trigger Description Like", and it looks for "data partition low", and of course value=true.
I have another expression which (for testing purposes) I have attempted to configure to go off only when it's been true for an hour. My understanding is that this is the purpose of the last number in (). Therefore, I have this:
{Template_Data_On_D:vfs.fs.size[d:,free].last(3600)}<3221225472
That trigger has a separate action linked to it, again using "Trigger Description Like", and this time it looks for "data partition low", AND "second warning", AND value=true.
I've been experimenting by pulling a file off and on the target machine which is just big enough to make me cross the threshold, causing the triggers to be true.
What happens is that both triggers become true at the same moment, and both actions fire off their emails. Even more confusing, I get TWO of the "second warning" emails, and one of the initial emails (total of 3) where it seems like I should be getting one email from each of the two actions. (total of 2).
In case it helps, I'm attaching a screenshot of my trigger and action configurations.
Comment