Hello Zabbix-Forums,
we use Zabbix to monitor systems via web scenarios. Based on the web scenario response codes there are triggers (200, 503 is accepted). Based on these triggers IT-services data is calculated (via the IT-Services module) and used for SLA reporting / calculation.
During a change a trigger has been set wrong. This made it trigger until it was corrected. While the basic data makes it clear that the service was available during that time, this distorted the recorded SLA for 2 days making it show less availability than factually existant.
Is there a way correct this wrongly displayed SLA? I have only found a way to completly flush the SLA statistics, which is, anyhow, not acceptable in this case.
The service_alarms table does not look promising. Maybe the trigger parts can be removed?
I appreciate all your answers and help!
we use Zabbix to monitor systems via web scenarios. Based on the web scenario response codes there are triggers (200, 503 is accepted). Based on these triggers IT-services data is calculated (via the IT-Services module) and used for SLA reporting / calculation.
During a change a trigger has been set wrong. This made it trigger until it was corrected. While the basic data makes it clear that the service was available during that time, this distorted the recorded SLA for 2 days making it show less availability than factually existant.
Is there a way correct this wrongly displayed SLA? I have only found a way to completly flush the SLA statistics, which is, anyhow, not acceptable in this case.
The service_alarms table does not look promising. Maybe the trigger parts can be removed?
I appreciate all your answers and help!
Comment