[ZBXNEXT-5265] Limit the number of fetched Actions per problem in problem view Created: 2019 May 31 Updated: 2019 Jun 21 |
|
Status: | Need info |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F) |
Affects Version/s: | 4.2.1, 4.2.2 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Minor |
Reporter: | Arnaud Ligot | Assignee: | Zabbix Development Team |
Resolution: | Unresolved | Votes: | 1 |
Labels: | crash, frontend | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
PHP 7.3 |
Attachments: | memory profile.PNG |
Description |
Conditions:** We configured Zabbix to send all events to a custom php script dealing with all notifications. Thus there are a lots' of action linked to our problems. Steps to reproduce:
Result: White page/error 500/out of memory Analyze:
Workaround/solution: within include/actions.inc.php, function getEventsAction, when calling API::Alert()->get(), I added a new options: 'time_from' => time()-86400 .
This limit the number of Action it fetch and make everyting working again.
The best solution would probably be to fetch max n actions of each event where n would be configurable somewhere.
Bottom line: Thanks for all your great work!
|
Comments |
Comment by Arturs Lontons [ 2019 Jun 04 ] |
HI, Regards, |
Comment by Arnaud Ligot [ 2019 Jun 04 ] |
yes... I stopped once I reached 2Go ...
Anyway, the more ram I give, the more time it takes before the error... at 2Go, its about a minute...
Best regards,
a. |
Comment by Arturs Lontons [ 2019 Jun 10 ] |
Hi, |