Steadybit

Create a Steadybit experiment to simulate a service outage by stopping a container.

Monitor the configured alerting system (e.g., Datadog, Prometheus) for triggered alerts.

Verify that the alerts contain relevant information about the outage.

Analyze the alert response time and accuracy.

Adjust alerting thresholds or configurations as needed.

Create a Steadybit experiment to simulate a network partition by blocking traffic between two microservices.

Monitor application performance and error rates.

Check if the application automatically reroutes traffic or degrades gracefully.

Analyze the impact on user experience and data consistency.

Implement fault-tolerance mechanisms to improve resilience.

Create a Steadybit experiment to trigger a DB cluster failover by promoting a standby instance to primary.

Monitor application performance and data consistency.

Verify that the application automatically connects to the new primary database.

Analyze the failover time and data loss.

Optimize the failover process to minimize downtime.

Create a Steadybit experiment to generate high CPU load on one or more cores.

Monitor application performance metrics such as response time and error rates.

Check if the application scales automatically or degrades gracefully.

Analyze the CPU utilization and resource contention.

Optimize the application code or infrastructure to handle high CPU load.

Create a Steadybit experiment to simulate an outage of an entire availability zone.

Monitor the failover to the disaster recovery site.

Verify that the application and data are successfully recovered.

Analyze the recovery time and data loss.

Optimize the disaster recovery plan to minimize downtime and data loss.

Create a Steadybit experiment to block access to DNS servers.

Monitor application's ability to resolve hostnames.

Verify fallback mechanisms such as cached DNS records.

Analyze impact on application functionality.

Implement DNS caching or alternative DNS resolution strategies.