Incident Handling: Difference between revisions

Incident Handling (view source)

43 bytes added , 4 March

no edit summary

116

edits

@@ Line 16: / Line 16: @@
 # If unresolved, create new plan
 # When resolved:
-** Verify trigger is no longer firing
+## Verify trigger is no longer firing
-** Mark Zulip topic as resolved if no other incidents for host
+## Mark Zulip topic as resolved if no other incidents for host
-** Check for related triggers and resolve them
+## Check for related triggers and resolve them
-==== Common Issues ====
+==== Common issues ====
 * SSH down: Check MaxStartups throttling, apply custom SSH config
 * No backup: Verify backup process is running, check devteam email
@@ Line 31: / Line 31: @@
 # Check metrics sheet for existing milestone
 # If milestone exists:
-** Add Lynx project ID to Zulip topic
+## Add Lynx project ID to Zulip topic
-** Add 🔁 emoji if ID already reported
+## Add 🔁 emoji if ID already reported
 # If no milestone:
-** Add to metrics sheet
+## Add to metrics sheet
-** Create Lynx project (priority 99, then 20 after estimation)
+## Create Lynx project (priority 99, then 20 after estimation)
-** Create Kimai activity
+## Create Kimai activity
-** Document IDs in Zulip topic
+## Document IDs in Zulip topic
-=== Informational Incidents (72hr acknowledge) ===
+=== Informational Incidents ===
+Informational incidents must be acknowledged within 72 hours.
 # Acknowledge in Zabbix