Ad Widget

Collapse

Remove / Change IT-Services recorded data / wrongly calculated SLA results

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • johntoe
    Junior Member
    • Jun 2015
    • 1

    #1

    Remove / Change IT-Services recorded data / wrongly calculated SLA results

    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!
  • BDiE8VNy
    Senior Member
    • Apr 2010
    • 680

    #2
    Contrary to my previous statement SLA calculation is indeed done, when accessing frontend sections. But corresponding alerts are added on event processing.

    Anyhow, it should be possible to manually manipulate the calculations on database level - no idea how though
    Meanwhile you might be interested in ZBXNEXT-1673. If so, consider to vote for it.

    The service_alarms table is indeed the one to look for. It represents the historic status of an IT-Service node:
    serviceid = ID of corresponding IT-Service node
    clock = point in time of status change
    value = value of status change. (see TRIGGER_SEVERITY_* in defines.inc.php for mapping)

    Note that value '0' has a special meaning. It represents OK instead of 'Not classified' That's btw the reason/side-effect why not supporting this severity in IT-Services.

    Edit:
    One can add one-time downtimes to hide problem periods from SLA calculation. But that's rather a kind of work-around.
    Last edited by BDiE8VNy; 06-06-2015, 20:59.

    Comment

    • arapozo
      Junior Member
      • Jan 2018
      • 9

      #3
      I don't know if you were able to solve this but I found out how to add previous triggers to a service manually. Let me know if you're still interested.

      Comment

      Working...