By stating to "[...] make a unified view [..]", is it meant to provide this view in addition or to replace the current views Triggers and Events, resp. to implement one view that supports each of these aspects?

While I can confirm that it is indeed confusing to new or non-power-users, it is pretty valuable to have these two aspects on issues. One aspect for the current state and another aspect for identifying what happened at a certain period in time.

A replacement view for Triggers and Events that provides several aspects sounds to be the best approach to me but is possibly also the most challenging one from a UX perspective.

However, if a good implementation design is found, that's to say one view that allows different kind of aspects with flexible but intuitive filter options, then this promises to become a huge improvement to users.

Btw, yet another aspect could be ZBXNEXT-2695.

The new view is supposed to support all functionality we already have under Monitoring->Triggers and Monitoring->Events along with additional filtering options and much better performance.

Available in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201

(1) Changed translation strings:

Strings added:

• RESOLVED
• Recent problems
• Recovery time
• Show unacknowledged only

iivs CLOSED

Available in pre-3.1.0 (trunk) r61049.

(2) Related to ZBXNEXT-2163.

Administration -> Media types: "exec_params_count" can be removed.
Monitoring -> Problems, Monitoring -> Web: "page" input parameter must be validated more strictly

sasha RESOLVED in trunk@61073,61074

iivs CLOSED

(3) Links to event details is missing from problem view

sasha RESOLVED in trunk@61077

iivs CLOSED

(4) Broken "Host" column in Monitoring->Triggers view

sasha RESOLVED in trunk@61081

iivs CLOSED

(5) Bulk acknowledge

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61346.

gunarspujats CLOSED

(6) [D] API documentation updated

• https://www.zabbix.com/documentation/3.2/manual/api/reference/problem
• https://www.zabbix.com/documentation/3.2/manual/api/reference/problem/object
• https://www.zabbix.com/documentation/3.2/manual/api/reference/problem/get
• https://www.zabbix.com/documentation/3.2/manual/api/reference/event/object
• https://www.zabbix.com/documentation/3.2/manual/api/reference/event/get
• https://www.zabbix.com/documentation/3.2/manual/api/changes_3.0_-_3.2

RESOLVED

gunarspujats CLOSED

(8) [F] Acknowledging problems, view switches to last page. So does the cancel.

sasha RESOLVED in trunk@r61145

iivs CLOSED

(9) [F] Problems page shows 8689+ records at the bottom, while other pages show only 1001+. Also API count returns 9849 records. Filter was reset, so shouldn't everything be selected?

sasha Problem view does not show old resolved problems. It depends on "Display OK triggers for" option.

sasha RESOLVED in trunk@r61143

iivs CLOSED

(10) [F] Sorting by severity doesn't change. Looks exactly like sorted by time.

alexei RESOLVED in trunk@r61120
sasha incorrect sorting by problem, host and severity. RESOLVED in trunk@r61141

iivs Looks good now.
CLOSED

(11) [F] As discussed, the extension of Monitoring -> Problems view from ZBXNEXT-3277 task is now moved here and I quote: "The view will be extended to have another column INFO placed after STATUS. The columns will contain an icon if problem was resolved by correlation."

sasha RESOLVED in r62098

Strings added:

• Correlation rule
• Resolved by correlation rule "%1$s".
• Resolved by correlation rule.
• Resolved by user "%1$s".
• Resolved by user.

gunarspujats CLOSED

(12) [A] Specification states that possible sorting columns for problem.get are eventid and clock, however objectid is implemented as well. Also there is no clock index on problem table.

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61320.

gunarspujats CLOSED

(13) [F] Coding style and other minor issues:

• ZBase.php
  • L:371 type must be set to CRouter and parameter is not described.
• monitoring.problem.view:
  • L21: Missing space before the first line of code
• CControllerProblemView.php:
  • L24: unused variable
  • L89-102: commented code
• CProblem.php:
  • L25: We don't write this anymore.
  • L42: PHPdoc for function states that there is an option count? And itemids? Seems like the Problem API options are quite different for that get method.
  • L293: We don't write this anymore.

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61316

