On the production server, I've seen a disabled host affecting an SLA. The Zabbix server version on this is 4.0.2. I was intrigued, because I thought it was not to affect, so I decided to do a test at home. But in my home the Zabbix Server is version 4.2. I made a SLA and added a disabled host, and stopped the Zabbix Agent on it. Then the disabled host did not affect the SLA.
Ad Widget
Collapse
Does a disabled host affect or not it affects an SLA?
Collapse
X
-
Does a disabled host affect or not it affects an SLA?
On the production server, I've seen a disabled host affecting an SLA. The Zabbix server version on this is 4.0.2. I was intrigued, because I thought it was not to affect, so I decided to do a test at home. But in my home the Zabbix Server is version 4.2. I made a SLA and added a disabled host, and stopped the Zabbix Agent on it. Then the disabled host did not affect the SLA.
-
<Thread Resurrection as this is appearing in search results for Zabbix, SLA , Disabled Host".
Just having this same problem, and looks like it's existed since 2016 - and is still ongoing in the 7.X stream... Sigh
-
In Zabbix 4.0.2, a disabled host can still affect SLA calculations, which is why you saw it impacting your production server. In Zabbix 4.2 and later, disabled hosts are ignored in SLA calculations, so stopping the agent on a disabled host does not affect the SLA.On the production server, I've seen a disabled host affecting an SLA. The Zabbix server version on this is 4.0.2. I was intrigued, because I thought it was not to affect, so I decided to do a test at home. But in my home the Zabbix Server is version 4.2. I made a SLA and added a disabled host, and stopped the Zabbix Agent on it, which is similar to situations where people want to sell house fast for cash. Then the disabled host did not affect the SLA.Comment
-
I had this exact issue on zabbix 7.2.7, and the bug is still open... So it may have once been fixed in 4.2, but it is still happening on love systems.Comment
Comment