[ZBXNEXT-2065] Option to see triggers in PROBLEM status only Created: 2013 Dec 09  Updated: 2014 Aug 22  Due: 2014 Apr 17  Resolved: 2014 Apr 22

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 2.0.9
Fix Version/s: 2.3.0

Type: Change Request Priority: Trivial
Reporter: Marc Assignee: Unassigned
Resolution: Fixed Votes: 3
Labels: filter, patch, trigger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File zbxNext2065-2.2.5.patch    

 Description   

Would be nice to have an option in 'Status of triggers' that filters for triggers in PROBLEM status only, regardless of 'Display OK triggers for' configuration.



 Comments   
Comment by richlv [ 2013 Dec 09 ]

"administration -> general -> trigger displaying options" allows to set 'ok' period to 0 - does that solve this ?

Comment by Marc [ 2013 Dec 10 ]

nope ([...] regardless of 'Display OK triggers for' configuration)

Comment by richlv [ 2013 Dec 10 ]

duh
what's the usecase that is not satisfied ?

Comment by Marc [ 2013 Dec 10 ]

The current behavior is very valuable.
It allows to notice triggers that just switched into OK status or switched into PROBLEM status and back to OK between a browser refresh.
So I don't want to swap it.

Anyhow, it happens regularly that there are too many triggers in OK status displayed and it's hard to overlook the ones in PROBLEM state.
Currently the only way to see only triggers in PROBLEM status is the "Last 20 issues" dashboard widget - admittedly, together with ZBXNEXT-1029 kind of work-around.

Maybe rather an issue in using Zabbix for enterprise environments

Comment by Filipe Paternot [ 2014 Feb 25 ]

I see his point.. it is a good feature request, indeed.

This would be helpful specially in cases of disaster recovery and with big zabbix setup. You may have a lot of triggers changing from PROBLEM to OK, and the ones that still in problem state could be mixed with many others that are already with OK.

This would also help with the absence of a way to make triggers smart enough about proxy downtime (see https://support.zabbix.com/browse/ZBXNEXT-46).

Comment by richlv [ 2014 Mar 11 ]

so to clarify, this is suggesting to move the option from global setting to a user-configurable setting in page filters - is that correct ?

Comment by Marc [ 2014 Mar 12 ]

Not exactly.
This issue is about a new (stricter) option than 'Problem' for selection in 'Triggers status'.
For instance:

  • Any
  • Problem
  • Problem (strict) *NEW OPTION*
  • Any
  • Problem/OK
  • Problem *NEW OPTION*
Comment by Filipe Paternot [ 2014 Mar 12 ]

Agree

Comment by Oleg Egorov (Inactive) [ 2014 Apr 10 ]

FIXED IN svn://svn.zabbix.com/branches/dev/ZBXNEXT-2065 r44277
But, as was discussed, fix temporary frozen

Comment by Marc [ 2014 Apr 11 ]

Fix in r44277 is working perfectly fine.
Thanks a lot!

Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 11 ]

(1) I suggest to change the label from "Problem/OK" to "Recent problem".

oleg.egorov RESOLVED IN r44323

Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 11 ]

(2)

if ($showTriggers == TRIGGERS_OPTION_PROBLEM_AND_OK) {
	$options['only_true'] = 1;
}
if ($showTriggers == TRIGGERS_OPTION_ONLY_PROBLEM) {
	$options['filter'] = array('value' => TRIGGER_VALUE_TRUE);
}

Sinces the two ifs are mutually exclusive, they should be written using an if-elseif clause.

oleg.egorov RESOLVED IN r44323

jelisejev CLOSED.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 11 ]

(3) The filter should remember the "problem" and "recent problem" values.

oleg.egorov RESOLVED IN r44323

jelisejev CLOSED.

Comment by Oleg Egorov (Inactive) [ 2014 Apr 11 ]

(4) Added string:
Recent problem

In Monitoring->Triggers New Triggers status filter option

jelisejev CLOSED.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 14 ]

TESTED.

I've made a couple of formatting changes in r44394.

Comment by Oleg Egorov (Inactive) [ 2014 Apr 15 ]

RESOLVED IN 2.3.0(trunk) r44413

Comment by richlv [ 2014 Apr 22 ]

(6) regression. trigger filter status option now remembers "any"

<richlv> as discussed, this was caused by some previous bug, where value for 'any' was wrtten into the db. latest versions should not do that. this problem only appeared for a while in trunk, so it should not affect "normal" users

CLOSED

Comment by Marc [ 2014 Aug 22 ]

Attached patch zbxNext2065-2.2.5.patch ports this very useful functionality back to 2.2

Generated at Fri Mar 29 17:58:57 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.