Handover: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(remove undefined reference to a "SRE team", and split a partially conditional step in two) |
||
| Line 11: | Line 11: | ||
* If there are any particularities the incoming FR needs to be aware of, those are shared. | * If there are any particularities the incoming FR needs to be aware of, those are shared. | ||
* The incoming FR asks their questions until they are satisfied and able to take over the FR | * The incoming FR asks their questions until they are satisfied and able to take over the FR | ||
* The incoming FR ensures they are subscribed to the following channels on Zulip: [https://chat.dsinternal.net/#narrow/stream/23-SRE---General SRE - General], [https://chat.dsinternal.net/#narrow/stream/24-SRE-.23-Critical SRE # Critical] | * The incoming FR ensures they are subscribed to the following channels on Zulip: [https://chat.dsinternal.net/#narrow/stream/23-SRE---General SRE - General], [https://chat.dsinternal.net/#narrow/stream/24-SRE-.23-Critical SRE # Critical]. | ||
* If the incoming FR is a member of "The Team", they also subscribe to [https://chat.dsinternal.net/#streams/4/SRE%20##%20Non-critical SRE ## Non-Critical] and [https://chat.dsinternal.net/#streams/5/SRE%20###%20Informational SRE ### Informational]. | |||
* The incoming FR announces/informs that they are now the current FR over Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] | * The incoming FR announces/informs that they are now the current FR over Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] | ||
* The incoming FR removes the current FR from IPA the sla-first-responder user group. | * The incoming FR removes the current FR from IPA the sla-first-responder user group. | ||
* The incoming FR disables Zabbix calling for the current FR. This is completed through Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions] | * The incoming FR disables Zabbix calling for the current FR. This is completed through Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions] | ||
Revision as of 03:20, 21 October 2025
When handing over the responsibility of first responder (FR), the following needs to happen:
- The handover can be initiated by both the incoming FR or the current FR
- Prior FR adds the incoming FR to the IPA sla-first-responder user group and enables Zabbix calling for the incoming FR if they have that set by going to Zabbix > Configuration > Actions > Trigger actions
- Before the handover, the current FR must ensure that all active incidents are acknowledged (this includes alert emails or opened topics in SRE General, etc...), updated with the latest status, and properly documented.
- The incoming FR makes sure they are aware of the state of the SLA and knows what questions they wants to ask the current FR.
- The incoming FR makes sure they are subscribed to the right channels.
The following steps can be done async or in person:
- The current FR announces/informs the incoming FR has been added to the sla-first-responder group (In Zulip's Organisational channel if asynq).
- If the current FR wants to hand over responsibility for any ongoing incident, they also state which incidents they want the incoming FR to take over.
- If there are any particularities the incoming FR needs to be aware of, those are shared.
- The incoming FR asks their questions until they are satisfied and able to take over the FR
- The incoming FR ensures they are subscribed to the following channels on Zulip: SRE - General, SRE # Critical.
- If the incoming FR is a member of "The Team", they also subscribe to SRE ## Non-Critical and SRE ### Informational.
- The incoming FR announces/informs that they are now the current FR over Zulip's Organisational channel
- The incoming FR removes the current FR from IPA the sla-first-responder user group.
- The incoming FR disables Zabbix calling for the current FR. This is completed through Zabbix > Configuration > Actions > Trigger actions