[ZBXNEXT-721] ability to silence a single trigger for a defined timeperiod (maintenance for a single trigger, or non-permanent acknowledgement) Created: 2011 Mar 30 Updated: 2024 Apr 10 Resolved: 2022 Jul 05 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | None |
Affects Version/s: | 1.8.4 |
Fix Version/s: | 6.2.0rc1, 6.2 (plan) |
Type: | New Feature Request | Priority: | Major |
Reporter: | Will Lowe | Assignee: | Miks Kronkalns |
Resolution: | Fixed | Votes: | 42 |
Labels: | acknowledges | ||
Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
Attachments: |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
||||||||||||||||||||||||
Issue Links: |
|
||||||||||||||||||||||||
Sub-Tasks: |
|
||||||||||||||||||||||||
Team: | |||||||||||||||||||||||||
Sprint: | Sprint 89 (Jun 2022), Sprint 90 (Jul 2022) | ||||||||||||||||||||||||
Story Points: | 10 |
Description |
We need a way to support the following workflow:
As I understand it the two possibilities today are: ACKNOWLEDGE the alert and configure the Action to ignore events which have been acknowledged. But there's no time limit – once acknowledged, an Action is silent forever. If alerts could have a time limit ("ACKNOWLEDGE for 24 hours") that would solve this use case. Schedule the entire host for maintenance. But then if the problem gets worse or another trigger fires, we won't find out. So if we could schedule a trigger on an individual host for maintenance, this would solve the use case. |
Comments |
Comment by Will Lowe [ 2011 Mar 30 ] |
Here's a thread on the forum about the same idea: http://www.zabbix.com/forum/showthread.php?p=82232#post82232 |
Comment by Elvar [ 2012 Dec 28 ] |
Yes, I have wanted something like this for a long time. The best example I can think of that does very close to this is the pause sensor in PRTG. (http://www.paessler.com/manuals/prtg8/pause). This simple addition to Zabbix would vastly improve the usability for me. If it could also allow data collection to still occur during the pause but simply supress alerts that would be perfect in my opinion. |
Comment by Tim Mooney [ 2013 Feb 15 ] |
I found this issue via the duplicate https://support.zabbix.com/browse/ZBXNEXT-769 Being able to temporarily acknowledge alerts but have the acknowledgement expire after a period of time and start re-alerting is something we want too. It's a feature that's always been part of the commercial monitoring package that we're abandoning, and it's probably the thing we miss the most. I understand that this poses some tricky issues with regard to escalations, but this feature is actually a lot more important to us than escalations. I'm going to start looking at the DB schema to see if there's a way I can expire acknowledgements by accessing the database directly. I'm not excited about that, but it's that important to us. |
Comment by Will Lowe [ 2013 Feb 16 ] |
In the short term we have implemented www.pagerduty.com as a workaround. It would be terrific if Zabbix could support similar workflows for alerting and escalation. |
Comment by Marc [ 2013 Mar 24 ] |
I would appreciate something similar to [..]time limit ("ACKNOWLEDGE for 24 hours") as additional option in operational condition of action operations. |
Comment by Rodrigo Pereira [ 2017 May 13 ] |
Hi. Is there any update on this issue? In order to cover extremely useful functionality found in another software, it would be required to do the following at host+trigger level:
This issue old and I've tried to find in documentation about related functionality, but couldn't find it. Appreciate any info, thanks!! |
Comment by Rodrigo Pereira [ 2017 Oct 25 ] |
Is this planned for version 4? |
Comment by Rodrigo Pereira [ 2017 Oct 25 ] |
where can I see what is planned for v4? |
Comment by richlv [ 2019 Apr 04 ] |
Tag based maintenance might have partially resolved this. |
Comment by Laz Ravelo [ 2019 Apr 04 ] |
I too would love to have this feature. It's the only thing keeping my organization from adopting Zabbix as the monitoring tool of choice. |
Comment by Laz Ravelo [ 2019 Apr 05 ] |
@richlv Can you give me an example as to how this could work? I'm doing a pic for different monitoring applications and this particular feature is the deal breaker on whether or not we get to choose Zabbix. |
Comment by Erhan ERTUL [ 2019 Sep 12 ] |
The solution exists. Just check Example 9 here > https://www.zabbix.com/documentation/4.2/manual/config/triggers/expression |
Comment by Alexei Vladishev [ 2022 Apr 08 ] |
Just a quick update. We are aiming to include this functionality in Zabbix 6.2, stay tuned. |
Comment by Mickael Martin [ 2022 Apr 11 ] |
hello @alexei . Great new ! We work with tag like it but there is some limitations :
But, we have an icon "maintenance" on all hosts on each "trigger maintenance" ... (cf https://support.zabbix.com/browse/ZBXNEXT-5897?filter=20717 ) |
Comment by Miks Kronkalns [ 2022 Jun 08 ] |
Implemented in:
|
Comment by Miks Kronkalns [ 2022 Jun 17 ] |
Updated API documentation pages: Updated documentation pages: |