Hello,
I have a vfs.fs trigger that looks like this:
{foo_Template_Windows:vfs.fs.size[c:,free].last(0)}<7415529472
I have a host that is generating an event for this trigger. That looks good and is working as expected. However, the action is acting funny. I am getting two notifications, one that says the {STATUS} is OK, and the other says the {STATUS} is PROBLEM. Not sure how this can be. This tells me that it is flapping but it isn't because I don't have recovery message checked. I dropped the period on the action to 60 seconds so I can troubleshoot and every 60 seconds I got two messages.
The action has escalations enabled and 1 step that sends me an email with the following parameters:
From: 1
To: 0
Period: 0
Default Message: checked.
I have a feeling that the problem lies in the escalation steps but not sure how. I would expect that this type of escalation will notify every 60 seconds forever until the status changes.
What am I missing?
I have a vfs.fs trigger that looks like this:
{foo_Template_Windows:vfs.fs.size[c:,free].last(0)}<7415529472
I have a host that is generating an event for this trigger. That looks good and is working as expected. However, the action is acting funny. I am getting two notifications, one that says the {STATUS} is OK, and the other says the {STATUS} is PROBLEM. Not sure how this can be. This tells me that it is flapping but it isn't because I don't have recovery message checked. I dropped the period on the action to 60 seconds so I can troubleshoot and every 60 seconds I got two messages.
The action has escalations enabled and 1 step that sends me an email with the following parameters:
From: 1
To: 0
Period: 0
Default Message: checked.
I have a feeling that the problem lies in the escalation steps but not sure how. I would expect that this type of escalation will notify every 60 seconds forever until the status changes.
What am I missing?

Comment