Incident Handling: Difference between revisions

From Delft Solutions
Jump to navigation Jump to search
No edit summary
No edit summary
Line 17: Line 17:
# Communicate plan/next steps (even if that is gathering information)
# Communicate plan/next steps (even if that is gathering information)
# Communicate findings/results of executed plan, go back to previous step if not resolved
# Communicate findings/results of executed plan, go back to previous step if not resolved
# If there is no resolution to the incident, evaluate if the trigger needs updating/disabling
# Get a review of your resolution/conclusion
# Resolve incident
# Resolve incident



Revision as of 07:16, 4 August 2023

Critical incidents

  • Critical incidents are resolved within 16 hours.

Checklist

  1. Acknowledge on Zabbix and state who is responsible for resolving this in the description
  2. Determine affected clients
  3. Communicate to affected clients that the issue is being investigated
  4. Communicate plan/next steps (even if that is gathering information)
  5. Communicate findings/results of executed plan, go back to previous step if not resolved
  6. Resolve incident

Non-Critical incidents

  • Non-critical incidents are acknowledged within 9 hours and resolved within one week.

Checklist

  1. Acknowledge on Zabbix and state who is responsible for resolving this in the description
  2. Communicate plan/next steps (even if that is gathering information)
  3. Communicate findings/results of executed plan, go back to previous step if not resolved
  4. If there is no resolution to the incident, evaluate if the trigger needs updating/disabling
  5. Get a review of your resolution/conclusion
  6. Resolve incident

Informational incidents

  • Informational incidents are acknowledged within 72 hours

Checklist

  1. Acknowledge on Zabbix
  2. Sanity check the event, post result in thread
  3. If action needed, perform action