Team B
[ZBXNEXT-5339] The division into pages of the list of triggers in services and maps Created: 2019 Jul 26 Updated: 2024 Apr 10 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Trivial |
| Reporter: | Smirnov Dmitriy | Assignee: | Zabbix Development Team |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | maps, pagination, performance, services, triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | Team B |
| Description |
|
Good day. Our infrastructure uses switch stacks consisting of hundreds of ports. Thousands and tens of thousands of triggers are created on one such node. In general, it does not bring any problems, except for the choice of triggers on the Services page and Maps. In these places, the list of triggers is not paginated and either loads for a very long time or does not load at all. Please consider the possibility of dividing the list of triggers into pages or otherwise simplify the process of selecting a trigger.
|
