[ZBXNEXT-8829] SLA vs SERVICE Downtime Created: 2023 Nov 10  Updated: 2023 Nov 10

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: 6.4.7
Fix Version/s: None

Type: Change Request Priority: Medium
Reporter: Cesar Inacio Martins Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: downtime,, services, sla,
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Web frontend - SLA Report



 Description   

Hi,

The SLA Report is very useful tool, however never was improved as should be... is a tool with a huge lack of resource which make it very frustrating.

So, after migrate my zabbix to version 6.x , I needed to reconfigure all my SLAs because the big change occurred on they way to work.

One BIG problem is the incorrect place to set the Excluded Downtimes.
I really don't understand why this option is into SLA configuration.

Downtimes are specific of services , example:
I have a SLA for all databases of the company .

However, I have databases which should run 24x7 without downtime and databases which have daily or weekly automatic maintenance where they came offline for some window of time.

This is specific of each database and should be configured on the SERVICE not on SLA.

The SLA I set only one for ALL databases , make no sense need to configure one SLA for each database only to configure the downtime specific for eachone.

To be flexible , this option could be existent on both configuration SLA and SERVICE, but MUST exists on SERVICES set.

Maybe , this could be added as "Aditional rule" on SERVICE.

 

 


Generated at Sat May 10 07:03:29 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.