[ZBXNEXT-6800] Support of complex service status calculation and propagation rules Created: 2021 Jul 29  Updated: 2024 Apr 10  Resolved: 2021 Sep 30

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 6.0.0alpha2, 6.0 (plan)

Type: New Feature Request Priority: Trivial
Reporter: Rostislav Palivoda Assignee: Andris Zeila
Resolution: Fixed Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PDF File ACC_ Support of complex service status calculation and propagation rules - v1.0.pdf     GIF File weight_doesnt_work.gif    
Issue Links:
Causes
Duplicate
is duplicated by ZBXNEXT-6611 Take into account services_times data... Open
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-6801 Frontend changes to support complex s... Specification change (Sub-task) Closed Andrejs Verza  
Team: Team A
Sprint: Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021)
Story Points: 7

 Description   

Current implementation of services was designed long time ago, it is rather limited and has significant limitations. Major limitations are:

  • scalability: it does not scale well, also bad user experience when number of services exceeds few hundreds
  • hard to configure: mapping based on triggers does not work well and requires significant effort
  • very limited visualization: no graphical representation of services, no good reporting
  • limited SLA calculation rules
  • no alerting in case of service status changes
  • user permissions: all or nothing

Proposed functionality will introduce more flexible status calculation and propagation rules.



 Comments   
Comment by Andrejs Verza [ 2021 Aug 30 ]

Implemented in

Updated documentation:

Generated at Tue Apr 01 11:11:05 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.