Handover - Revision history

Jakobbuis: points

2025-10-21T11:26:32Z

points

Jakobbuis at 11:24, 21 October 2025

2025-10-21T11:24:57Z

← Older revision		Revision as of 04:24, 21 October 2025
Line 1:		Line 1:
	When handing over the responsibility of '''first responder''' (FR), the following needs to happen:		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		* 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 > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]		* The current 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 > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# 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.		* 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 aware of the state of the SLA and knows what questions they wants to ask the current FR.

Jakobbuis: verb simplified, split run-on sentence

2025-10-21T11:24:19Z

verb simplified, split run-on sentence

← Older revision		Revision as of 04:24, 21 October 2025
Line 7:		Line 7:

	The following steps can be done async or in person:		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~~ [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel~~] if async)~~.		* The current FR informs the incoming FR he/she has been added to the sla-first-responder group. If the handover is conducted async, this is done in the [https://chat.dsinternal.net/#narrow/stream/13-Organisational #Organisational] channel.
	* 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 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.
	* The current FR shares with the incoming FR any particularities they should be aware of.		* The current FR shares with the incoming FR any particularities they should be aware of.

Jakobbuis: spelling

2025-10-21T11:22:30Z

spelling

← Older revision		Revision as of 04:22, 21 October 2025
Line 7:		Line 7:

	The following steps can be done async or in person:		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 [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if ~~asynq~~).		* The current FR announces/informs the incoming FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if async).
	* 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 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.
	* The current FR shares with the incoming FR any particularities they should be aware of.		* The current FR shares with the incoming FR any particularities they should be aware of.

Jakobbuis: reformulate imperative sentence, clarify assigned to current FR

2025-10-21T11:21:55Z

reformulate imperative sentence, clarify assigned to current FR

← Older revision		Revision as of 04:21, 21 October 2025
Line 9:		Line 9:
	* The current FR announces/informs the incoming FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if asynq).		* The current FR announces/informs the incoming FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational 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 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 current FR shares with the incoming FR any particularities they should be aware of.
	* 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].

Jakobbuis: remove undefined reference to a "SRE team", and split a partially conditional step in two

2025-10-21T11:20:39Z

remove undefined reference to a "SRE team", and split a partially conditional step in two

← Older revision		Revision as of 04:20, 21 October 2025
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] ~~and if part~~ of ~~the SRE team~~ [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 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]

Jakobbuis at 11:19, 21 October 2025

2025-10-21T11:19:05Z

← Older revision		Revision as of 04:19, 21 October 2025
Line 13:		Line 13:
	* 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] and if part of the SRE team [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 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] and if part of the SRE team [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 ~~and~~ disables Zabbix calling for the current FR ~~if they had that enabled by going to~~ Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]		* 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]

Jakobbuis: wording improvement FR references

2025-10-21T11:18:10Z

wording improvement FR references

Jakobbuis: Created page with "When handing over the responsibility of '''first responder''' (FR), the following needs to happen: * The handover can be initiated by both the upcoming FR or the acting FR * Acting FR adds the upcoming FR to the IPA sla-first-responder user group and enables Zabbix calling for the upcoming FR if they have that set by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions] * Before the handover, the..."

2025-10-17T13:53:13Z

Created page with "When handing over the responsibility of '''first responder''' (FR), the following needs to happen: * The handover can be initiated by both the upcoming FR or the acting FR * Acting FR adds the upcoming FR to the IPA sla-first-responder user group and enables Zabbix calling for the upcoming FR if they have that set by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions] * Before the handover, the..."

New page

When handing over the responsibility of '''first responder''' (FR), the following needs to happen:
* The handover can be initiated by both the upcoming FR or the acting FR
* Acting FR adds the upcoming FR to the IPA sla-first-responder user group and enables Zabbix calling for the upcoming FR if they have that set by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]
* Before the handover, the acting 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 upcoming FR makes sure they are aware of the state of the SLA and knows what questions they wants to ask the acting FR.
* The upcoming FR makes sure they are subscribed to the right channels.

The following steps can be done async or in person:
* The acting FR announces/informs the upcoming FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if asynq).
* If the acting FR wants to hand over responsibility for any ongoing incident they also state which incidents they want the upcoming FR to take over.
* If there are any particularities the upcoming FR needs to be aware of, those are shared.
* The upcoming FR asks their questions until they are satisfied and able to take over the FR
* The upcoming 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] and if part of the SRE team [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 upcoming FR announces/informs that they are now the acting FR over Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel]
* The now acting FR removes the previous FR from IPA the sla-first-responder user group and disables Zabbix calling for the previous FR if they had that enabled by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]

← Older revision		Revision as of 04:26, 21 October 2025
Line 1:		Line 1:
	When handing over the responsibility of '''first responder''' (FR), the following needs to happen:		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		* The handover can be initiated by both the incoming FR or the current FR.
	* The current 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 > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]		* The current 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 > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# 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.		* 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 aware of the state of the SLA and knows what questions they wants to ask the current FR.
Line 10:		Line 10:
	* 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 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.
	* The current FR shares with the incoming FR any particularities they should be aware of.		* The current FR shares with the incoming FR any particularities they should be aware of.
	* 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].		* 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].

← Older revision		Revision as of 04:18, 21 October 2025
Line 1:		Line 1:
	When handing over the responsibility of '''first responder''' (FR), the following needs to happen:		When handing over the responsibility of '''first responder''' (FR), the following needs to happen:
	* The handover can be initiated by both the ~~upcoming~~ FR or the ~~acting~~ FR		* The handover can be initiated by both the incoming FR or the current FR
	* ~~Acting~~ FR adds the ~~upcoming~~ FR to the IPA sla-first-responder user group and enables Zabbix calling for the ~~upcoming~~ FR if they have that set by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]		* 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 > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]
	* Before the handover, the ~~acting~~ 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.		* 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 ~~upcoming~~ FR makes sure they are aware of the state of the SLA and knows what questions they wants to ask the ~~acting~~ FR.		* 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 ~~upcoming~~ FR makes sure they are subscribed to the right channels.		* The incoming FR makes sure they are subscribed to the right channels.

	The following steps can be done async or in person:		The following steps can be done async or in person:
	* The ~~acting~~ FR announces/informs the ~~upcoming~~ FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if asynq).		* The current FR announces/informs the incoming FR has been added to the sla-first-responder group (In Zulip's [https://chat.dsinternal.net/#narrow/stream/13-Organisational Organisational channel] if asynq).
	* If the ~~acting~~ FR wants to hand over responsibility for any ongoing incident they also state which incidents they want the ~~upcoming~~ FR to take over.		* 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 ~~upcoming~~ 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 ~~upcoming~~ 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 ~~upcoming~~ 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] and if part of the SRE team [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 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] and if part of the SRE team [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 ~~upcoming~~ FR announces/informs that they are now the ~~acting~~ 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 ~~now acting~~ FR removes the ~~previous~~ FR from IPA the sla-first-responder user group and disables Zabbix calling for the ~~previous~~ FR if they had that enabled by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]		* The incoming FR removes the current FR from IPA the sla-first-responder user group and disables Zabbix calling for the current FR if they had that enabled by going to Zabbix > Configuration > Actions > [https://status.delftinfra.net/zabbix/actionconf.php?eventsource=0# Trigger actions]