[ZBXNEXT-1737] Trigger with one status only Created: 2013 May 07  Updated: 2018 May 16

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

Type: New Feature Request Priority: Trivial
Reporter: Cristian Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: triggerstatus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Sub-task
part of ZBXNEXT-4555 Support custom representations for st... Open

 Description   

I think would be useful to have the option for triggers to have a custom number of statuses (to allow even 1 status only, not OK/PROBLEM).

A sample of this is when is needed to monitor restart of a service. I don't think the dual OK/PROBLEM is appropriate. Rather is normal to have only one status (as PROBLEM or INFO only). Of course, the notifications/actions can be customized to only send notifications per initial PROBLEM. But still, in the system are registered 2 events, bot the PROBLEM and the OK....



 Comments   
Comment by Cristian [ 2013 May 07 ]

Other sample: version changed, is same one status only...

Comment by richlv [ 2013 May 07 ]

very similar to ZBXNEXT-415

Comment by Volker Fröhlich [ 2013 May 11 ]

Much like ZBXNEXT-582

Comment by Cristian [ 2013 May 11 ]

Not quite. ZBNEXT-582 is quite fixed with adding option to not send a recovery message.

My proposal was to have diff events than PROBLEM/OK.

Comment by Marc [ 2013 Nov 13 ]

I'm not absolutely sure if this is the right place.
Anyhow, I would prefer to keep the current implementation as it is (just to avoid deep cuts).

But I would like to see an option to allow a different representation for status OK and PROBLEM (in frontend, messages, etc.) on trigger level.
In fact these status represent (expression) TRUE or FALSE. In most cases a trigger expression indeed represents a PROBLEM, thus it's not generally wrong.

Having an option to either choose between proper status representation sets or to configure custom representations would be a great improvement.

 

 Edit: Stripped of into ZBXNEXT-4555

Generated at Fri Mar 29 04:12:43 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.