steadybit-extension-http

Steadybit

EC2 is part of the AWS Elastic Compute Cloud, which acquires and releases resources depending on the traffic demand. Check whether your application is elastic as well by rebooting an EC2 instance.

AWS achieves high availability via redundancy across different Availability Zones. Ensure that failover works seamlessly by simulating Zone outages.

Verify that an increased latency in a Redis cache is handled by your application properly by having increased processing time but still being able to maintain the throughput.

Check that your application handles a Redis cache downtime gracefully and continues to deliver its intended functionality. The cache downtime may be an unavailable Redis instance or a complete cluster.

An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.

An unavailable Oracle database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.

Your application should continue to function properly and indicate unavailability appropriately in case of increased connection latency to PostgreSQL. Additionally, this experiment can highlight requests that need optimization of timeouts to prevent dropped requests.

An unavailable PostgreSQL database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.

An unavailable database should be handled by your application gracefully and being indicated appropriately. Specifically, we want to ensure that at least one monitor in Datadog is alerting us to the outage. You can address a potential impact on your system by implementing e.g. a failover or caching mechanism.

Ensure that your pods become ready again when your containers exceed ephemeral storage.

If configured properly, Kubernetes is able to detect a non-responding pod and tries to fix it by simply restarting the unresponsive pod. Even so, the exact configuration requires careful consideration to avoid killing your pods too early or flooding your cluster’s traffic with liveness probes.

Kubernetes features a rolling update strategy to deploy new releases without downtime. When being under load this only works reliably when your load balancer and the Kubernetes readiness probe are configured properly and DNS caches are up-to-date.

When you need to scale your Kubernetes deployment, ensure that users don't notice any hiccups and that it seamlessly integrates into your load balancing.

When draining a node, Kubernetes should reschedule the pods on other nodes to achieve elasticity.

An unavailable Kafka is not user-visible as it leads to graceful degradation and downstream retries as soon as the Kafka is back available again.

HTTP

HTTP

HTTP

HTTP

Introduction

HTTP check periodically

HTTP check with fixed amount of calls

EC2 restart doesn't result in user-visible errors

AWS Zone Outage doesn't result in user-visible errors

Verify system unavailability status during Redis latency

Verify system unavailability status during Redis downtime