-
Change Request
-
Resolution: Fixed
-
Major
-
None
-
None
-
Sprint 81 (Oct 2021), Sprint 82 (Nov 2021), Sprint 83 (Dec 2021), Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022)
-
19
Current implementation of services was designed long time ago, it is rather limited and has significant limitations.
It would be nice to improve SLA reporting by introducing more flexible SLA definition (timezone, SLO, effective date, excluded downtimes) and SLI reporting showing all the numbers (SLO, SLI, uptime, downtime, error budget, etc).
Also it would be great to have ability to define multiple SLAs per service and link SLAs to services using tags.Â
- causes
-
ZBX-21084 Inconsistent Custom schedule default values for SLA create and SLA edit actions
- Open
-
ZBX-21110 "Failed to parse time string" runtime error observed for graphs with items without data
- Closed
- duplicates
-
ZBXNEXT-1673 Possibility to manipulate SLA by adding corrections
- Open
- is duplicated by
-
ZBXNEXT-1131 IT Services do not indicate start of actual collected data
- Open