66
edits
Incident Handling: Difference between revisions
Jump to navigation
Jump to search
Visual status changes
No edit summary |
(Visual status changes) |
||
| Line 2: | Line 2: | ||
* Critical incidents are resolved within 16 hours. | * Critical incidents are resolved within 16 hours. | ||
Checklist | ===Checklist=== | ||
# Acknowledge on Zabbix and state who is responsible for resolving this in the description | # Acknowledge on Zabbix and state who is responsible for resolving this in the description | ||
# Determine affected clients | # Determine affected clients | ||
| Line 9: | Line 9: | ||
# 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 | ||
# Resolve incident | # Resolve incident | ||
===Additional context=== | |||
* Critical incidents are posted in '''Infrastructure'''. | |||
* When it is being tracked on GitLab a heavy check mark is added to the message. | |||
* Responses on the thread and on GitLab are automatically synced (to some extend) | |||
* When you reply with '''I agree that this has been fully resolved''' eventually Zabbix will pick this up and a green check mark is added to the message. | |||
== Non-Critical incidents == | == Non-Critical incidents == | ||