Chaos Engineering in 60 Seconds - Process Killer Attack
Chaos Engineering in 60 Seconds - Process Killer Attack.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
Chaos Engineering
PD Summit21: Responding to Chaos with Gremlin and PagerDuty
Incident response is something you hope to never need, but when you do, you want it to go smoothly and seamlessly. Normally the knowledge of how to handle incidents within your company will be built up over time, getting better with each incident. While tools such as PagerDuty's Major Incidents Application can help you recover quickly, the process you follow is just as important. This documentation will allow you to learn from the start something which has taken us years to build up. Giving you a head start on how to deal with a major incident in a way which leads to the fastest possible incident recovery.
When Disaster Strikes: Ensuring Your DRP Actually Works
Black swan events are inherently unpredictable—you can’t prepare for every possible threat. Instead, you must identify the ways systems can fail and develop strategies to restore them to full service when these failures happen. But a disaster recovery plan (DRP) can’t be relied on until it’s been proven to work. The use of Chaos Engineering allows you to test your DRP much more safely and predictably than you could otherwise.
SRE's Guide to Chaos & Observability
Today’s distributed, cloud-based environments are incredibly complex. Not only does each component depend on many others, but modern systems are also highly dynamic—changing frequently as teams push new code or make updates to infrastructure. Taming this complexity to ensure reliability requires end-to-end observability to understand how components depend on each other. Additionally, proactive Chaos Engineering combined with AI-driven observability lets you uncover “unknown unknowns” that impact how your system will respond to different failure scenarios.
Building Reliable Applications Webinar 6 17 21
Test-driven development (TDD) is a process that ensures quality in the applications we develop while guarding against feature creep/skew. But as our applications have become increasingly complex, traditional testing methods are not enough. Traditional testing only evaluates what we know, but complex systems often fail due to unknowns—the things that are almost impossible to test because we are unaware of them. Chaos Engineering is the exception that allows us to test for what we don’t know.
Podcast: Break Things on Purpose | Taylor Dolezal, Senior Developer Advocate at HashiCorp
In this episode of the Break Things on Purpose podcast, we speak with Taylor Dolezal, Senior Developer Advocate at HashiCorp.
Self-service reliability with Internal Developer Platforms and Chaos Engineering
Get started with Gremlin's Chaos Engineering tools to safely, securely, and simply inject failure into your systems to find weaknesses before they cause customer-facing issues. Up until the early 2000s, developers and Ops (at the time IT) had separate and often competing objectives, separate department leadership, separate key performance indicators by which they were judged, and often worked on separate floors or even separate buildings.
Podcast: Break Things on Purpose | The Hill You'll Die On
In this episode of the Break Things on Purpose podcast, we ask our guests for their strong opinions.
Announcing the availability of Gremlin using AWS CloudFormation Public Registry
Get started with Gremlin's Chaos Engineering tools to safely, securely, and simply inject failure into your systems to find weaknesses before they cause customer-facing issues. We’re excited to announce that Gremlin is available on AWS CloudFormation Public Registry.