[ZBXNEXT-892] Triggers should be filterable by Unknown status Created: 2011 Aug 17 Updated: 2016 Mar 23 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F) |
Affects Version/s: | 1.8.6 |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Major |
Reporter: | Robert Hau | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 1 |
Labels: | filters, triggers | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | zabbix-2.2.0-ZBXNEXT-892-Filter-for-unknown-state-in-Monitoring-Triggers.patch | ||||||||
Issue Links: |
|
Description |
It currently is impossible to sort for unknown triggers We have a few branches with network disconnects often and items go unknown. An ops guy goes to click on the map and they see 45 pages of triggers. that are ok or problem. In order to find the unknown you must go through most of the pages to find it. We need to have a filter for Unknown/Problem/Any. I found a short term workaround in the tr_status.php. $table->setHeader(array( Now at least i can sort on the status column and get the unknown on either the first page or last. |
Comments |
Comment by Alexey Fukalov [ 2012 Jul 25 ] |
For 2.0.x Monitoring->Triggers planned changes: |
Comment by Volker Fröhlich [ 2013 Dec 09 ] |
This patch replaces the string "Triggers status" with "Trigger status". The value of the respective form variable is stored in the profile. The API request is appended a filter element for state = 1. |
Comment by Volker Fröhlich [ 2016 Mar 23 ] |
What's the status here? |