1. - available in 1.8.3
2. probably checkboxes for ok/problem/unknown (currently only unknown can be hidden);
3. ideally, severity checkboxes (helpful also for zabbix configuration reviewing)
4. look for ack/nonack events
5. filter for events with ok/nonok actions

Right now, you may only filter for a specific trigger on a specific host. It does not allow to filter on a trigger from a template. Filtering on trigger description might also be great, if not better.

Hi, I'm Takanori Suzuki working at Miracle Linux.
We made an attached patch to add event filter for Zabbix 2.0.3.
It adds "trigger status", "acknowledges status" and "severity level" filters.

• About implementation
  We extended "Event" API function, but it just adds additional option, so usually it doesn't affect to existing API using code.
  Though extending API function might be problem to be accepted.

Sorry, the previous post patch has problem in CSV output processing.
In CSV output processing, "$config['event_ack_enable']" doesn't exist and it failed to output.
I fixed my patch to make $config before using.

Thank you Takanori, your patch works fine for me.

zabbix-2.0.4-filter_events_by_trigger_description.patch allows to filter by trigger description, much like on the tr_status page.

Filtering with the two patches combined

Tested on centos epel 205 distrib.
First patch works fine.
Second works with some manual corrections if the first one installed.

Errors:

--- events.php  2012-12-08 12:09:20.000000000 +0100
+++ events.php  2013-02-11 16:23:43.119990951 +0100
@@ -116,6 +117,7 @@
 if (isset($_REQUEST['filter_rst'])) {
        $_REQUEST['triggerid'] = 0;
        $_REQUEST['showUnknown'] = 0;
+       $_REQUEST['txt_select'] = '';
 }

 $source = get_request('triggerid') > 0 ? EVENT_SOURCE_TRIGGERS
@@ -123,6 +125,7 @@

 $_REQUEST['triggerid'] = get_request('triggerid', CProfile::get('web.events.filter.triggerid', 0));
 $_REQUEST['showUnknown'] = get_request('showUnknown', CProfile::get('web.events.filter.showUnknown', 0));
+$_REQUEST['txt_select'] = get_request('txt_select', CProfile::get('web.events.filter.txt_select', ''));

 // Change triggerId filter if change hostId
 if (($_REQUEST['triggerid'] > 0) && isset($_REQUEST['hostid'])) {
@@ -224,6 +227,7 @@
 if (isset($_REQUEST['filter_set']) || isset($_REQUEST['filter_rst'])) {
        CProfile::update('web.events.filter.triggerid', $_REQUEST['triggerid'], PROFILE_TYPE_ID);
        CProfile::update('web.events.filter.showUnknown', $_REQUEST['showUnknown'], PROFILE_TYPE_INT);
+       CProfile::update('web.events.filter.txt_select', $_REQUEST['txt_select'], PROFILE_TYPE_STR);
 }
 // --------------

There seems to be a flaw with the Duration column. The calculated durations are wrong if filtered by trigger status.

Cumulative patch including duration fix uploaded

Cumulative patch for 2.2.0; please don't let me port it to 2.4 as well!

Hi,

I would like to see that feature: Filter events by severity.

Michael.

Please add this to the next 2.2 or 2.4

Filtering events by severity is very usefull, in particular if triggers with a 'not classified' severity are used to change colors of links on a map the event list gets cluttered.

Adapted patch to fit 2.2.5

Paging doesn't work with the patches

zabbix-2.2.5-ZBXNEXT-410-2.patch hat the paging problem solved, but I discovered ZBX-9003.

Ported to 2.4.2. This port includes the paging bug fix that Volker fixed.

Nice features! Today you cannot get an overview of only high events/triggers in an specific periode. It is difficult to report impact back to management, when bigger problems occurs.

The ability to filter on status, gives a much better overview on events = only one line per event.
/Erik

after applying the 2.4.2 patch, it's sort of working, but throws this error at the end of the page:

Undefined index: searchWildcardsEnabled [events.php:740 → CFrontendApiWrapper->get() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CFrontendApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → call_user_func_array() → CEvent->get() → zbx_db_search() in /var/www/html/include/db.inc.php:777]

Ported to 2.4.7

I think this can be closed as "Fixed in 3.2"!

Already implemented under ZBXNEXT-3201.

I'm glad it was finally implemented in ZBXNEXT-3201 but my issue predates the other one by 6 years so closing this as "duplicates" seems at least... odd