gremlin.com
Last updated: 3/20/2026valid
Independent Directory - Important Information
This llms.txt file was publicly accessible and retrieved from gremlin.com. LLMS Central does not claim ownership of this content and hosts it for informational purposes only to help AI systems discover and respect website policies.
This listing is not an endorsement by gremlin.com and they have not sponsored this page. We are an independent directory service with no affiliation to the listed domain.
Copyright & Terms: Users should respect the original terms of service of gremlin.com. If you believe there is a copyright or terms of service violation, please contact us at support@llmscentral.com for prompt removal. Domain owners can also claim their listing.
Current llms.txt Content
# Reliability Testing & Chaos Engineering | Gremlin > Reduce downtime, improve resilience, and protect revenue. Gremlin helps engineering teams find and fix reliability risks before they become expensive outages. ## Aws - [Getting started with Chaos Engineering on AWS](https://www.gremlin.com/aws): Everything you need to safely, securely, and simply run Chaos Engineering experiments on AWS. ## Blog - [Proactively improve reliability | Gremlin Blog](https://www.gremlin.com/blog): Prevent outages, innovate faster, and earn customer trust with Gremlin's Reliability Management and Chaos Engineering platform. - [Achieving FMEA goals faster with Chaos Engineering](https://www.gremlin.com/blog/achieving-fmea-goals-faster-with-chaos-engineering): Failure mode and effects analysis (FMEA) is a decades-old method for identifying all possible failures in a design, a manufacturing or assembly process, or a product or service. In the last few years it has begun to be used by companies looking to make their computer systems better. While FMEA is not officially an ISO standard procedure like ISO 31000 Risk Management, there are ISO implementations specific to certain applications. Instead, it is broader and able to be applied to a wide range of needs. - [Why Reliability Engineering Matters: an Analysis of Amazon's Dec 2021 US-East-1 Region Outage](https://www.gremlin.com/blog/analysis-amazon-dec-2021-us-east-1-region-outage): In the field of Chaos Theory, there’s a concept called the Synchronization of Chaos—disparate systems filled with randomness will influence the disorder in other systems when coupled together. From a theoretical perspective, these influences can be surprising. It’s difficult to understand exactly how a butterfly flapping its wings could lead to a devastating tornado. But we often see the influences of seemingly unconnected systems play out in real life. - [Automate reliability testing in your CI/CD pipeline using the Gremlin API](https://www.gremlin.com/blog/automate-reliability-testing-in-your-ci-cd-pipeline-using-the-gremlin-api): For many software engineering teams, most testing is done in their CI/CD pipeline. New deployments run through a gauntlet of unit tests, integration tests, and even performance tests to ensure quality. However, there's one key test type that's excluded from this list, and it's one that can have a critical impact on your application and your organization: reliability tests. - [Avoiding Problems When the Clocks Change](https://www.gremlin.com/blog/avoiding-problems-when-the-clocks-change): The season is upon us when clocks change for Daylight Savings Time. Sure, distributed systems are frequently set by default to use UTC as the basis for all time-related settings and those systems then perform any needed locale-specific adjustments in the agent. However, this is not true for everyone and many of us are responsible for systems that rely on timestamps in a locale that adjusts the time twice a year. For the rest of us, even when using UTC, things can get complicated with leap years and the occasional leap second. - [Four pillars of a best-in-class reliability program](https://www.gremlin.com/blog/best-in-class-reliability-program-pillars): Reliability impacts every organization, whether you plan for it or not. Leading companies take matters into their own hands and get ahead of incidents by building reliability programs. But since many of these programs are still nascent, how do you know what good looks like? - [Best practices for a resilient AWS architecture](https://www.gremlin.com/blog/best-practices-for-a-resilient-aws-architecture): Get best practices based on the AWS Well-Architected Framework for autoscaling, redundancy, dependencies, and more to make your AWS architecture more resilient. - [Best Practices for Testing Zone Redundancy](https://www.gremlin.com/blog/best-practices-for-testing-zone-redundancy): Gremlin Principal Software Engineer Sam Rossoff shares key best practices and strategies for effectively testing zone redundancy. - [Bring Chaos Engineering to your CI/CD pipeline](https://www.gremlin.com/blog/bring-chaos-engineering-to-your-ci-cd-pipeline): Chaos Engineering is all the rage these days. So many Site Reliability Engineering (SRE) teams have started performing chaos experiments in QA testing or stage environments, while moving toward limited and expanding testing in production systems. The industry is just beginning to think about the benefits of chaos testing earlier in the process, in the CI/CD pipeline. But we expect that to change because reliability and resiliency need to shift left and start at the beginning. - [Building more reliable financial systems with Chaos Engineering](https://www.gremlin.com/blog/building-more-reliable-financial-systems-with-chaos-engineering): The financial services industry has built in more capital buffers to prevent market shocks from bringing another economic collapse. In addition to these financial controls, many banks and personal trading platforms have begun building resiliency into information technology shocks. Despite these new precautions, we’re still seeing outages today, preventing customers from depositing and withdrawing their money, completing transactions, and executing trades during key events. - [Chaos Engineering and Add-To-Cart](https://www.gremlin.com/blog/chaos-engineering-and-add-to-cart): An E-Commerce Example of Preparing for Black Friday. - [Chaos Engineering and Windows: Mitigating common Windows failure scenarios](https://www.gremlin.com/blog/chaos-engineering-and-windows): Microsoft Windows is a popular operating system for many enterprise applications, such as Microsoft SQL Server clusters and Microsoft Exchange Servers. About 30% of the world’s web application hosting systems are running Windows, making it an important part of every enterprise’s plans to prevent outages and enhance reliability. - [Chaos Engineering & Autonomous Optimization combined to maximize resilience to failure](https://www.gremlin.com/blog/chaos-engineering-autonomous-optimization-combined-to-maximize-resilience-to-failure): This blog is co-authored by Giuseppe Nardiello, Vice President of Product Management & Business Dev at Akamas. - [Chaos Engineering is Not Just Tools—It's Culture](https://www.gremlin.com/blog/chaos-engineering-is-not-just-tools-its-culture): To wield chaos tools responsibly, your organization needs a trusting, collaborative culture. - [Chaos Engineering and Resilience Testing Tools: Build vs Buy](https://www.gremlin.com/blog/chaos-engineering-tools-build-vs-buy): Not sure whether you should build or buy a Fault Injection tool for Chaos Engineering and resilience testing? Check out the pros and cons of building vs buying. - [Chaos Engineering tools: myth vs. fact](https://www.gremlin.com/blog/chaos-engineering-tools-myth-vs-fact): With so many Chaos Engineering tools available, it’s no surprise that SRE and platform leaders are doing their homework when choosing a platform to help them build and scale their Chaos Engineering programs. But like anything else you can research on the internet, there’s a lot of noise and hype that you need to wade through. - [Defining Dashboard Metrics](https://www.gremlin.com/blog/defining-dashboard-metrics): “How do you measure availability?” - [Design thinking leads to Chaos Engineering](https://www.gremlin.com/blog/design-thinking-leads-to-chaos-engineering): In the Double Diamond Framework for Innovation from the Design Council in the United Kingdom, there are four defined stages in the process of creating a good design. They illustrate those stages using a diagram like this (ours is simplified slightly from theirs). - [Ensuring reliability when modernizing financial applications](https://www.gremlin.com/blog/ensuring-reliability-when-modernizing-financial-applications): For decades, information technology in the financial services industry meant deploying bulky applications onto monolithic systems like mainframes. These systems have a proven track record of reliability, but don’t offer the flexibility and scalability of more modern architectures such as microservices and cloud computing. During periods of unexpectedly high demand, this inflexibility can cause technical issues for organizations ranging from personal trading platforms to major banks. Likewise, periods of low demand result in unused computing resources, costing these same organizations money. - [Ensuring Runbooks are Up-to-Date](https://www.gremlin.com/blog/ensuring-runbooks-are-up-to-date): One thing that all technical documentation for software that is still in active development has in common is that if it is not already outdated, it will be. We must be intentional if we want information to stay current. This includes runbooks. - [Ensuring your AI systems can scale to meet demand](https://www.gremlin.com/blog/ensuring-your-ai-systems-can-scale-to-meet-demand): Demand for AI services is ever-increasing. Are your systems prepared? This blog teaches you how to prepare for sudden demand surges. - [Fault Injection in your release automation](https://www.gremlin.com/blog/fault-injection-in-your-release-automation): A Gremlin Principal Engineer goes over Fault Injection and resilience testing in the CI/CD and release automation portion of an SDLC. - [Five mindset shifts for effective reliability programs](https://www.gremlin.com/blog/five-mindset-shifts-for-effective-reliability-programs): When people think about reliability, it’s easy to focus on incident response and moving fast to fix outages. This reactive approach to reliability can very quickly lead to burnout as you bounce from incident to incident. - [What are the four Golden Signals?](https://www.gremlin.com/blog/four-golden-signals): When it comes to building reliable and scalable software, few organizations have as much authority and expertise as Google. Their Site Reliability Engineering Handbook, first published in 2016, details their practices to maintain reliability as Google scaled. But when you have over a million servers running thousands of services across more than twenty data centers, how do you monitor them in a consistent, logical, and relevant way? The answer is with the four Golden Signals: latency, traffic, error rate, and resource saturation. - [Seven tests to measure and improve reliability: what matters and how it works](https://www.gremlin.com/blog/four-reliability-tests): Learn how to take reliability from a "nice to have" to a standard operating practice within your organization. We'll show you seven easy tests you can use to start building resilient systems. - [Gartner: tips for improving reliability](https://www.gremlin.com/blog/gartner-tips-for-improving-reliability): In their report titled “IT Resilience — 7 Tips for Improving Reliability, Tolerability and Disaster Recovery”, Gartner presents seven strategies for improving the resilience posture of your critical systems. These recommendations range from how to get started, to identifying IT hazards and risks to reliability, to capturing metrics and translating them into business value. - [Getting started with Blackhole attacks](https://www.gremlin.com/blog/getting-started-with-blackhole-attacks): In today’s distributed, cloud-native world, network connectivity is just as important as reliable hardware. The migration from monoliths to microservices and on-prem datacenters to public clouds means our applications are much more dependent on healthy networks. But as systems become more distributed and network diagrams become more complex, so does the risk of failure. If a network card, switch, router, API gateway, firewall, or ethernet cable fails, it could take our entire application offline. We need to design applications and services to be resilient to these kinds of failures, and the Blackhole attack can help. - [Getting started with CPU attacks](https://www.gremlin.com/blog/getting-started-with-cpu-attacks): The CPU attack is one of the most common attack types run by Gremlin users. CPU attacks let you consume CPU capacity on a host, container, Kubernetes resource, or service. This might sound like a trivial exercise, but consuming even small amounts of CPU can reveal unexpected behaviors on our systems. These behaviors can manifest as poor performance, unresponsiveness, or instability. - [Getting started with Disk attacks](https://www.gremlin.com/blog/getting-started-with-disk-attacks): Persistent storage is one of the more difficult aspects of managing distributed systems. When we attach a storage device to a host—whether it’s flash storage, network attached storage (NAS), or old fashioned spinning disks—we generally don’t give it much thought until we start running distributed applications or need to increase capacity. But there’s more that can go wrong with storage, and this can have unexpected consequences for our systems, services, and applications. - [Getting started with DNS attacks](https://www.gremlin.com/blog/getting-started-with-dns-attacks): Whenever an online service goes down, you're likely to hear three words: "it was DNS!" Blaming DNS might be a running joke among network admins and engineers, but it's one rooted in experience. DNS problems are known for causing massive, Internet-wide outages such as the 2021 Akamai outage that temporarily made the websites for Delta Air Lines, American Express, Airbnb, and others unreachable. Since DNS is a critical component of modern networks, outages can have a huge impact, so teams must design their systems to be capable of withstanding and recovering from DNS problems. - [Getting started with IO attacks](https://www.gremlin.com/blog/getting-started-with-io-attacks): Storage devices remain one of the most significant bottlenecks in modern systems. CPU and RAM speed seems to increase exponentially year over year, and although there have been large improvements in IO performance with solid state (SSD) and NVMe drives, moving data to and from persistent storage is still orders of magnitude slower than moving it to and from memory. In scalable cloud applications, this slowness can have a major impact on performance, latency, and the user experience. To replicate this effect ourselves, we can use the IO attack. - [Getting started with Latency attacks](https://www.gremlin.com/blog/getting-started-with-latency-attacks): As the world becomes more dependent on cloud-native systems, the tolerance for slow services is decreasing. Users expect instantaneous access to services, whether it's for work, entertainment, or even cloud infrastructure. Even small amounts of latency can significantly decrease user satisfaction: nearly half of all users expect web pages to load in under two seconds, and as many as 28% of users will permanently abandon a slow site. The problem is, how can we test and verify that our applications and services will perform well even when network conditions are less than ideal? - [Getting started with Memory attacks](https://www.gremlin.com/blog/getting-started-with-memory-attacks): Memory (or RAM, short for random-access memory) is a critical computing resource that stores temporary data on a system. Memory is a finite resource, and the amount of memory available determines the number and complexity of processes that can run on the system. Running out of RAM can cause significant problems such as system-wide lockups, terminated processes, and increased disk activity. Understanding how and when these issues can happen is vital to creating stable and resilient systems. - [Getting started with Packet Loss attacks](https://www.gremlin.com/blog/getting-started-with-packet-loss-attacks): Imagine this: you're in the middle of an important presentation when all of a sudden your video feed starts to stutter. You hear other people speaking, but their words are choppy. A message comes through Slack from one of your co-workers: "I think your connection cut out." You scramble to try different solutions—restarting your videoconferencing application, checking your Internet connection, switching to your phone—but ultimately, your presentation gets cut short. - [Getting started with Process Killer attacks](https://www.gremlin.com/blog/getting-started-with-process-killer-attacks): Modern applications come in a variety of forms–monoliths, microservices, serverless functions, and containers to name a few–but at the heart of all of these are processes. Processes are the fundamental unit of execution that we use to run programs, and although we need processes to run our applications, software engineers rarely think about them. We leave it to the operating system to manage them for us, and rather than monitor individual processes for performance and availability, we monitor services as a whole. This doesn’t mean we shouldn’t care about them, as even one failed process can make an entire system unstable. - [Getting started with Shutdown attacks](https://www.gremlin.com/blog/getting-started-with-shutdown-attacks): For many years, system uptime was the primary measure of reliability, especially when the most popular method of running software was on bare metal, on-premises servers. If a server was shutdown, rebooted, or otherwise became unavailable, downtime was expected until a system administrator could manually restart it. The introduction of virtualization in the early 2000s—followed by the rise of public cloud platforms—made it easier to automatically detect and reboot shutdown systems, but this didn't address the core problem of reliance on uptime. Applications were—and often still are—designed with the expectation that the underlying systems will have unlimited uptime, and this simply isn't realistic. We need to design our applications with the expectation that systems will shutdown, reboot, and fail suddenly due to power outages or other unexpected state changes. - [Getting started with Time Travel attacks](https://www.gremlin.com/blog/getting-started-with-time-travel-attacks): It's the middle of the night when your phone goes off. You rub your eyes and unlock the screen to see a SEV 1 alert from your incident management tool. The application is down, multiple cloud server instances are offline, and the remaining instances are being overwhelmed by the sudden increase in demand. - [Failure Flags helps build testable, reliable software—without touching infrastructure](https://www.gremlin.com/blog/gremlin-failure-flags-test-software): Building provably reliable systems means building testable systems. Testing for failure conditions is the only way to... - [Gremlin for AWS](https://www.gremlin.com/blog/gremlin-for-aws): Gremlin is introducing Gremlin for AWS, a suite of tools to more easily find and fix the reliability risks that cause downtime on AWS. Gremlin for AWS enables engineering teams on AWS to prevent incidents, monitor and test systems for known causes of failure, and gain visibility into the reliability posture of their applications. - [How to verify, document, & prove compliance with Gremlin](https://www.gremlin.com/blog/gremlin-for-compliance): Find out how Gremlin can help companies in regulated industries comply with Operational Resilience requirements like DORA, APRA CPS230, FCA PS21/3, and more. - [Gremlin for DORA compliance: how financial services firms build digital resilience–and prove it](https://www.gremlin.com/blog/gremlin-for-dora-compliance-how-financial-services-firms-build-digital-resilience-and-prove-it): The Digital Operational Resilience Act (DORA) is set to significantly impact the financial sector. Coming into full effect in 2025, this EU regulation will set new standards for information and communications technology (ICT) risk management. In this landscape, how can financial firms ensure they’re not only compliant, but also operationally resilient? - [Managing and improving reliability using Gremlin's Reliability Dashboard](https://www.gremlin.com/blog/gremlins-reliability-dashboard): Part of a successful reliability program is being able to monitor and review your progress toward improving reliability. Being able to run tests on services is a big part of it, but how can you tell you're making progress if you can only see your latest test results? There should be a way to track improvements or regressions in your reliability testing practice across your organization in a way that's easy to digest. That's where the Reliability Dashboard comes in. - [Hitting reliability goals in the face of layoffs](https://www.gremlin.com/blog/hitting-reliability-goals-in-the-face-of-layoffs): It’s rough when there are layoffs and you have to still keep everything going with fewer people. That's when you want to lean on your partners and embrace automation and core best practices. With resiliency, that means choosing something like Gremlin that has pre-built test scenarios so you can deploy the agent, then get the results and spend your time mitigating instead of building all of the tests and custom experiments. - [How a major retailer tested critical serverless systems with Failure Flags](https://www.gremlin.com/blog/how-a-major-retailer-tested-critical-serverless-systems-with-failure-flags): Find out how Gremlin helped a major retailer test region failover for a critical service built on AWS Lambda using Failure Flags. - [How dependency discovery works in Gremlin](https://www.gremlin.com/blog/how-dependency-discovery-works-in-gremlin): Gremlin’s dependency discovery automatically finds your services’ dependencies and tests their resiliency, giving you a complete view of your reliability. Learn how it works in our latest blog. - [Five ways Gremlin helps organizations meet DORA requirements](https://www.gremlin.com/blog/how-gremlin-helps-meet-dora-resilience): DORA establishes stringent standards for financial services firms operating in the EU. Gremlin’s Reliability Management Platform helps organizations meet DORA requirements by automating the tracking, monitoring, and testing of ICT services and infrastructure for resiliency risks. This article discusses five ways Gremlin can help. - [How Gremlin helps you meet Google's Infrastructure Reliability standards](https://www.gremlin.com/blog/how-gremlin-helps-you-meet-googles-infrastructure-reliability-standards): In January of 2023, Google released its infrastructure reliability guide, which provides guidelines on how to build high-availability applications in Google Cloud. While it's written for Google Cloud, it provides some excellent general-purpose information on how to architect reliable applications on any cloud provider, including: - [How Gremlin runs a GameDay](https://www.gremlin.com/blog/how-gremlin-runs-a-gameday): You might be familiar with GameDays at this point. From watching our Introduction to GameDay webinar, viewing our Demo video, and reading our tutorial, you’ve probably learned that GameDays were created with the goal of increasing reliability by purposely creating major failures on a regular basis. Better yet, perhaps your own team has run a GameDay and learned something new about their services’ behavior during failure scenarios. At this point, you might be wondering, “How does Gremlin run their own internal GameDay?” - [Reliable AI models, simulations, and more with Gremlin's GPU experiment](https://www.gremlin.com/blog/how-gremlins-gpu-experiment-makes-ai-models-simulations-and-video-encoding-more-resilient): Build more resilient machine learning and AI models, video streaming, simulations, and more with Gremlin’s GPU experiment. - [How Gremlin's reliability score works](https://www.gremlin.com/blog/how-gremlins-reliability-score-works): In order to make reliability improvements tangible, there needs to be a way to quantify and track the reliability of systems and services in a meaningful way. This "reliability score" should indicate at a glance how likely a service is to withstand real-world causes of failure without having to wait for an incident to happen first. Gremlin's Reliability Score feature allows you to do just that. - [How reliability differs between monolithic and microservice-based architectures](https://www.gremlin.com/blog/how-reliability-differs-between-monolithic-and-microservice-based-architectures): Moving from a monolithic architecture to a microservice-based one is a massive and often failure-prone process. Learn about the reliability risks unique to microservices and how to avoid them. - [How reliability engineering can verify disaster recovery plans](https://www.gremlin.com/blog/how-reliability-engineering-can-verify-disaster-recovery-plans): Learn how reliability engineering and Gremlin can help test your disaster recovery plans to make sure you’re prepared—and compliant with regulations. - [How reliability testing and load testing are complementary](https://www.gremlin.com/blog/how-reliability-testing-and-load-testing-are-complementary): How can you tell if your systems are reliable when under load? A common answer is to open your observability dashboards, wait for a high-traffic event (like Black Friday), and cross your fingers. - [How role-based access control (RBAC) works in Gremlin](https://www.gremlin.com/blog/how-role-based-access-control-rbac-works-in-gremlin): Gremlin recently released custom role-based access controls (RBAC) for greater control over your reliability testing. Learn how it works in this blog post. - [How the Gremlin agent fails safely](https://www.gremlin.com/blog/how-the-gremlin-agent-fails-safely): Reliability testing shouldn’t feel risky. Learn how Gremlin makes testing safer with fail-safe agents and automatic rollbacks. - [How to adapt software testing for the cloud](https://www.gremlin.com/blog/how-to-adapt-software-testing-for-the-cloud): Cloud adoption has almost reached its saturation point. 94% of enterprises ran workloads in the cloud in 2018, and more than half planned to migrate more workloads throughout 2019. We often associate cloud computing with production applications and infrastructure, but it’s also a prime platform for QA. - [How to be prepared for cloud provider outages](https://www.gremlin.com/blog/how-to-be-prepared-for-cloud-provider-outages): Check out these testing best practices teams should follow to minimize the impact of cloud provider outages so they don’t catch you by surprise. - [How to build reliable services with unreliable dependencies](https://www.gremlin.com/blog/how-to-build-reliable-services-with-unreliable-dependencies): Dependencies are everywhere, and they make reliability work difficult. How can you build reliable when you depend on services that could fail at any time, and that you have no control over? Our latest blog has the answers. - [How to build zone-redundant cloud instances and clusters](https://www.gremlin.com/blog/how-to-build-zone-redundant-cloud-instances-and-kubernetes-clusters): Learn how to distribute your Amazon EC2 instances and Kubernetes worker nodes across multiple availability zones (AZs) for greater reliability and redundancy. - [How to define and measure the reliability of a service](https://www.gremlin.com/blog/how-to-define-and-measure-the-reliability-of-a-service): More and more teams are moving away from monolithic applications and towards microservice-based architectures. As part of this transition, development teams are taking more direct ownership over their applications, including their deployment and operation in production. A major challenge these teams face isn't in getting their code into production (we have containers to thank for that), but in making sure their services are reliable. - [How to deploy a multi-availability zone Kubernetes cluster for High Availability](https://www.gremlin.com/blog/how-to-deploy-ha-kubernetes-across-availability-zones): Many cloud infrastructure providers make deploying services as easy as a few clicks. However, making those services high availability (HA) is a different story. What happens to your service if your cloud provider has an Availability Zone (AZ) outage? Will your application still work, and more importantly, can you prove it will still work? - [How to ensure Amazon DynamoDB meets your reliability goals](https://www.gremlin.com/blog/how-to-ensure-amazon-dynamodb-meets-your-reliability-goals): Amazon DynamoDB is a NoSQL database service boasting high availability, high durability, and single-digit millisecond performance. It offers a wealth of reliability features such as automatic replication across multiple Availability Zones in an AWS region, automatic backups, in-memory caching, and optional multi-region and multi-master replication. Since it’s a fully-managed service, we don’t need to worry about things like provisioning hardware, maintaining servers, or replicating data, as these are all provided in the base product or available as add-ons. - [How to ensure your Kubernetess cluster can tolerate lost nodes](https://www.gremlin.com/blog/how-to-ensure-your-kubernetes-cluster-can-tolerate-lost-nodes): Kubernetes is known for its redundancy features, but that doesn’t make it infallible. Learn what the risks are of having a Kubernetes node fail, and how you can prepare for them using Gremlin. - [How to ensure your Kubernetes Pods and containers can restart automatically](https://www.gremlin.com/blog/how-to-ensure-your-kubernetes-pods-and-containers-can-restart-automatically): What happens when your Kubernetes container fails? Does it restart, or does it enter a crash loop? Learn how to ensure your containers restart reliability with Gremlin. - [How to fix and prevent CrashLoopBackOff events in Kubernetes](https://www.gremlin.com/blog/how-to-fix-kubernetes-crashloopbackoff): It's one of the most dreaded words among Kubernetes users. Regardless of your software engineering skill or seniority level, chances are you've seen it at least once. There are a quarter of a million articles on the subject, and countless developer hours have been spent troubleshooting and fixing it. We're talking, of course, about CrashLoopBackOff. - [How to fix and prevent ImagePullBackOff events in Kubernetes](https://www.gremlin.com/blog/how-to-fix-kubernetes-imagepullbackoff): You'll often hear the term "containers" used to refer to the entire landscape of self-contained software packages: this includes tools like Docker and Kubernetes, platforms like Amazon Elastic Container Service (ECS), and even the process of building these packages. But there's an even more important layer that often gets overlooked, and that's container images. Without images, containers as we know them wouldn't exist—but this means that if our images fail, running containers becomes impossible. - [How to fix Kubernetes init container errors](https://www.gremlin.com/blog/how-to-fix-kubernetes-init-container-errors): One of the most frustrating moments as a Kubernetes developer is when you go to launch your pod, but it fails to start… - [How to troubleshoot unschedulable Pods in Kubernetes](https://www.gremlin.com/blog/how-to-fix-kubernetes-unschedulable-pods): Kubernetes is built to scale, and with managed Kubernetes services, you can deploy a Pod without having to worry... - [How to fix the root cause of a failed reliability test](https://www.gremlin.com/blog/how-to-fix-the-root-cause-of-a-failed-reliability-test): You’ve run your reliability tests, and unfortunately, some of them failed. No need to panic: we’ll tell you how to turn that F into an A. - [How to identify and map service dependencies](https://www.gremlin.com/blog/how-to-identify-and-map-service-dependencies): Modern applications are a web of interdependent services. As applications grow in size and complexity, and as more engineering teams adopt service-based architectures like microservices, this web becomes deeper and denser. Eventually, keeping track of the interdependencies between services becomes a complex and time-consuming task in and of itself. In addition, if any of these dependencies fails, it can have cascading impacts on the rest of your services and on the application as a whole. - [How to load-balance across multiple availability zones for improved redundancy](https://www.gremlin.com/blog/how-to-load-balance-across-multiple-availability-zones-for-greater-redundancy): Load balancers are great at distributing traffic across individual hosts, but what about zones? This blog explains cross-zone load balancing, and how it can help you improve throughput and reliability. - [How to make your AI-as-a-Service more resilient](https://www.gremlin.com/blog/how-to-make-your-ai-as-a-service-more-resilient): Getting an AI-powered service up and running is hard; keeping it running is even harder. Read how AI-as-a-service systems can fail and how Gremlin makes them reliable. - [How to make your services resilient to slow dependencies](https://www.gremlin.com/blog/how-to-make-your-services-resilient-to-slow-dependencies): Our applications increasingly rely on services we don’t control. What happens when those services become unreliable? This blog post explains how to build software that stays available and responsive, even if your dependencies aren’t. - [How to prevent accidental load balancer deletions](https://www.gremlin.com/blog/how-to-prevent-accidental-aws-elb-load-balancer-deletions): Accidentally deleting cloud resources happens more often than you’d think. Learn how to enable deletion protection for your AWS Elastic Load Balancers (ELBs) and lower your risk of service outages. - [How to detect and prevent memory leaks in Kubernetes applications](https://www.gremlin.com/blog/how-to-prevent-memory-leaks-kubernetes-applications): In our last blog, we talked about the importance of setting memory requests when deploying applications to Kubernetes. We explained how memory requests lets you specify how much memory (RAM for short) Kubernetes should reserve for a pod before deploying it. However, this only helps your pod get deployed. What happens when your pod is running and gradually consumes more RAM over time? - [How to Prioritize Reliability Work Using Gremlin's Reliability Calculator](https://www.gremlin.com/blog/how-to-prioritize-reliability-work-using-gremlins-reliability-calculator): Even the simplest applications can consist of several microservices and as complexity increases, it can be very difficult to decide where to focus your reliability efforts. As engineers with only so many hours in a day, we want to ensure any time we spend thinking about reliability (and not the newest feature) will have the maximum effect. - [How to make your services zone redundant](https://www.gremlin.com/blog/how-to-run-a-zone-redundancy-test-using-gremlin): Learn how to prepare for—and become resilient to—availability zone and region outages. - [How to Safely Manage Change in a CI/CD World](https://www.gremlin.com/blog/how-to-safely-manage-change-in-a-ci-cd-world): Change management exists because it ensures the attention of many eyes and that much care is taken before modifying production systems, hopefully creating some reliability. The reason that change management processes don’t exist in modern systems is that our systems change so rapidly that no review panel could possibly keep up. This article proposes a way to keep the reliability factor alive while moving to a new, better methodology. - [How to scale your systems using CPU utilization](https://www.gremlin.com/blog/how-to-scale-your-systems-based-on-cpu-utilization): Scaling on CPU usage is a fundamental practice in cloud computing. Learn why CPU-based scaling is so important, how to set CPU scaling thresholds, and how to validate those thresholds using Gremlin. - [How to ensure your Kubernetes Pods have enough CPU](https://www.gremlin.com/blog/how-to-set-cpu-requests-kubernetes-pods): A common risk is deploying Pods without setting a CPU request. While it may seem like a low-impact, low-severity issue, not using CPU requests can have a big impact, including preventing your Pod from running. In this blog, we explain why missing CPU requests is a risk, how you can detect it using Gremlin, and how you can address it. - [How to keep your Kubernetes Pods up and running with liveness probes](https://www.gremlin.com/blog/how-to-set-kubernetes-liveness-probes): Getting your applications running on Kubernetes is one thing: keeping them up and running is another thing entirely. While the goal is to deploy applications that never fail, the reality is that applications often crash, terminate, or restart with little warning. Even before that point, applications can have less visible problems like memory leaks, network latency, and disconnections. To prevent applications from behaving unexpectedly, we need a way of continually monitoring them. That's where liveness probes come in. - [How to ensure your Kubernetes Pods have enough memory](https://www.gremlin.com/blog/how-to-set-memory-requests-kubernetes-pods): Memory (or RAM, short for random-access memory) is a finite and critical computing resource. The amount of RAM in a system dictates the number and complexity of processes that can run on the system, and running out of RAM can cause significant problems, including: - [How to standardize resiliency on Kubernetes](https://www.gremlin.com/blog/how-to-standardize-resiliency-on-kubernetes): Use this framework to improve Kubernetes resiliency at scale with a combination of organizational standards, resilience testing, and reliability risk monitoring. - [How to test AWS managed services with Gremlin](https://www.gremlin.com/blog/how-to-test-aws-managed-services-with-gremlin): How do you run reliability tests on services that you don’t manage? This blog explains how to manage reliability when using cloud services, including AWS, GCP, and Azure. - [Why it's important to test for expiring TLS/SSL certificates](https://www.gremlin.com/blog/how-to-test-for-expired-tls-ssl-certificates-using-gremlin): Transport Layer Security (TLS), and its preceding protocol, Secure Sockets Layer (SSL), are essential to the modern Internet. Encrypting network communications using TLS protects users and organizations from publicly exposing in-transit data to third parties. This is especially important for the web, where TLS secures HTTP traffic (HTTPS) between backend servers and customers’ browsers. TLS is so important that browsers will display warnings for insecure pages, search engines reduce SEO rankings for insecure pages, and the average percentage of web pages using HTTPS increased from 45% in 2015 to 99% in 2022. - [How to use host redundancy to improve service reliability and availability](https://www.gremlin.com/blog/how-to-use-host-redundancy-to-improve-service-reliability-and-availability): Learn how to prepare for—and become resilient to—host and instance outages using Gremlin. - [How to validate memory-intensive workloads scale in the cloud](https://www.gremlin.com/blog/how-to-validate-memory-intensive-workloads-in-the-cloud): Managing memory usage in cloud workloads is challenging. Learn how to determine your memory and RAM requirements, how to autoscale based on memory usage, and how to ensure you’re ready for high-traffic events using Gremlin. - [If you're adopting Kubernetes, you need Chaos Engineering](https://www.gremlin.com/blog/if-youre-adopting-kubernetes-you-need-chaos-engineering): When Ticketmaster started their Kubernetes migration, they had to address a huge problem: whenever ticket sales opened for a popular event, as many as 150 million visitors flooded their website, effectively causing distributed denial of service (DDoS) attacks. With new events happening every 20 minutes and $7.6 billion in revenue at stake, outages could mean hundreds of thousands in lost sales. - [Implementing cost-saving strategies on Amazon EC2 with Chaos Engineering](https://www.gremlin.com/blog/implementing-cost-saving-strategies-on-amazon-ec-2-with-chaos-engineering): The COVID-19 pandemic has created a state of uncertainty, and many organizations are turning to cost-saving measures as a precaution. In a survey by PwC, 74% of CFOs expect a significant impact on their operations and liquidity. As a result, many organizations are looking to reduce costs wherever possible, and this includes cloud computing. - [Improve M&A success rates by testing for system reliability](https://www.gremlin.com/blog/improve-m-a-success-rates-by-testing-for-system-reliability): Coming out of recessions, merger and acquisition volume typically picks up as lower interest rates drop the cost of capital and Corporate Development teams begin executing on the strategies they’ve developed during the holding periods. This year has been no exception, with $350 billion spent on tech acquisitions to date. This period is a boon for entrepreneurs seeking exits and for companies trying to expand their businesses into new markets or increase market share. - [Incremental Reliability Improvement](https://www.gremlin.com/blog/incremental-reliability-improvement): If you improved reliability by just 1% each day, how long would it take for you to get that “extra 9”? That’s an interesting question. This article begins by exploring the potential for small improvements to add up like compound interest. It concludes with a list of practical steps we can take that improve system reliability. - [Infographic: Resilience and reliability in the cloud](https://www.gremlin.com/blog/infographic-resilience-and-reliability-in-the-cloud): Created in partnership with AWS, this infographic shows the impact of outages, the most common causes of outages, and the results companies get from investing in resilience. - [Insights to keep AI applications reliable](https://www.gremlin.com/blog/insights-to-keep-ai-applications-reliable): AI has become a massive investment for companies, but how do you keep AI applications reliable? Check out these insights from Gremlin, Nobl9, and Pagerduty to find out! - [Intelligent Health Checks: one-click observability for reliability tests](https://www.gremlin.com/blog/intelligent-health-checks-one-click-observability-for-reliability-tests): Figuring out what to monitor can be a challenge. That’s why Gremlin does it for you. Learn how Gremlin automatically creates and monitors critical metrics for your AWS services. - [Interpreting your reliability test results](https://www.gremlin.com/blog/interpreting-your-reliability-test-results): You’ve run your reliability tests and got your results…now what? This blog explains how to turn your insights into actions and, ultimately, into more reliable services. - [Introducing Custom Reliability Test Suites, Scoring and Dashboards](https://www.gremlin.com/blog/introducing-custom-reliability-test-suites-and-scoring): Last year, we released Reliability Management, a combination of pre-built reliability tests and scoring to give you a consistent way to define, test, and measure progress toward reliability standards across your organization. - [Introducing Detected Risks](https://www.gremlin.com/blog/introducing-detected-reliability-risks): We're excited to introduce a new enhancement to help teams build more reliable software: Detected Risks. - [Introducing Gremlin: Orchestrating Chaos](https://www.gremlin.com/blog/introducing-gremlin-orchestrating-chaos): Today is an exciting day for our team at Gremlin. After nearly two years in the making, we're proud to share that Gremlin's "Reliability as a Service" is publicly available! We're also excited to announce our $7.5M Series A funding, led by Index Ventures and Amplify Partners, as well as several customers leveraging Gremlin to increase their system's reliability, including Twilio, Expedia, Confluent, and Remind. - [Introducing Scenarios to prepare for real-world outages](https://www.gremlin.com/blog/introducing-scenarios): Since 2017, Gremlin has offered a platform to run Chaos Engineering experiments, enabling our customers to increase the reliability of their applications. Gremlin provides a variety of different failure modes across state, resource, network, and application to test your reliability. However until now, while running a single Chaos Engineering attack has been simple, we’ve received many customer requests to simplify planning and tracking an experiment to simulate a real-world outage. - [Is your microservice a distributed monolith?](https://www.gremlin.com/blog/is-your-microservice-a-distributed-monolith): Your team has decided to migrate your monolithic application to a microservices architecture. You’ve modularized your business logic, containerized your codebase, allowed your developers to do polyglot programming, replaced function calls with API calls, built a Kubernetes environment, and fine-tuned your deployment strategy. But soon after hitting deploy, you start noticing problems. Services take a long time to start, failures cascade from one container to the next, and small changes involve redeploying the entire application. Weren’t microservices supposed to solve these problems? - [How to ensure consistent Kubernetes container versions](https://www.gremlin.com/blog/kubernetes-container-image-version-uniformity): One of Kubernetes' killer features is its ability to seamlessly update applications no matter how large your deployment is. Did a developer make a code change, and now you need to update a thousand running containers? Just run kubectl apply -f manifest.yaml and watch as Kubernetes replaces each outdated pod with the new version. - [Lessons from Alaska’s outage: Redundant ≠ resilient](https://www.gremlin.com/blog/lessons-from-alaskas-outage-redundant-resilient): Redundancy is a core part of designing resilient architectures, but only if you build the right amount of redundancy. Find that sweet spot of redundancy with resilience testing. - [Making Your APIs More Resilient with Gremlin](https://www.gremlin.com/blog/making-your-apis-more-resilient-with-gremlin): Here's the thing: when a company measures their critical services, APIs are often considered second class-citizens. But the fact of the matter is that APIs are a core part of an organization's infrastructure, and not understanding their weaknesses can lead to performance issues and downtime. - [Maximizing your reliability on AWS](https://www.gremlin.com/blog/maximizing-your-reliability-when-using-aws-services): Learn how to maximize reliability when running workloads on Amazon EC2, EKS, ECS, and other services. - [Measure your reliability risk, not your engineers](https://www.gremlin.com/blog/measure-your-reliability-risk-not-your-engineers): Reliability metrics should uncover risks and enable your teams to improve reliability, not create defensiveness and blame games. - [Measuring the impact of your reliability work with reports](https://www.gremlin.com/blog/measuring-the-impact-of-your-reliability-work-with-reports): Learn how Gremlin’s built-in reporting tools track your reliability work, find high-priority reliability risks in your environment, and demonstrate your progress towards greater reliability. - [Monitoring Your Chaos Engineering Experiments With Datadog](https://www.gremlin.com/blog/monitoring-your-chaos-engineering-experiments-with-datadog): Chaos Engineering, much like monitoring, is about continually removing uncertainty from the way your system behaves, especially under stress or failure. Controlling the cause of system failure (Chaos Engineering) while measuring its effect (Monitoring) allows your team to rapidly experiment and improve upon the systems they build. - [Observability and incident response need resilience testing](https://www.gremlin.com/blog/observability-and-incident-response-need-resilience-testing): Find out how observability, incident response, and resilience testing work together to help you make your system more reliable, resilient, and available. - [Introducing Process Exhaustion: How to scale your services without overwhelming your systems](https://www.gremlin.com/blog/process-exhaustion-scale-services-without-overwhelming-systems): Gremlin’s Process Exhaustion experiment lets you test how resilient your systems are when many processes are running. Learn how it works and why you should use it in our latest blog. - [Reducing reliability risks in the cloud with the AWS Well-Architected Framework](https://www.gremlin.com/blog/reducing-cloud-reliability-risks-with-the-aws-well-architected-framework): This blog post is an introduction to the AWS Well-Architected Framework (WAF), AWS’ official guide to building cloud-optimized systems and infrastructure. We explain what it is, the benefits of using it, and how Gremlin helps you adopt it. - [Reliability recommendations when adopting Kubernetes](https://www.gremlin.com/blog/reliability-recommendations-when-adopting-kubernetes): General reliability best practices when adopting Kubernetes. - [Your reliability scorecard: How to measure and track service reliability](https://www.gremlin.com/blog/reliability-scorecards-how-to-measure-and-track-service-reliability): Learn how Gremlin helps you track and manage your progress towards improved reliability with its comprehensive, built-in reporting tools. - [Reliability testing: Definition, history, methods, and examples](https://www.gremlin.com/blog/reliability-testing-definition-history-methods-and-examples): Reliability testing is the process of projecting and testing a system’s probability of failure throughout the development lifecycle in order to plan for and reach a required level of reliability, target a decreasing number of failures prior to launch, and to target improvements after launch. That is a difficult mission, especially as systems increase in complexity. The purpose of reliability testing is not to achieve perfection, but to reach a level of reliability that is acceptable before releasing a software product into the hands of customers. - [Resiliency is different on AWS: Here’s how to manage it](https://www.gremlin.com/blog/resiliency-is-different-on-aws-heres-how-to-manage-it): Learn about the reliability risks you can still run into when deploying to AWS, and how to avoid them. - [Setting better SLOs using Google's Golden Signals](https://www.gremlin.com/blog/setting-better-slos-using-googles-golden-signals): To many engineers, the idea that you can accurately and comprehensively track your application's user experience using just a few simple metrics might sound far-fetched. Believe it or not, there are four metrics that aim to do just that. They're called the four Golden Signals and should be a core part of your observability and reliability practices. - [How to show reliability results to your organization](https://www.gremlin.com/blog/show-reliability-results): Building momentum for a reliability program can be tough. Improving reliability takes time, effort, and resources. But when everything from launching new features to improving security demands those same resources, it can be a struggle to get the buy-in you need to address reliability risks. - [Simple Kubernetes Targeting for Your Chaos Experiments](https://www.gremlin.com/blog/simple-kubernetes-targeting-for-your-chaos-experiments): Today we’re excited to introduce native Kubernetes support to the Gremlin Reliability as a Service platform. Gremlin users can now easily discover, visualize, and target their Kubernetes objects within our web app and using our API. Now, when kicking off an experiment, Gremlin will intelligently select the containers underlying the specified Kubernetes objects so that you can be confident that your application runs the way you expect it to on Kubernetes. - [Simulating artificial intelligence (AI) service outages with Gremlin](https://www.gremlin.com/blog/simulating-artificial-intelligence-service-outages-with-gremlin): Learn how to leverage artificial intelligence (AI) services while avoiding downtime caused by outages. - [How a simple metric drives reliability culture at Slack](https://www.gremlin.com/blog/slack-reliability-culture-metrics): How do you track reliability in an organization with hundreds of engineers, dozens of daily production changes, and over 32 million monthly users? Even more, how do you do this in a way that's simple, presentable to executives, and doesn't dump a ton of extra work on to engineers' plates? - [Strategies for migrating to Kubernetes](https://www.gremlin.com/blog/strategies-for-migrating-to-kubernetes): Learn various techniques for migrating workloads from traditional monolithic application architectures to Kubernetes. - [Technology Business Management and Chaos Engineering](https://www.gremlin.com/blog/technology-business-management-and-chaos-engineering): Technology Business Management (TBM) is a decision-making tool that helps organizations maximize the business value of information technology (IT) spending by adjusting management practices. With TBM, IT is transformed to run like a business instead of merely a cost center. Decisions are made based on overall business needs like reliability and customer satisfaction. - [10 Most Common Kubernetes Reliability Risks](https://www.gremlin.com/blog/ten-most-common-kubernetes-reliability-risks): These Kubernetes reliability risks are present in almost every Kubernetes deployment. While many of these are simple configuration errors, all of them can cause failures that take down systems. Make sure that your teams are building processes for detecting these risks so you can resolve them before they cause an outage. - [Test serverless and application-level reliability with Failure Flags](https://www.gremlin.com/blog/test-serverless-and-application-level-reliability-with-failure-flags): Run resilience tests at the application level in serverless, container, Kubernetes, and service mesh environments with Gremlin Failure Flags. - [Testing doesn't stop at staging](https://www.gremlin.com/blog/testing-doesnt-stop-at-staging): Originally published April 27, 2020. - [Testing for expiring TLS and SSL certificates using Gremlin](https://www.gremlin.com/blog/testing-for-expiring-tls-and-ssl-certificates-using-gremlin): TLS certificates are a critical part of the modern web, but they require rotating. Learn why expiring certificates are such a big problem, and how Gremlin helps you stay ahead of them. - [Testing the reliability of your fulfillment center](https://www.gremlin.com/blog/testing-the-reliability-of-your-fulfillment-center): Fulfillment pipelines for order management in e-commerce have a lot of intricate moving parts that depend on one another. Sales orders, fulfillment, negotiation, shipment, and receipt are closely interconnected but require different actions while depending on one another closely. You also need messaging around order statuses, conditions, actions, rules, and inventory, just to name a few of the important parts of these complex systems. - [After the Retrospective: The 2017 Amazon S3 Outage](https://www.gremlin.com/blog/the-2017-amazon-s-3-outage): Systems fail. Even Amazon breaks. Despite our best efforts, technology is never perfect. In this first post of a series, we look at the Amazon S3 outage of 2017 in a blameless way, seeking to learn from it things we can do to enhance the reliability of our own systems. - [The case for Fault Injection testing in Production](https://www.gremlin.com/blog/the-case-for-fault-injection-testing-in-production): Gremlin Principal Engineer Sam Rossoff shows you when you should run Fault Injection tests in non-production and Production environments. - [The Cost of Downtime](https://www.gremlin.com/blog/the-cost-of-downtime): In 2016, IHS Markit surveyed 400 companies and found downtime was costing them a collective $700 billion per year. How do you estimate your own cost? - [The Discipline of Chaos Engineering](https://www.gremlin.com/blog/the-discipline-of-chaos-engineering): Last time, we introduced you to the idea of breaking things on purpose in order to build more reliable systems. By triggering failures intentionally in a controlled way, we gain confidence that our systems can deal with those failures before they occur in production. - [The Dual Approach in Scaling: Chaos Engineering and Performance Engineering](https://www.gremlin.com/blog/the-dual-approach-in-scaling-chaos-engineering-and-performance-engineering): “Do you want the most blazing program that works most of the time? Or do you want a program that maybe runs a little bit slower but it lets you sleep at night because it’s solid? I’ll go with solid every time” - Bill Kennedy - [The KPIs of improved reliability](https://www.gremlin.com/blog/the-kpis-of-improved-reliability): This article was originally published on May 5, 2022. - [The two kinds of failure testing](https://www.gremlin.com/blog/the-two-kinds-of-failure-testing): Learn more about exploratory testing and validation testing, the two most common uses of Fault Injection. - [Three key facts about serverless reliability](https://www.gremlin.com/blog/three-key-facts-about-serverless-reliability): Serverless means not managing servers, but you still need to consider reliability. In our latest blog, learn why and how to build resilient serverless applications. - [Three reliability best practices when using AI agents for coding](https://www.gremlin.com/blog/three-reliability-best-practices-when-using-ai-agents-for-coding): AI agents can help developers move faster, but they can also introduce potential failures into your system. Find out best practices for reliability to keep human and AI errors from causing outages. - [Three roles you need for reliability success](https://www.gremlin.com/blog/three-roles-you-need-for-reliability-success): Find out who needs to be at the table to make your systems more reliable, improve resilience, and increase the availability of your applications. - [Three serverless reliability risks you can solve today using Failure Flags](https://www.gremlin.com/blog/three-serverless-reliability-risks-you-can-solve-today-using-failure-flags): Just because your app is serverless doesn’t mean you don’t need to think about reliability. Learn three of the top causes of serverless failures—and how to prevent them—in our latest blog. - [Treat reliability risks like security vulnerabilities by scanning and testing for them](https://www.gremlin.com/blog/treat-reliability-risks-like-security-vulnerabilities): Finding, prioritizing, and mitigating security vulnerabilities is an essential part of running software. We’ve all recognized that vulnerabilities exist and that new ones are introduced on a regular basis, so we make sure that we check for and remediate them on a regular basis. - [Treating Containers As First-Class Citizens](https://www.gremlin.com/blog/treating-containers-as-first-class-citizens): When we launched Gremlin late last year, we knew the journey ahead would be two-fold. First and foremost, we would need to educate companies, ultimately changing the way they think about operations and shifting the culture to be much more proactive. And then we’d need to build a product which enabled them to do just that. We knew that in traditional organizations, too much engineering time was spent fighting fires and addressing problems after they’ve already impacted customers. - [Uncovering hidden reliability risks in complex systems](https://www.gremlin.com/blog/uncovering-hidden-reliability-risks-in-complex-systems): Learn how Gremlin automatically detects reliability risks in your environment. Review risks and implement fixes before your customers ever notice any issues. - [Understanding your application’s critical path](https://www.gremlin.com/blog/understanding-your-applications-critical-path): It’s 3 a.m. You’re lying comfortably in bed when suddenly your phone starts screeching. It’s an automated high-severity alert telling you that your company’s web application is down. Exhausted, you open the website on your phone and do some basic tests. Everything looks ok at first, but then you realize customers can’t log into their accounts or make purchases. What happened, and what does this mean for your application? - [Updating the Industry's Reliability Practices](https://www.gremlin.com/blog/updating-the-industrys-reliability-practices): Companies will continue to struggle to implement good reliability practices if the only opportunity to improve are adjustments made after production failures. - [More Flexibility in Testing Your Environment with Gremlin’s New Infrastructure Attack Options](https://www.gremlin.com/blog/upgrades-to-gremlins-infrastructure-attacks): We’ve recently made upgrades to our CPU, disk, and memory attacks to provide more configurability, improve reliability, and enhance ease of use. Infrastructure attacks (Resource, State, and Network attacks) are at the core of Gremlin’s functionality. These attacks provide stresses on your infrastructure, highlighting application weaknesses and bugs that lead to incidents or outages, creating a poor user experience. - [Using Chaos Engineering to Demonstrate Regulatory Compliance](https://www.gremlin.com/blog/using-chaos-engineering-to-demonstrate-regulatory-compliance): Chaos Engineering is a powerful tool that can help you prove that your systems are compliant with regulations and standards surrounding risk management and disaster recovery in your enterprise IT systems. - [Validating the resilience of your API gateway with Chaos Engineering](https://www.gremlin.com/blog/validating-the-resilience-of-your-api-gateway-with-chaos-engineering): API gateways are a critical component of distributed systems and cloud-native deployments. They perform many important functions including request routing, caching, user authentication, rate limiting, and metrics collection. However, this means that any failures in your API gateway can put your entire deployment at risk. How confident are you that your gateway will be resilient to common production conditions such as backend outages, poor network performance, and sudden traffic surges? - [What is a "service" in a microservices architecture?](https://www.gremlin.com/blog/what-is-a-service): The past ten years marked a significant change in how software teams build and deploy applications. We moved away from bulky, slow, monolithic applications toward lightweight, scalable, distributed service-based applications. Meanwhile, tools like Docker, Kubernetes, and other container platforms helped accelerate this process. Despite this sudden growth, a fundamental question remains: what exactly is a service, and how does it fit into a microservice architecture? - [What is Chaos Engineering? SREs and Leaders Define the Practice & Where It's Going](https://www.gremlin.com/blog/what-is-chaos-engineering-and-where-is-it-going): Chaos Engineering is a practice that is growing in implementation and interest. What is it and why are some of the most successful companies in the world adopting it? - [What is fault injection?](https://www.gremlin.com/blog/what-is-fault-injection): When reading about Chaos Engineering, you’ll likely hear the terms “fault injection” or “failure injection.” As the name suggests, fault injection is a technique for deliberately introducing stress or failure into a system in order to see how the system responds. But what exactly does this mean, and how does this relate to Chaos Engineering? In this post, we’ll look at the history of fault injection, how it’s evolved over time, and how it contributed to Chaos Engineering as we know it today. - [What is Reliability Management?](https://www.gremlin.com/blog/what-is-reliability-management): Measuring and improving the reliability of technical systems has always been challenging. As an industry, we've developed several practices to try and address reliability concerns, such as incident response, observability, and Chaos Engineering. This led SREs and service owners to measure reliability in a handful of ways: - [What is the Well-Architected Cloud Test Suite?](https://www.gremlin.com/blog/what-is-the-well-architected-cloud-test-suite): Find out the tests included in Gremlin’s Well-Architected Cloud Test Suite to make it easier than ever to verify your cloud reliability. - [What your company can learn from the Bank of England’s resilience proposal](https://www.gremlin.com/blog/what-your-company-can-learn-from-the-bank-of-englands-resilience-proposal): This article was originally published on TechCrunch. - [What's the reliability of your checkout process?](https://www.gremlin.com/blog/whats-the-reliability-of-your-checkout-process): One of the reasons companies practice Chaos Engineering is to prevent expensive outages in retail (or anywhere, for that matter) from happening in the first place. This blog post walks through a common retail outage where the checkout process fails, then covers how to use Chaos Engineering to prevent the outage from ever happening in the first place. - [What’s the ROI of reliability?](https://www.gremlin.com/blog/whats-the-roi-of-reliability): Learn how to compute the ROI of a reliability or Chaos Engineering program, including how to quantify the positive impact your efforts created for the company. - [Where to automate resilience testing in your SDLC](https://www.gremlin.com/blog/where-to-automate-resilience-testing-in-your-sdlc): When organizations begin to deploy resilience testing or Chaos Engineering, there’s a natural question: can we integrate this with our CI/CD pipeline or release automation tools? The short answer is yes. Integration is possible, but resiliency is different, so automation is a nuanced conversation. - [Why CTOs And CIOs Should Care More About The Cost Of Downtime](https://www.gremlin.com/blog/why-ctos-and-cios-should-care-more-about-the-cost-of-downtime): Originally published on Forbes.com. - [Why modern testing requires Chaos Engineering](https://www.gremlin.com/blog/why-modern-testing-requires-chaos-engineering): Chaos and Reliability Engineering techniques are quickly gaining traction as essential disciplines to building reliable applications. Many organizations have embraced Chaos Engineering over the last few years. - [Why You Need Chaos Engineering in Your Hybrid Infrastructure](https://www.gremlin.com/blog/why-you-need-chaos-engineering-in-your-hybrid-infrastructure): Originally published on DevOps.com. ## Certification - [Get Gremlin certified](https://www.gremlin.com/certification): Demonstrate your reliability expertise, increase your visibility, and advance your career with a Gremlin Enterprise Chaos Engineering certification. ## Chaos-engineering - [Chaos Engineering](https://www.gremlin.com/chaos-engineering): Chaos Engineering is a disciplined approach of identifying potential failures before they become outages. ## Chaos-engineering-measuring-benefits - [Measuring the benefits of Chaos Engineering | Gremlin](https://www.gremlin.com/chaos-engineering-measuring-benefits): A look at the benefits of chaos engineering, the challenges in tracking them, and how to start measuring. ## Chaos-monkey - [What Is Chaos Monkey? A Complete Guide for Engineers, DevOps & SREs](https://www.gremlin.com/chaos-monkey): A complete and comprehensive guide to learn about, set up, and deploy Chaos Monkey and other similar tools for creating chaos. Download the whole guide. - [Taking Chaos Monkey to the Next Level - Deploy a Spinnaker Stack](https://www.gremlin.com/chaos-monkey/advanced-developer-guide): A detailed, advanced developer guide for DevOps and SREs to get the most out of Chaos Monkey and push Chaos Engineering efforts to the next level of maturity. - [Chaos Monkey Alternatives for Creating Failure Outside AWS](https://www.gremlin.com/chaos-monkey/chaos-monkey-alternatives): Looking for a Chaos Monkey alternative? See the complete list and determine the best technology for your specific use case. - [A step-by-step guide on setting up and using Chaos Monkey with AWS. Explore specific scenarios in which Chaos Monkey may (or may not) be useful.](https://www.gremlin.com/chaos-monkey/chaos-monkey-tutorial): Chaos Monkey AWS Tutorial - Step-by-Step Guide to Create Failure - [Resources & Links For Engineers to Master Chaos Monkey](https://www.gremlin.com/chaos-monkey/for-engineers): A complete list of resources, tools, and links to learn more about Chaos Monkey, its numerous alternatives, and the Simian Army. - [Chaos Monkey at Netflix: the Origin of Chaos Engineering](https://www.gremlin.com/chaos-monkey/the-origin-of-chaos-monkey): Learn the origins and history of Chaos Monkey and see why Netflix needed to create failure within their systems to improve their resilience. - [The Simian Army and other Tools for Creating Chaos](https://www.gremlin.com/chaos-monkey/the-simian-army): The Simian Army is a suite of failure-inducing tools designed to add more capabilities beyond Chaos Monkey. Learn how they shaped the practice of Chaos Engineering. ## Community - [Tutorials](https://www.gremlin.com/community/tutorials): Prevent outages, innovate faster, and earn customer trust with Gremlin’s Reliability Management and Chaos Engineering platform. ## Customers - [Gremlin makes our customers more reliable](https://www.gremlin.com/customers): Forward-looking engineering organizations use Gremlin for their Chaos Engineering programs and to build more reliable software. - [Self-service culture of reliability](https://www.gremlin.com/customers/grubhub): In the era of DevOps, human processes are often harder than technical ones. Doug shares how Grubhub made Chaos Engineering with Gremlin universally available to their developers in order to build a culture of reliability. - [Building resiliency at a 160 year old bank](https://www.gremlin.com/customers/nab): NAB, Australia’s largest business bank and one of the ‘big four,’ kicked off its Technology Transformation program at the end of 2018 in pursuit of simplicity, agility, resilience and to stay relevant to an ever-evolving competitive landscape. - [How Ritchie Bros Creates a Culture of Reliability](https://www.gremlin.com/customers/ritchie-bros): Gremlin helps the world's largest auctioneer of commercial assets and vehicles create a seamless customer experience by helping them modernize with confidence, build an innovative engineering culture, and keep their applications available. - [How Sephora improves performance and availability](https://www.gremlin.com/customers/sephora): Gremlin helps the world’s leading prestige beauty retail brand smoothly migrate from monolithic to Kubernetes—and to pull off Black Friday and Cyber Monday without any major issues. - [Creating a Culture of Reliability at Visa Cross-Border Solutions](https://www.gremlin.com/customers/visa-cross-border-solutions): Using Gremlin, Visa Cross-Border Solutions was able to standardize resilience testing in staging to create a culture of reliability that improved the resilience and availability of services across their organization. ## Demo - [Gremlin: Proactively improve reliability](https://www.gremlin.com/demo): Downtime is expensive and damages customer trust. Gremlin finds weaknesses in your system before they cause problems. ## Docs - [Overview > Gremlin Documentation](https://www.gremlin.com/docs): Welcome to the Gremlin documentation! Getting started New to Gremlin? If you are a free trial user, see our Gremlin… - [API Reference > Getting started with the Gremlin API](https://www.gremlin.com/docs/api-reference-api-keys): Learn how to authenticate with the Gremlin API using your username and password, MFA, or API keys. - [API Reference > API reference: Classes, methods, & attributes](https://www.gremlin.com/docs/api-reference-overview): A complete reference to the Gremlin REST API, from authenticating to running experiments. Improve reliability programmatically. - [API Reference > API Reference](https://www.gremlin.com/docs/api-reference-overview-main): How to use the Gremlin REST API. - [Deploying Failure Flags on Pivotal Cloud Foundry (PCF)](https://www.gremlin.com/docs/deploying-failure-flags-on-pivotal-cloud-foundry-pcf): Learn how to use Failure Flags to run application-level reliability tests in Cloud Foundry. - [Deploying Failure Flags on the Istio service mesh via Envoy](https://www.gremlin.com/docs/deploying-failure-flags-on-the-istio-service-mesh-via-envoy): Learn how to run Chaos Engineering experiments on the Istio service mesh and Envoy proxy using Gremlin Failure Flags. - [Deploying Failure Flags on AWS ECS](https://www.gremlin.com/docs/failure-flags-ecs): This document will walk you through setting up Failure-Flags-Sidecar for your ECS Tasks. Failure-Flags-Sidecar runs… - [Running Failure Flags experiments](https://www.gremlin.com/docs/failure-flags-experiments): This document will walk you through running your first experiment using Failure Flags. Example: the HTTPHandler… - [Installing the Failure Flags SDK](https://www.gremlin.com/docs/failure-flags-installing-failure-flags-sdk): This document will walk you through adding the Failure Flags SDK to your application. Failure Flags is currently… - [Deploying Failure Flags on Kubernetes](https://www.gremlin.com/docs/failure-flags-kubernetes): This document will walk you through setting up Failure-Flags-Sidecar, a small per-process sidecar agent. Failure-Flags… - [Deploying Failure Flags on AWS Lambda](https://www.gremlin.com/docs/failure-flags-lambda): This document will walk you through setting up the Failure Flags agent for Lambda Functions. The Failure Flags agent… - [Failure Flags](https://www.gremlin.com/docs/failure-flags-overview): Gremlin Failure Flags lets you run Chaos Engineering experiments and reliability tests on serverless workloads… - [Experiments](https://www.gremlin.com/docs/fault-injection-experiments): An experiment is a method of injecting failure into a system in a simple, safe, and secure way. Learn how easy it is to run experiments in Gremlin. - [Blackhole Experiment](https://www.gremlin.com/docs/fault-injection-experiments-blackhole): The Blackhole experiment blocks inbound and outbound traffic to simulate a total network outage. - [Certificate Expiry Experiment](https://www.gremlin.com/docs/fault-injection-experiments-certificate-expiry): The Certificate Expiry experiment checks your TLS certificate chain to ensure no certificates are expiring soon. - [CPU Experiment](https://www.gremlin.com/docs/fault-injection-experiments-cpu): Test resource scalability by consuming CPU capacity on a host, container, Kubernetes resource, or service, to test systems with low compute availability. - [Disk Experiment](https://www.gremlin.com/docs/fault-injection-experiments-disk): The disk experiment writes random data to a block device to test systems under low disk conditions. - [DNS Experiment](https://www.gremlin.com/docs/fault-injection-experiments-dns): The DNS experiment blocks all outgoing traffic over the standard DNS port ( 53 ), simulating a DNS failure. - [GPU Experiment](https://www.gremlin.com/docs/fault-injection-experiments-gpu): Build more resilient AI and machine learning models, video streaming and encoding services, and simulations with Gremlin’s GPU experiment. - [IO Experiment](https://www.gremlin.com/docs/fault-injection-experiments-io): The IO experiment generates large amounts of IO requests (read, write, or both) to test disk performance and quotas. - [Latency Experiment](https://www.gremlin.com/docs/fault-injection-experiments-latency): The Latency experiment injects latency into IP packets at the transport layer, simulating slow or unstable network connections. - [Memory Experiment](https://www.gremlin.com/docs/fault-injection-experiments-memory): The Memory experiment consumes a set amount of memory (RAM) to test system stability under low-memory conditions. - [Packet Loss Experiment](https://www.gremlin.com/docs/fault-injection-experiments-packetloss): The Packet Loss experiment drops (or corrupts) a percentage of network packets to simulate unstable network conditions. - [Process Exhaustion Experiment](https://www.gremlin.com/docs/fault-injection-experiments-processexhaustion): Process Exhaustion creates new threads to consume the number of available threads on a target. Learn more in the Gremlin documentation. - [Process Killer Experiment](https://www.gremlin.com/docs/fault-injection-experiments-processkiller): The Process Killer experiment sends an IPC signal to kill, stop, or run any other signal on targeted processes. - [Shutdown Experiment](https://www.gremlin.com/docs/fault-injection-experiments-shutdown): The Shutdown experiment issues a system call to shut down or reboot the operating system on which the target is running… - [Time Travel Experiment](https://www.gremlin.com/docs/fault-injection-experiments-timetravel): The Time Travel experiment temporarily changes the system's current time for testing clock drift, TLS certificate expiry, and DST resilience. - [GameDays](https://www.gremlin.com/docs/fault-injection-gamedays): A GameDay is an organized team event to practice Chaos Engineering, test your incident response process, validate past… - [Fault Injection](https://www.gremlin.com/docs/fault-injection-overview): Welcome to Gremlin Fault Injection (FI)! Gremlin FI lets you use Gremlin’s comprehensive fault injection library to… - [Scenarios](https://www.gremlin.com/docs/fault-injection-scenarios): A Scenario is a set of Health Checks and Gremlin experiments that you can define, along with a name, description… - [Scheduling Scenarios](https://www.gremlin.com/docs/fault-injection-scenarios-scheduling-scenarios): Scenarios can be scheduled to run randomly within a timeframe. A Scenario will run at least once on the day and in the… - [Shared Scenarios](https://www.gremlin.com/docs/fault-injection-scenarios-shared-scenarios): Shared Scenarios are pre-configured Scenarios created by Gremlin users to test real-world failure modes, or to use as… - [Targets](https://www.gremlin.com/docs/fault-injection-targets): A target is any infrastructure or application resource that you can run experiments on. This can include Amazon EC… - [Configuring the Gremlin Agent](https://www.gremlin.com/docs/getting-started-agent-configuration): This documentation page shows you how to configure the Gremlin Agent. You can configure Gremlin using either environment… - [Authenticating the Gremlin Agent](https://www.gremlin.com/docs/getting-started-authentication): Before you can start using Gremlin, you need to authenticate the Agent with your Gremlin team. This documentation page… - [Enabling AWS PrivateLink](https://www.gremlin.com/docs/getting-started-aws-privatelink): Learn how to configure Gremlin for use over AWS PrivateLink. - [Compatibility](https://www.gremlin.com/docs/getting-started-compatibility): The following matrices show the operability of Gremlin on various platforms. Following the compatibility matrices is a… - [Enabling DNS collection](https://www.gremlin.com/docs/getting-started-enabling-dns-collection): Learn how to enable Gremlin's DNS collection feature. - [Additional Configuration for Helm](https://www.gremlin.com/docs/getting-started-helm-additional-configuration): Some environments require additional configuration. Review the following sections to find the best configuration for… - [Installing Gremlin on Kubernetes with Helm](https://www.gremlin.com/docs/getting-started-install-kubernetes-helm): The Gremlin Helm Chart is the easiest way to install the Gremlin Agent on Kubernetes. - [Install Gremlin on Kubernetes manually](https://www.gremlin.com/docs/getting-started-install-kubernetes-manual): This section will guide you through installing the Gremlin Agent using only YAML files. We only recommend using this… - [Install Gremlin on OpenShift 4](https://www.gremlin.com/docs/getting-started-install-openshift4): Pre-requisites Download authentication keys Gremlin requires authentication during installation. You will need to… - [Installing Gremlin on a virtual machine](https://www.gremlin.com/docs/getting-started-install-virtual-machine): General steps for deploying the Gremlin Agent to a virtual machine: Gather your credentials Install Gremlin packages… - [Installing Gremlin on Windows](https://www.gremlin.com/docs/getting-started-install-windows): General steps for deploying the Gremlin Agent on Windows: Gather your credentials Install the Gremlin agent Configure… - [Installing the Gremlin Agent](https://www.gremlin.com/docs/getting-started-installing-gremlin): In order to use Gremlin on your systems, you'll need to install the Gremlin Agent. The Gremlin Agent is an executable… - [Installing Gremlin on AWS - Configuring your VPC](https://www.gremlin.com/docs/getting-started-installing-gremlin-install-aws-vpc): Amazon Web Services (AWS) has unique networking requirements that must be implemented for Gremlin to run successfully… - [Network Tags](https://www.gremlin.com/docs/getting-started-network-tags): What are tags? Tags are basically the metadata or labels attached to an object. Each tag consists of a key and an… - [Getting Started](https://www.gremlin.com/docs/getting-started-overview): Prevent outages, innovate faster, and earn customer trust with Gremlin’s Reliability Management and Chaos Engineering platform. - [Process Collection](https://www.gremlin.com/docs/getting-started-process-collection): Gremlin can collect information about the processes running on the Linux machines where the Gremlin Agent is installed… - [Troubleshooting Gremlin on OpenShift](https://www.gremlin.com/docs/getting-started-troubleshoot-openshift): Gremlin network timeouts This issue is most often seen with timeout errors in both Chao and Gremlin logs. This usually… - [Installing Gremlin on Amazon ECS](https://www.gremlin.com/docs/installing-gremlin-on-amazon-ecs): Learn how to install Gremlin on EC2-backed Amazon Elastic Container Service (ECS) deployments. - [Installing Gremlin on GKE Autopilot](https://www.gremlin.com/docs/installing-gremlin-on-gke-autopilot): Learn how to install Gremlin onto a Google Kubernetes Engine (GKE) Autopilot cluster. - [Installing Gremlin on Pivotal Cloud Foundry (PCF)](https://www.gremlin.com/docs/installing-gremlin-on-pivotal-cloud-foundry-pcf): Learn how to deploy the Gremlin agent to Pivotal Cloud Foundry (PCF). Start detecting services and running experiments in minutes. - [Managing Kubernetes namespaces](https://www.gremlin.com/docs/managing-kubernetes-namespaces): This page explains how to grant and revoke access to Kubernetes namespaces for your Gremlin teams. - [Managing running, scheduled, and past experiments](https://www.gremlin.com/docs/managing-running-scheduled-and-past-experiments): Learn how to view and manage schedules for your Chaos Engineering experiments, Scenarios, and reliability tests. - [Command Line Interface](https://www.gremlin.com/docs/platform-command-line-interface): Gremlin Command line interface allows the user to perform commands directly from the host. The impact of the attack will… - [Managing the Gremlin Agent](https://www.gremlin.com/docs/platform-gremlin-daemon-and-agent): The Gremlin Agent is an executable binary installed on a host operating system, container runtime, or Kubernetes cluster… - [Gremlin Private Edition](https://www.gremlin.com/docs/platform-gremlin-private-edition): Learn about Gremlin Private Edition, an isolated Gremlin instance hosted entirely in your network. - [Health Checks](https://www.gremlin.com/docs/platform-health-checks): A Health Check checks the state of systems before, during, and after an experiment, Scenario, or reliability test. They… - [Private Network Integration Agent](https://www.gremlin.com/docs/platform-integration-agent): Private Network Integrations lets you use Gremlin's Health Checks and Webhooks featires without exposing your… - [Integrations](https://www.gremlin.com/docs/platform-integrations): Company Integrations Company level integrations allow you to create integrations for use across your entire Gremlin… - [Custom Load Generator](https://www.gremlin.com/docs/platform-integrations-custom-load-generator): Gremlin requires the following for a custom Load Generator integration: Name URL for the authentication step… - [Datadog Integration](https://www.gremlin.com/docs/platform-integrations-datadog): Synchronize test runs between your Gremlin and Datadog accounts. - [Grafana Cloud k6](https://www.gremlin.com/docs/platform-integrations-grafana-cloud-k6): For Grafana Cloud k6, Gremlin automatically sets the base URL. All you need to do is add the API Key header to be used… - [Jira](https://www.gremlin.com/docs/platform-integrations-jira): With Gremlin's Jira integration, you can create and track Jira issues directly from Services, Scenario Runs, and GameDay… - [Slack](https://www.gremlin.com/docs/platform-integrations-slack): Slack is a communications and collaboration platform to help teams get together and get things done. If you already use… - [Webhooks](https://www.gremlin.com/docs/platform-integrations-webhooks): Overview Webhooks let you call custom HTTP endpoints when running experiments. Using webhooks, you can easily send the… - [Platform](https://www.gremlin.com/docs/platform-overview): Learn how to manage the Gremlin platform: adding users and teams, updating agents, configuring RBAC, and more. - [Reliability Intelligence](https://www.gremlin.com/docs/platform-reliability-intelligence): Reliability Intelligence analyzes your Gremlin environment and provides recommendations on how to make your services more reliable. - [Reports](https://www.gremlin.com/docs/platform-reports): Learn how to use Gremlin’s powerful reporting tools to review, track, and manage your organization’s reliability. - [Restricting Testing Times](https://www.gremlin.com/docs/platform-restricted-time-windows): Restricted Time Windows are times during which all tests (Chaos Engineering experiments, Scenarios, and reliability… - [Configuring Role Based Access Control (RBAC)](https://www.gremlin.com/docs/platform-role-based-access-control): Gremlin provides role based access control functionality that grants specific privileges to a role. - [Updating Gremlin](https://www.gremlin.com/docs/platform-updating-gremlin): It's important to keep Gremlin up to date, in order to take advantage of new features and important bug fixes. - [User Authentication via SAML and Okta](https://www.gremlin.com/docs/platform-user-authentication): Gremlin supports several different authentication systems, including password-based (default), Google, OAuth , and… - [Authenticating Users with Microsoft Entra ID (Azure Active Directory) via SAML](https://www.gremlin.com/docs/platform-user-authentication-entra-id-azure-ad-saml): Learn how to authenticate users to Gremlin by using Microsoft Entra ID (previously Azure Active Directory) and SAML. - [Managing Users and Teams](https://www.gremlin.com/docs/platform-users): To view, invite, and manage Gremlin users and their privileges within your company, select "Company Settings" from the… - [Quick Start Guides > Quick Start Guides](https://www.gremlin.com/docs/quick-start-guides-overview): Use these short guides to quickly start using Gremlin. - [Detected Risks](https://www.gremlin.com/docs/reliability-management-detected-risks): Detected Risks are high-priority reliability concerns that Gremlin automatically identified in your environment. These… - [Reliability Management](https://www.gremlin.com/docs/reliability-management-overview): Prevent outages, innovate faster, and earn customer trust with Gremlin’s Reliability Management and Chaos Engineering platform. - [Quick Start Guides > Reliability Management (RM) Quick Start Guide](https://www.gremlin.com/docs/reliability-management-quick-start-guide): Welcome to the Gremlin Reliability Management (RM) quick start guide! This guide will walk you through installing… - [Reliability Score](https://www.gremlin.com/docs/reliability-management-reliability-score): The Reliability Score helps set a standard view of reliability across all teams and services in your organization. Once… - [Reliability Tests](https://www.gremlin.com/docs/reliability-management-reliability-tests): Reliability tests test a specific behavior of your service, such as autoscaling CPU and memory, zone and host redundancy… - [Services and Dependencies](https://www.gremlin.com/docs/reliability-management-services): A service is a discrete unit of functionality provided by one or more systems in your environment. For example, a web… - [Test Suites](https://www.gremlin.com/docs/reliability-management-test-suites): A Test Suite is a group of reliability tests that get applied to each service in a Gremlin team. Test Suites let you… - [Resources > Glossary](https://www.gremlin.com/docs/resources-glossary): Here is a list of common terms and definitions related to the practice of Chaos Engineering. Abort Conditions System… - [Resources > Resources](https://www.gremlin.com/docs/resources-overview): Gremlin blog Our blog focuses on Chaos Engineering insights and education, product news, and shares our own internal… - [Security > Container security](https://www.gremlin.com/docs/security-containers): Gremlin containers run as root When Gremlin runs within a container, gremlin processes run as root . This is because… - [Security > Security](https://www.gremlin.com/docs/security-overview): To find an overview of Gremlin’s security practices, check out gremlin.com/security . Gremlin makes it easy to find… ## Ecommerce-cost-of-downtime - [Cost of Downtime for Top US eCommerce Sites](https://www.gremlin.com/ecommerce-cost-of-downtime): We used online revenue metrics to calculate just how much each second of downtime costs the largest and most well-known ecommerce retailers. ## Gameday - [Gameday](https://www.gremlin.com/gameday): Increase your system’s reliability with safe, secure, and simple GameDays. ## Kubernetes-chaos-engineering - [Getting started with Chaos Engineering on Kubernetes](https://www.gremlin.com/kubernetes-chaos-engineering): Everything you need to safely, securely, and simply run Chaos Engineering experiments on Kubernetes. ## Leadership - [About Gremlin](https://www.gremlin.com/leadership): We've lived and breathed incidents, on-call, and Chaos Engineering for a decade. We've served as 'Call Leaders' at Amazon and Netflix, resposible for fixing global outages. We've employed Chaos Engineering to harden and prepare our services for internet scale. We've built this tooling before, and engineers loved it. We hope you'll love it too! ## Media - [Media Coverage for Gremlin](https://www.gremlin.com/media): News, company info, and media resources ## Product - [Chaos Engineering | Gremlin](https://www.gremlin.com/product/chaos-engineering): Gremlin enables every organization to conduct safe and secure chaos engineering experiments. Find reliability risks in any environment—before they impact users. - [Reliability Management | Gremlin](https://www.gremlin.com/product/reliability-management): Rapidly start and scale world-class reliability practices organization-wide. Find and fix known reliability risks with standardized reliability testing, scoring and automation - [Reliability and Chaos Engineering Platform | Gremlin](https://www.gremlin.com/product): Reduce downtime, improve resilience, and protect revenue. Gremlin helps engineering teams find and fix reliability risks before they become expensive outages. ## Reliability-tracker-download - [Navigating the Reliability Minefield: Finding and Fixing Your Hidden Reliability Risks](https://www.gremlin.com/reliability-tracker-download): Find out how you can create a reliability map of your systems using a spreadsheet that you can use to align teams around reliability risks, prioritize fixes, and track reliability efforts. ## Security - [Security Practices](https://www.gremlin.com/security/practices): Downtime is expensive and damages customer trust. Gremlin's Failure as a Service finds weaknesses in your system before they cause problems. - [Security](https://www.gremlin.com/security): Prevent outages, innovate faster, and earn customer trust with Gremlin’s Reliability Management and Chaos Engineering platform. ## Slack - [Slack](https://www.gremlin.com/slack): Join the Gremlin User Community to chat with other engineers, SREs, and reliability experts. ## State-of-chaos-engineering - [State of Chaos Engineering 2021](https://www.gremlin.com/state-of-chaos-engineering/2021): Understand the evolution of Chaos Engineering. How are teams using Chaos Engineering to improve reliability across their systems? Dive into the results of the inaugural State of Chaos Engineering Report to find out. ## Team - [Careers](https://www.gremlin.com/team): We've lived and breathed incidents, on-call, and Chaos Engineering for a decade. We've served as 'Call Leaders' at Amazon and Netflix, resposible for fixing global outages. We've employed Chaos Engineering to harden and prepare our services for internet scale. We've built this tooling before, and engineers loved it. We hope you'll love it too! ## Terms - [Terms of Service](https://www.gremlin.com/terms): Downtime is expensive and damages customer trust. Gremlin's Failure as a Service finds weaknesses in your system before they cause problems. ## Trial - [Get immediate free access to Gremlin for 30 Days](https://www.gremlin.com/trial): Get immediate access to Gremlin ## Dora - [Gremlin for DORA](https://www.gremlin.com/dora): Get access to Gremlin's DORA compliance solution ## Kubernetes - [The Ultimate Guide to Kubernetes High Availability](https://www.gremlin.com/kubernetes): Find out how to deliver highly available, resilient, and reliable Kubernetes deployments with Kubernetes risk monitoring and resilience testing. ## Kubernetes-cluster-reliability-metrics - [How to measure Kubernetes cluster reliability](https://www.gremlin.com/kubernetes-cluster-reliability-metrics): Learn how to use resilience testing and Kubernetes reliability risk monitoring to measure and report the reliability of your Kubernetes clusters. ## Monitor-kubernetes-reliability-risks - [How to monitor Kubernetes reliability risks](https://www.gremlin.com/monitor-kubernetes-reliability-risks): Learn how to use automated Kubernetes risk monitoring to detected reliability risks before they cause outages. ## Kubernetes-cluster-resilience-testing - [Resilience testing for Kubernetes clusters](https://www.gremlin.com/kubernetes-cluster-resilience-testing): Learn how to use Fault Injection testing to verify resilience to known Kubernetes failures—and to uncover unknown reliability risks. ## About - [About Gremlin](https://www.gremlin.com/about): Gremlin helps engineering teams proactively manage reliability at scale. Our platform makes it easy to uncover risks, run automated tests, and validate disaster recovery, so you can stay ahead of outages and deliver a better customer experience. ## Solutions - [Gremlin on AWS](https://www.gremlin.com/solutions/aws): Modernize reliability on AWS - [Gremlin](https://www.gremlin.com/solutions/build-a-reliability-program): Build, standardize, and automate world-class reliability programs at scale. Find and fix known reliability risks with standardized reliability testing, scoring, and automation tools. - [Gremlin](https://www.gremlin.com/solutions/cloud-migrations): Migrate to the cloud with confidence by finding and fixing reliability risks before, during, and after go-live. - [Gremlin](https://www.gremlin.com/solutions/find-outages-before-they-happen): Most teams jump into action after users feel the pain. With Gremlin, you can root out the common causes of incidents and outages before they impact users. - [Financial Services](https://www.gremlin.com/solutions/finserve): Build resilience. Prove reliability. - [Improve AI reliability and availability](https://www.gremlin.com/solutions/improve-ai-reliability): Gremlin helps you prevent outages before they happen, creating more reliable AI services and AI-enabled applications. - [Gremlin](https://www.gremlin.com/solutions/it-governance-and-compliance): Gremlin offers a multi-faceted approach that both enhances your organizational resilience and provides concrete, auditable evidence to back it up. - [Gremlin](https://www.gremlin.com/solutions/recreate-incidents-and-outages): Gremlin enables every organization to recreate incidents and outages with safe and secure Chaos Engineering experiments. - [Retail](https://www.gremlin.com/solutions/retail): Reliability that drives revenue. - [Saas & Technology](https://www.gremlin.com/solutions/saas): Improve reliability without slowing down. - [Gremlin](https://www.gremlin.com/solutions/shift-left-reliability-testing): Catch reliability risks before they make it to production. With Gremlin, you can integrate reliability testing early in the software development lifecycle, mitigating risks and enhancing user experience from day one. - [Gremlin](https://www.gremlin.com/solutions/tune-observability): With Gremlin’s fault injection tools, you can fine-tune your observability tools to focus on the metrics that matter, eliminate noisy and irrelevant alerts, and ensure timely detection and resolution of real issues. - [Gremlin](https://www.gremlin.com/solutions/validate-runbooks-and-dr): Ensure your organization has effective runbooks and disaster recovery plans that minimize downtime by testing them with Gremlin’s fault injection and reliability management platform. ## Technologies - [Dependency Discovery](https://www.gremlin.com/technologies/dependency-discovery): Discover, track, and test the reliability of your dependencies from a single pane of glass with Gremlin. - [Detected Risks](https://www.gremlin.com/technologies/detected-risks): Gremlin automatically finds potential reliability risks in your environment, without running a single test. - [Failure Flags](https://www.gremlin.com/technologies/failure-flags): Test the resiliency of applications and serverless functions with Failure Flags, Gremlin's safe and secure application-layer fault injection feature—no infrastructure access required. - [Fault Injection](https://www.gremlin.com/technologies/fault-injection): Catch reliability risks before they make it to production. With Gremlin Fault Injection, you can integrate reliability testing early in the software development lifecycle, mitigating risks and enhancing user experience from day one. - [Gremlin Private Edition](https://www.gremlin.com/technologies/gremlin-private-edition): Gremlin Private Edition is a private, secure, self-hosted Gremlin instance that runs entirely within your network. - [Reliability Scoring](https://www.gremlin.com/technologies/reliability-scoring): Get a comprehensive, objective measurement of your services's reliability in minutes with Gremlin. ## Whitepapers - [https://cdn.prod.website-files.com/64a5291e7847ac04fe1531ad/6750c983aed8c384d4eb22ec_FCA-Operational-Resilience-Gremlin-Datasheet.pdf](Compliance for FCA Operational Resilience (PS21/3)): How Gremlin helps you comply with FCA Operational Resilience regulations - [https://cdn.prod.website-files.com/64a5291e7847ac04fe1531ad/6750c983bd2484044fe92abe_APRA%20CPS%20230%20Gremlin%20Datasheet.pdf](Compliance for APRA Prudential Standard CPS 230): How Gremlin helps you comply with and verify APRA CPS 230 regulations - [https://cdn.prod.website-files.com/64a5291e7847ac04fe1531ad/6644f1d3fca033de549e271d_Gremlin%20for%20DORA-202404.pdf](Gremlin for DORA Governance and Compliance) - [https://cdn.prod.website-files.com/64a5291e7847ac04fe1531ad/663560aab65f9691fada9bd7_Closing%20the%20AWS%20Reliability%20Gap%20-%20Gremlin.pdf](Closing the AWS Reliability Gap) - [https://cdn.prod.website-files.com/64a5291e7847ac04fe1531ad/65b3f12e925d641fc6ddc5f4_Critical%20Kubernetes%20Reliability%20Risks.pdf](Critical Kubernetes Reliability Risks) - [https://cdn.prod.website-files.com/64a5291e7847ac04fe1531ad/65b3f0b1737c7b538ca680cd_2024%20Chaos%20Engineering%20Enterprise%20Buyers%20Guide.pdf](Chaos Engineering Enterprise Buyer's Guide)
Version History
Version 13/20/2026, 8:01:40 AMvalid
100479 bytes
Categories
blognewsecommercee-commercedocumentationdocsentertainmenteducationtechnologybusinesshealthtravel
Visit Website
Explore the original website and see their AI training policy in action.
Visit gremlin.comContent Types
articlespagesapidocumentationtutorialsguides
Recent Access
No recent access
API Access
Canonical URL:
https://llmscentral.com/gremlin.com/llms.txt
API Endpoint:
/api/llms?domain=gremlin.com