Apply new Sysdig License
Scheduled Maintenance
Report for ACP
Completed
As the Sysdig-Prod license is approaching time of expiration, we will need to apply the new license to continue to utilise the service.
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
Update
As the Sysdig-Prod license is approaching time of expiration, we will need to apply the new license to continue to utilise the service.
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
In progress
As the Sysdig-Prod license is approaching time of expiration, we will need to apply the new license to continue to utilise the service.
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
Scheduled
As the Sysdig-Prod license is approaching time of expiration, we will need to apply the new license to continue to utilise the service.
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
This necessitates a very brief service interruption, as per the Sysdig documentation we require to restart some of the Sysdig Backend Components (however these are controlled by multi-replica deployments w/ failover, so impact should be minimal)
Given the short time-frame until expiration, this will be put forward as an Emergency Change (as there is less than 1/2 weeks to give notice)
This scheduled maintenance affected: Sysdig.