[ZBX-19037] An issue with "Problem is not suppressed" action condition after the maintenance period ends Created: 2021 Feb 18  Updated: 2024 Apr 02  Resolved: 2023 Dec 22

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 5.0.8
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Oleg Ivanivskyi Assignee: Oleksii Zagorskyi
Resolution: Incomplete Votes: 0
Labels: conditions, maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 5.0.2

Issue Links:
Duplicate

 Description   

"Problem is not suppressed" action condition in the actions may lead to missing notifications from Zabbix. Another affected user: https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/370741-problem-with-actions-after-maintenance-period-ends-zabbix-4-0-1

 

Steps to reproduce:

  1. Configure Zabbix action with "Problem is not suppressed" condition for a host (use other default values, i.e. "Pause operations for suppressed problems" is enabled also)
  2. Use "1 - 0" step to execute an operation continuously (e.g. execute a command every N minutes) 
  3. Configure maintenance for 5 minutes for the host
  4. Wait until maintenance is started for the host
  5. Generete a test problem
  6. Wait for 5 minutes until maintenance is ended for the host
  7. Wait for some time

Result:
No operations/actions will be executed for the active problem after the maintenance

Expected:
Operation/escalation should be executed after the maintenance because problem is still active and not suppressed any more.

 Comments   
Comment by Kevin Daudt [ 2021 Feb 18 ]

This is already the case since the "Pause operations for suppressed problems" option was introduced. Since then, the "Problem is not suppressed" condition actually is used as a filter, meaning that when the problem occurs, and the problem is suppressed, the action is never started for that problem (just like any other condition would).

So if you just want to prevent alerts to be sent while the host is in maintenance, but be sent out when the maintenance ends, just remove that condition make sure the "Pause operations for suppressed problems" option is enabled.

Comment by Oleg Ivanivskyi [ 2021 Feb 18 ]

1. Yes, I know about that "workaround". Just imagine a situation: you have an old Zabbix version. You use maintenance periods and have actions with "Problem is not suppressed" condition to suppress action execution while host has maintenance enabled. You upgraded Zabbix to 5.x. Result: actions stopped worked as expected.

Since then, the "Problem is not suppressed" condition actually is used as a filter, meaning that when the problem occurs, and the problem is suppressed, the action is never started for that problem (just like any other condition would).

2. Maybe it is an option for one time operation (e.g. 1-1 step). I am talking about a different issue: Maintenance ended and problem is not suppressed any more > I have "1 - 0" step to execute an operation continuously > I would expect that Zabbix will run the operation

It is even more interesting because Zabbix has no maintenance history:
host was in maintenance > critical problem was generated > maintenance ended > problem is active for a month/year > no one will be notified

  • it would be great to have a warning related to #1 in the upgrade procedure
  • #2 is a bug
Comment by Oleksii Zagorskyi [ 2023 Dec 22 ]

Having "Problem is not suppressed" condition obviously does not start escalations at all when a problem gets created. So after maintenance period ends, there is nothing to send alerts, as there no escalations.

After 2 years this topic probably became less actual as before, as most of installations already on 6.0+ and some upgrade nuances have been resolved already.
So, I'm closing this.

Generated at Mon Oct 27 22:28:44 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.