Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Verify System Unavailability Status During RabbitMQ Downtime

An unavailable RabbitMQ cluster 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.
Targets:

Containers

Datadog monitors

Download now

Verify System Unavailability Status During RabbitMQ Downtime

An unavailable RabbitMQ cluster 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.
Targets:

Containers

Datadog monitors

Download now

Verify System Unavailability Status During RabbitMQ Downtime

An unavailable RabbitMQ cluster 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.
Targets:

Containers

Datadog monitors

Download now

Verify System Unavailability Status During RabbitMQ Downtime

An unavailable RabbitMQ cluster 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.
Targets:

Containers

Datadog monitors

Download now
Go back to list
The experiment editor showing the visual structure of the experiment.The experiment editor showing the visual structure of the experiment.

Intent

An unavailable RabbitMQ cluster 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.

Motivation

RabbitMQ downtime can lead to degraded system performance, lost data, and potentially long system recovery times. By testing the resilience of your system to RabbitMQ downtime, you can ensure that your system can handle the outage gracefully and continue to deliver its intended functionality. Additionally, you can identify any potential weaknesses in your system and take appropriate measures to improve its performance and resilience.

Structure

We will verify that a load-balanced user-facing endpoint fully works while having all pods ready. As soon as we simulate RabbitMQ downtime, we expect the system to indicate unavailability appropriately and maintain its throughput. To simulate downtime, we can shut down the RabbitMQ instance or cluster. The experiment aims to ensure that your system can handle the outage gracefully and continue to deliver its intended functionality. The performance should return to normal after the RabbitMQ instance or cluster is available again.


Download now

.yaml (3 kB)

It's quick and easy

  1. 1.

    Download .yaml file
  2. 2.

    Upload it inside Steadybit
  3. 3.

    Start your experiment!
Screenshot showing the Steadybit UI elements to import the experiment.yaml file into the Steadybit platform.
Tags
RabbitMQ
recoverability

Used Actions

See all
Blackhole

Drops network traffic (incoming and outgoing).

Attack

Attack

Containers

Start using Steadybit for free

Steadybit is free for personal use. Start your journey towards reliability!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
HubActionsTargetsExtensionsRecipes
© 2023 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon