[ZBXNEXT-755] add support for more operation conditions Created: 2011 Apr 14  Updated: 2015 Apr 16

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: 1.8.4
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Aleksandrs Saveljevs Assignee: Unassigned
Resolution: Unresolved Votes: 4
Labels: conditions, operations, patch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File ZBXNEXT-755.patch    

 Description   

It would be nice to have most of the action conditions in operation conditions as well.

For instance, if no one is going to do anything about a particular problem (say, the number of failed tests in Hudson) during weekend, it would be nice to be able to specify "Time period" condition of "1-5,09:00-19:30" for an operation that sends emails to developers to decrease the number of unnecessary emails. Setting "Time period" condition with "1-5,09:00-19:30" in action conditions may prevent the action from starting escalations at all. Setting "Time period" in media configuration prevents users from receiving all emails during weekends.

Another example is when we have an action that alerts about problems occurring on a particular host. Problems can be of two types: a software problem and a hardware problem. If "Application" is "Software", we wish to send an email to software staff. If "Application" is "Hardware", we wish to send an email to hardware staff. If "Application" is "Sordware", we wish to send an email to both groups. Currently, this is possible with three actions, but would be nice if we could do the same with one action, but three operations.



 Comments   
Comment by richlv [ 2011 Apr 14 ]

If "Application" is "Sordware" ?

"Sodware" might be a bit more practical, maybe...

Comment by richlv [ 2011 Apr 14 ]

also see ZBXNEXT-128

Comment by Michael Dai [ 2015 Apr 10 ]

How can I develop for this issue?

Comment by Michael Dai [ 2015 Apr 16 ]

Patch for ZBXNEXT-755

Generated at Fri Apr 04 16:02:12 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.