Ad Widget

Collapse

Weird SLA calculations

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • pinhafritaa
    Junior Member
    • Jun 2024
    • 7

    #1

    Weird SLA calculations

    Hi everyone, new member here, I've been configuring Zabbix for multi-tenancy, and one of things I'm working is the Services and SLA Reports.

    I have 3 FW that I want to monitor availability of them, for that, I picked the API port down trigger for SLA calculation. On the template, gave the trigger a tag named monit:uptime .
    On the firewall I have 3 tags: organization: potatoes; type:firewall; firewall:fw0x . (each firewall tag has a diferent number).
    On the service side have the parent service named firewall uptime and 3 child services, each named with the hostname of the firewalls.

    The SLA object has been configurated with only the necessary service tags and a reporting period of daily.

    The SLA Report measures are the following:
    fw01 service: 100%
    fw02 service: 94%
    fw03 service: 100%

    firewall uptime, parent service: 77%

    If all service weight are the same, shouldn't be taking the average of the 3 to take the parent service SLA?
    Last edited by pinhafritaa; 18-06-2024, 18:13.
  • Answer selected by pinhafritaa at 05-07-2024, 15:51.
    pinhafritaa
    Junior Member
    • Jun 2024
    • 7

    Well, some time has passed since this post, and the SLA calculation went back to normal. I'm assuming that because of setting up the service object on the same day as configuring the SLA policy does weird to the calculations.

    Comment

    • pinhafritaa
      Junior Member
      • Jun 2024
      • 7

      #2
      Well, some time has passed since this post, and the SLA calculation went back to normal. I'm assuming that because of setting up the service object on the same day as configuring the SLA policy does weird to the calculations.

      Comment

      Working...