Loading...

XML

Word

Printable

Type: Change Request
Resolution: Fixed
Priority: Major
Fix Version/s: 3.4.0alpha1, 3.4 (plan)
Affects Version/s: 2.2.6
Component/s: Server (S)
Labels:
- alerts
- multiple
- performance
- process

Sprint:
Sprint 2, Sprint 3, Sprint 4, Sprint 5, Sprint 6, Sprint 7, Sprint 8, Sprint 9, Sprint 10, Sprint 11
Story Points:
10

Alerter process may be overloaded very quickly.
How about adding support for multiple alerter processes?

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

retries_left.png
57 kB
2017 Jun 02 14:04
sub_issue_1.png
15 kB
2017 Mar 20 11:16
sub_issue_2.png
17 kB
2017 Mar 20 11:57
sub_issue_6.log
3.88 MB
2017 Mar 21 10:22
zabbix_server.log.part
296 kB
2017 Jun 22 16:10

is duplicated by

ZBXNEXT-2714 Split out alerter process to multiple child processes

Closed

ZBXNEXT-3020 Multiple Alert Processes

Closed

ZBXNEXT-3560 email notification slowdown

Closed

ZBX-12315 Zabbix Alerter 100%

Closed

ZBX-9446 Escalations via custom media types within the same step are not sent in parallel

Closed

ZBX-9654 if the jabber server is unavailable, Zabbix does not send e-mails

Closed

ZBX-9702 Simultaneous access to a serial GSM modem from multiple server processes corrupts communications

Closed

ZBX-9705 Alert sending from watchdog can block if some media type is "slow"

Closed

mentioned in: Page Loading...

(3 is duplicated by, 1 mentioned in)

There are no Sub-Tasks for this issue.

Assignee:: Unassigned

Reporter:: Marc

Team:: Team A

Votes:: 20 Vote for this issue

Watchers:: 28 Start watching this issue

Created:: 2014 Sep 06 12:40

Updated:: 2024 Apr 10 16:10

Resolved:: 2017 Jul 19 13:35