IT services/Sla always 100%. Why?

[skogan]

Folks, I think we just have to bite the bullet on this one: The WHOLE IT Services /SLA function of Zabbix is riddled with bugs to the point of it being unuseable. Not to mention that it's basic idea is wrong to begin with.
That explains the lack of documentation and responce from Alexei.

This "feature" should never have made it into the stable release, not in it's present state at least.

[Aly]

There's a pretty nice explaination here

Eleventh paragraph is wrong. Read my article about min/max/none.

[acucatti]

Thanks for your answer Aly and skogan,

I had already read those posts, but still doesn´t work. I think I´m not doing or something wrong but could be missing anything.
Do you know if there is a bug on version 1.4.2 ?
Do i have to wait at least one week to SLA work properly, like sugested by some earlier post ? I dont think so ...
Neither the parents or the children work.
There is some other tip or workaroud ?

thanks again

[hardtofi]

Can anyone explain this behavior (screen shot below)? It's related to my post earlier in this thread.

The parent is configured with:
Depends on the child (not soft linked(?))
Calculation alg: min of child
Show sla: yes
Acceptable: 99.8
No service times
No links to trigger.

The child:
No dependency
Show SLA: yes
Acceptable: 99.8
No service times
Link to trigger: yes


If I click the bar with percentages of the parent it shows 3h 17m of problems last week, if I click the bar of the child it shows 0 time problems.

Is there any logic here I'm not understanding? I would have suspected both to have the same percentage of error.

(*edit : I'm using zabbix 1.4.4 compiled from source)

[Aly]

SLA of parent service is calculated depending on previous SLA, so if there was some other service(as leaf), then you deleted it and added new one, SLA of parent node will not be calculated only depending on new added service, it's also calculates all previous SLA(parent's node SLA).

[hardtofi]

SLA of parent service is calculated depending on previous SLA, so if there was some other service(as leaf), then you deleted it and added new one, SLA of parent node will not be calculated only depending on new added service, it's also calculates all previous SLA(parent's node SLA).

Thanks for the reply but the problem is that the trigger that the child is depending on is firing off regularly so the number reported by the parent is probably true, while the child is wrong.

If I click on the link [1s SLA on search] in the child on the "IT Services" page will I get the list attached (croped since it's very long). And this certainly isn't 100%.

[hardtofi]

I've been looking at the table zabbix.service_alarms now and it seems rows (for some IT services) are not being inserted there when the triggers goes off, and thus the lack of correct data. I tried inserting a few rows manually and that affects the percentage.

What is it that triggers the zabbix_serverd to call DBadd_service_alarm and insert rows there? Is there a bug or does it depend on something I might have missed in my configuration?