Creating chaos in real life? Not fun - we probably all have enough of that! But creating chaos to test your system for vulnerabilities? It’s a great way to find issues before they become a problem for your customers. Chaos engineering is the idea that by purposefully overloading and breaking your system, you can see where vulnerabilities and failures happen before they get into production.
Want to run your own Chaos Gameday?
Gremlin provides tools to inject failure into your systems to target weaknesses. But how do you know what to target? The observability that Lightstep Observability gives you can help you answer that question. Using it’s tracing data, you can scale attacks to target not just one service, but all dependencies up and down the line, simulating cascading latency and errors across an application.
And once you’ve configured Gremlin to create the attack (based on information that Lightstep Observability has provided), you can use Lightstep Observability to quickly find the issues that start occurring.
You’ll learn how to:
- Use Lightstep Observability to determine where to target Gremlin attacks.
- Use a script to access the service hierarchy from Lightstep Observability and automatically start the attack with Gremlin based on Lightstep data.
- Use Lightstep Observability to find the issues caused by the attack.
Before you begin
You’ll need the following to complete this Learning Path:
- A Lightstep Observability account. Lightstep offers a free Community tier account. If you don’t already have an account, you can sign up here.
A Lightstep project with running services. You can use your own or you can fork the Lightstep version of the Hipster Shop (a multi-service web-based e-commerce app). Follow the instructions in the README to get it installed and running.
The services need to running in a container.
- A Gremlin account.
- Node.js installed on your machine. The Gremlin attack is configured using the Lightstep JS SDK and requires using npm.