gunarspujats CLOSED

(14) [F] sorting by priority in problem view does not work

alexei RESOLVED in revision 61120.

iivs How is this different from (10)?

sasha CLOSED as duplicate of (10)

(15) [F] after first in-line refresh all sorting links in table header become incorrect

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61336.

gunarspujats CLOSED

(16) [F] Performance issue
Monitoring->Problems use a lot of memory. To see 50 problems need at least 512 RAM for PHP

(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/zbxnext_3274/include/classes/api/CRelationMap.php on line 77
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 78 bytes) in /var/www/zbxnext_3274/include/classes/api/CApiService.php on line 286
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/zbxnext_3274/include/classes/api/CApiService.php on line 286
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/zbxnext_3274/include/classes/api/CApiService.php on line 286
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/zbxnext_3274/include/classes/api/CApiService.php on line 286
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 64 bytes) in 
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/zbxnext_3274/include/classes/api/CRelationMap.php on line 48
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 80 bytes) in /var/www/zbxnext_3274/include/db.inc.php on line 599
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 85 bytes) in /var/www/zbxnext_3274/include/db.inc.php on line 599
(mod_fastcgi.c.2673) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 78 bytes) in /var/www/zbxnext_3274/include/classes/api/CRelationMap.php on line 73

Moved from ZBXNEXT-3277 (25)

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61291:r61312

sandis.neilands It is better now however with 105k problems the "Problems" page still runs out of memory. This shouldn't happen since we show only 20 pages, e.g. 1000 problems by default.

gunarspujats CLOSED

(17) [F] Moved from ZBXNEXT-3277 (27)

sandis.neilands: What does the 'Action' column in 'Problems' page is supposed to show? Just the actions taken for problem event, problem and ok event?

sasha RESOLVED in r62041

Strings added:

• Actions on
• Failures

Strings deleted:

• Not sent

gunarspujats CLOSED

sasha added displaying of total number of actions in r62141

RESOLVED

gunarspujats CLOSED

(18) Different filter controls in Monitoring->Triggers, Monitoring->Overview and Monitoring->Problems

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61335.

gunarspujats CLOSED

(19) [F] if sorting by host empty list, errors

    Undefined variable: triggers_hosts [zabbix.php:21 → require_once() → ZBase->run() → ZBase->processRequest() → CView->getOutput() → include() → CScreenProblem->get() in include/classes/screens/CScreenProblem.php:166]
    Invalid argument supplied for foreach() [zabbix.php:21 → require_once() → ZBase->run() → ZBase->processRequest() → CView->getOutput() → include() → CScreenProblem->get() in include/classes/screens/CScreenProblem.php:166]

picture no_data_sort_host.jpg

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61348.
natalja.zabbix CLOSED

(20) [F] Based on specification "Displayed tag and tag value length is limited to N pixels". No limit to N pixels, now displaying all 255 symbols of tag and tag value
picture tag_lenght.png

sasha Already fixed in ZBXNEXT-3274 (18). CLOSED

(21) [F] no space between third tag and '...' , with space looks better

sasha RESOLVED in dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 r61436

gunarspujats CLOSED

svn://svn.zabbix.com/branches/dev/ZBXNEXT-3201-1 was merged to trunk r61447.

2nd phase was implemented in pre-3.2.0alpha2 r61801.

(22) 2nd phase translation strings:

Strings added:

• a time is expected

Strings deleted:

• DISCOVERED
• DOWN
• LOST
• Latest events
• UP
• Recent problem removed in r61447

oleg.egorov CLOSED

(23) changelog entry currently says :

improved event.get() and problem.get() methods

it might be worth specifying what was improved (performance ? something else ?)

sasha CLOSED as duplicate of (6)

richlv hmm, will the person updating the API docs remember to change the changelog entry ? maybe that's worth adding in that subissue ?

sasha You are right! FIXED in r64478

CLOSED

(24) [F] when use filtering options "Show:History", "Tags:any tag name and tag value" geting error

Error in query [SELECT e.eventid,e.objectid,e.clock,e.ns FROM events e WHERE e.source='0' AND e.object='0' AND EXISTS (SELECT NULL FROM event_tag et WHERE e.eventid=et.eventid AND et.tag='TagName' AND UPPER(pt.value) LIKE'%TESTVALUE%' ESCAPE '!') AND e.clock>='1408860125' AND e.clock<='1471932125' AND e.value='1' ORDER BY e.eventid DESC LIMIT 1001 OFFSET 0] [Unknown column 'pt.value' in 'where clause']

sasha RESOLVED in r61872

oleg.egorov CLOSED

(25) [F] Time bar issue in Monitoring->Problems if selected all period

sasha Cannot reproduce. Seems the bug is related to timebar. CLOSED

(26) [F] not renamed labels according specification in Administration->General->Trigger displaying options:
Display OK triggers for -> Display OK events for
On status change triggers blink for -> New PROBLEM events blink for

sasha it is decided to leave these labels without changes

CLOSED

(27) [F] according to the specification "Show events not older than (in days)" and "Max count of events per trigger to show" should be removed in Administration->General->GUI

sasha These fields already used in tr_status.php. Specification must be updated.

WON'T FIX

(28) [I] Missed upgrade patch, event_expire and event_show_max should be removed from config table.

sasha These fields already used in tr_status.php. Specification must be updated.

WON'T FIX

(29) [F] sorting by any type, change current page number
Steps to reproduce:
1. select second page
2. sort by severity
Result: page changed to third

oleg.egorov After bulk acknowledge happens same issue
I have page number 2
Period from 2016-03-13 22:14:40 till 2016-03-13 21:30:40
After bulk acknowledge happens redirect to page number 3

sasha RESOLVED in r61873

natalja.zabbix UI successfully tested

oleg.egorov CLOSED

(30) [A] Slow query

SQL (65.140725)

SELECT   e.eventid,e.objectid,e.clock,e.ns FROM events e WHERE e.source='0' AND e.object='0' AND (e.objectid BETWEEN '15353' AND '15398' OR e.objectid BETWEEN '15411' AND '15423' OR e.objectid BETWEEN '15493' AND '15505' OR e.objectid BETWEEN '16165' AND '16177' OR e.objectid BETWEEN '16180' AND '16189' OR e.objectid IN ('15440','15441','15442','15443','15543','15547','15548','15550','15551','15553','15561','15563','16162')) AND EXISTS (SELECT NULL FROM functions f,items i,hosts_groups hg,triggers t WHERE e.objectid=f.triggerid AND f.itemid=i.itemid AND i.hostid=hg.hostid AND (hg.groupid BETWEEN '4' AND '9' OR hg.groupid BETWEEN '16' AND '25' OR hg.groupid IN ('1','2','11','12','14','30','32','43','45','46','47','48')) AND i.hostid='10343' AND e.objectid=t.triggerid AND t.priority='5') AND e.acknowledged=0 AND e.clock>='1436821200' AND e.clock<='1457902800' AND e.value='1' ORDER BY e.eventid DESC LIMIT 1001 OFFSET 0

zabbix.php:21 → require_once() → ZBase->run() → ZBase->processRequest() → CView->getOutput() → include() → CScreenProblem->get() → CScreenProblem->getData() → CScreenProblem->getDataEvents() → CFrontendApiWrapper->get() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CFrontendApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → call_user_func_array() → CEvent->get() → DBselect() in include\classes\api\services\CEvent.php:379

Debug info:

Total time: 69.799992
Total SQL time: 66.112774000004
SQL count: 2339 (selects: 1523 | executes: 816)
Peak memory usage: 63.25M
Memory limit: 3072M

Installation:

3,055,333 - events
2,167 - triggers

sasha I can't reproduce this issue.

SQL (0.232991): SELECT   e.eventid,e.objectid,e.clock,e.ns FROM events e WHERE e.source='0' AND e.object='0' AND e.objectid IN ('13666','13782','13784','13786','13788','13790','13792','13794','13796','13798','13800','13802','13804','13806','13808','13810','13812','13814','13816','13818','13820','13822','13824','13826','13828','13830','13832','13834','13836','13838','13840','13842','13844','13846','13848','13850','13852','13854','13856','13858','13860','13862','13864','13866','13868','13870','13872','13874','13876','13878') AND EXISTS (SELECT NULL FROM functions f,items i,hosts_groups hg,triggers t WHERE e.objectid=f.triggerid AND f.itemid=i.itemid AND i.hostid=hg.hostid AND (hg.groupid BETWEEN '4' AND '16' OR hg.groupid IN ('1','2')) AND i.hostid IN ('10084','10105') AND e.objectid=t.triggerid AND t.priority IN ('2','3','4','5')) AND e.acknowledged=0 AND e.clock>='1408909797' AND e.clock<='1471981797' AND e.value='1' ORDER BY e.eventid DESC LIMIT 1001 OFFSET 0
zabbix.php:21 → require_once() → ZBase->run() → ZBase->processRequest() → CView->getOutput() → include() → CScreenProblem->get() → CScreenProblem->getData() → CScreenProblem->getDataEvents() → CFrontendApiWrapper->get() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CFrontendApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → call_user_func_array() → CEvent->get() → DBselect() in include/classes/api/services/CEvent.php:379

Debug info:

******************** Script profiler ********************
Total time: 0.298484
Total SQL time: 0.262083
SQL count: 58 (selects: 35 | executes: 23)
Peak memory usage: 6.75M
Memory limit: 512M

Installation:

1,135,455 - events
402 - triggers

sasha WON'T FIX

(31) [F] In Monitoring->Problems displaying event acknowledge errors.

Open in the new tab Event acknowledge , then try to submit space till page refreshed without error message.

sasha WON'T FIX

(32) [F] Triggers (tr_status.php) regression
Missed stime and period

In "Trigger" page select old, problem trigger, then on popup select "Problems" link... and there is no result, because it's was old issue.

sasha Already discussed with alexei. It was decided to show only recent problems from triggers popup menu.

WON'T FIX

(33) [F] macros not opened in trigger input after filtering

sasha RESOLVED in r61876

natalja.zabbix UI successfully tested

oleg.egorov CLOSED

(34) [F] Possible memory leak, tested on IE11
Leeks speed ~6kb\sec

Will be tested on other browsers.

Night test results:
IE memory leak by 16 hours is 422MB of RAM or ~7kb\sec
Chrome memory leak by hours is 241MB of RAM or ~4kb\sec

iivs My IE11 is eating 28kb/s. Over night it ate around 1.6GB of RAM. Trying to resize browser in the morning and using navigation to check if browser still works, it just freezes up and still continues to consume more memory. At this point I'm not sure if this is the only page or any page with 30s (default) refresh and left unattended for long periods of time.
FF crashed at unknown time.
This needs more investigation.

oleg.egorov Won't fix. CLOSED

Fixed in pre-3.2.0beta1 r61938.

When housekeeper remove an event (or in our test we truncated events table), the Monitoring => problems page shows an event age equal as the start of time, or unixtime at least. The events page seems to be OK.

See the attachments below.

backoffice.team, it is already fixed under ZBX-11132. Will be released in 3.2.0beta2.

(35) Show details filter option is not implemented

sasha RESOLVED in r62059

gunarspujats CLOSED

(36) Problems in CLOSING state are not blinking

sasha RESOLVED in r62060

gunarspujats CLOSED

(37) Applied new icons

old	new

sasha RESOLVED in r62125

gunarspujats CLOSED

(11), (17), (35), (36) and (37) are fixed in pre-3.2.0beta2 r62146.

(38) [F] incorrect values in "action" and "tag" column in exported csv file from Monitoring->Problem page. Tag column empty, but in action column tag values

iivs RESOLVED in r62308

natalja.zabbix ui successfully tested

sasha CLOSED

(39) [F] fixed displaying of actions popup; added footer for truncated action list

sasha RESOLVED in r62326.

Strings deleted:

• Actions on

oleg.egorov Fixed coding style in r62332. CLOSED

(38) and (39) are fixed in pre-3.2.0beta3 r62334.