# Gremlin Blog Prevent outages, innovate faster, and earn customer trust with Gremlin's Reliability Management and Chaos Engineering platform. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to verify your Azure Application Gateway is zone-redundant DevFeed: [How to verify your Azure Application Gateway is zone-redundant]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Azure](), [Availability](), [Cloud](), [web applications](), [Command-line interface](), [Shared Responsibility Model]() Tags: [availability](), [azure](), [cli](), [cloud](), [features](), [high-availability](), [how-to](), [infrastructure](), [post](), [shared-responsibility](), [web-applications]() ### AI overview This how-to article explains availability-zone redundancy for Azure Application Gateway. It describes the redundancy model, the shared responsibility boundary, and how to verify whether a gateway is zone-redundant or zonal using Azure CLI and Resource Graph. It also cautions that a redundant gateway does not by itself make the services behind it redundant. ### Source excerpt This post explains what zone redundancy means for Application Gateway, how to confirm whether a given gateway is zone-redundant or zonal using the Azure CLI and Resource Graph, and why a gateway surviving a zone failure doesn't mean the services calling through it will. ## Managing Kubernetes node drains with Pod Disruption Budgets DevFeed: [Managing Kubernetes node drains with Pod Disruption Budgets]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-08-27T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Kubernetes](), [web applications](), [Latency](), [nginx]() Tags: [deployment](), [features](), [how-to](), [kubernetes](), [latency](), [learn](), [nginx](), [web]() ### AI overview This article explains how Kubernetes PodDisruptionBudgets protect application availability during voluntary disruptions such as node drains, autoscaler consolidation, and pod migration. It describes the risks of missing PDB definitions, explains how PDBs limit simultaneous pod unavailability, and outlines how to identify deployments without them and test their behavior. ### Source excerpt A missing PodDisruptionBudget lets a routine node drain take your service offline. Learn how to set minAvailable, find gaps, and test that your PDB holds. ## Safer Kubernetes rollouts with minReadySeconds DevFeed: [Safer Kubernetes rollouts with minReadySeconds]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-08-20T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Kubernetes](), [Availability](), [Deployment]() Tags: [availability](), [deployment](), [kubernetes](), [load-balancer]() ### AI overview This article explains how Kubernetes minReadySeconds makes newly created pods remain Ready for a defined period before rollout controllers remove the pods they replace. It describes how the setting improves rolling-update safety, supports pod disruption budgets, and allows time for external load balancers to register new backends. ### Source excerpt minReadySeconds makes new pods prove they can stay ready before a rollout moves on. Learn what it controls, how to set it, and how to find workloads missing it. ## Optimizing Kubernetes pods for reliability with topology spread constraints DevFeed: [Optimizing Kubernetes pods for reliability with topology spread constraints]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-08-13T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Kubernetes](), [Availability]() Tags: [availability](), [blog](), [how-to](), [kubernetes](), [manifest]() ### AI overview This blog explains how Kubernetes topology spread constraints distribute pods across failure domains such as availability zones, regions, and nodes. It covers their reliability benefits, configuration through spec.topologySpreadConstraints, and the main constraint fields and behaviors. ### Source excerpt Topology spread constraints let you determine how Kubernetes spreads pod replicas across failure domains, such as availability zones and regions. This blog explains how they work, how to configure them, and how to scan for missing constraints. ## What your AI SRE can't see (and what you can do about it) DevFeed: [What your AI SRE can't see (and what you can do about it)]() Original publisher: [Read original article]() Author: Ryan Detwiller Published: 2026-08-06T00:00:00Z Content type: opinion Language: en Sources: [Gremlin Blog]() Topics: [Artificial Intelligence](), [SRE](), [incident](), [Availability](), [telemetry](), [Latency](), [Memory Leaks](), [Deployment]() Tags: [ai](), [availability](), [config](), [dependency](), [deployment](), [latency](), [load-balancer](), [memory](), [outage](), [outages](), [sre]() ### AI overview The article argues that AI SRE tools can speed up triage, reduce alert fatigue, and automate frontline incident response, but they do not solve all reliability problems. It identifies gaps including acting only after failures begin and being unable to predict sudden failures without detectable warning signals. ### Source excerpt AI SRE is having a moment. And let's be honest: faster triage, less alert fatigue, and automated frontline response are wins for understaffed teams. But there are still five gaps in their capabilities, and if you don't understand those gaps before you deploy, you'll find out during an outage. ## Managing slow container starts with Kubernetes readiness probes DevFeed: [Managing slow container starts with Kubernetes readiness probes]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Kubernetes](), [App](), [Database](), [Network]() Tags: [blog](), [how-to](), [kubernetes](), [learn]() ### AI overview This article explains how Kubernetes readiness probes prevent slow-starting pods from receiving live traffic before they are prepared. It describes when a pod is considered ready and outlines configuration considerations for applications that need setup time. ### Source excerpt Pods without readiness probes are like engineers without coffee. Learn how readiness probes work, why they're important, and how to configure them correctly. ## The Gremlin app for Dynatrace: resilience testing and reliability scoring, built on the observability you already trust DevFeed: [The Gremlin app for Dynatrace: resilience testing and reliability scoring, built on the observability you already trust]() Original publisher: [Read original article]() Author: Ryan Detwiller Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Resilience](), [dynatrace](), [observability](), [Instrumentation](), [distributed-systems]() Tags: [announcements](), [distributed-systems](), [dynatrace](), [engineering](), [gremlin](), [incident](), [instrumentation](), [metrics](), [observability](), [real-time](), [resilience](), [safety](), [systems](), [testing](), [uptime]() ### AI overview The Gremlin app for Dynatrace adds resilience testing and reliability scoring to Dynatrace workflows. Teams can run reliability tests, observe their impact in real time, and track service-level reliability scores using existing Dynatrace metrics, alerts, instrumentation, and health checks. ### Source excerpt With the Gremlin app for Dyantrace, you get resilience testing and reliability scoring built on the observability you already trust. ## Eliminate Reliability Blind Spots in AWS, Azure, and GCP DevFeed: [Eliminate Reliability Blind Spots in AWS, Azure, and GCP]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-07-14T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Cloud](), [Kubernetes](), [Resilience](), [Amazon Web Services](), [Azure](), [Chaos Engineering]() Tags: [availability](), [aws](), [azure](), [containers](), [deployment](), [experimentation](), [features](), [gcp](), [gremlin](), [kubernetes](), [orchestration](), [outages](), [resilience](), [uptime]() ### AI overview Gremlin's expanded Detected Risks feature automatically identifies high-priority reliability risks across AWS, Azure, GCP, and Kubernetes environments. It is designed to reveal issues such as misconfigured deployments, crash-looping containers, missing readiness probes, and poor pod distribution before they cause outages. ### Source excerpt Discover reliability risks without running a single test. See how Gremlin identifies high-priority reliability risks across AWS, Azure, and GCP to prevent outages. ## Creating an agentic feedback loop with reliability guardrails DevFeed: [Creating an agentic feedback loop with reliability guardrails]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2026-06-25T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [AI Development](), [AI-assisted coding](), [Chaos Engineering](), [Resilience](), [CI/CD](), [Code review]() Tags: [agentic-ai](), [ai](), [ai-for-code](), [chaos-engineering](), [ci-cd](), [code-generation](), [resilience](), [testing]() ### AI overview The article explains how reliability guardrails and resilience testing can create an agentic feedback loop for AI coding. It argues that agentic code review and QA alone may miss production failures, so fault injection and Chaos Engineering can validate system behavior under realistic failures and provide data that improves AI-generated code. It also discusses using resilience tests as an automated CI/CD gate. ### Source excerpt Reliability guardrails are essential for ensuring resilience with AI development, but they can also be used to create a feedback loop for AI context. ## Announcing no-code application fault injection DevFeed: [Announcing no-code application fault injection]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-06-02T00:00:00Z Content type: release Language: en Sources: [Gremlin Blog]() Topics: [Failure Flags](), [Serverless](), [Chaos Engineering](), [Testing](), [Availability](), [Latency](), [observability]() Tags: [availability](), [failure-flags](), [gremlin](), [health-checks](), [infrastructure](), [latency](), [no-code](), [observability](), [performance](), [serverless](), [testing](), [uptime]() ### AI overview Gremlin announces Failure Flags by proxy, a no-code application fault injection solution for serverless and managed applications. The sidecar proxy enables reliability tests such as simulating outages, adding latency, and generating exceptions without code changes. Intelligent Health Checks automatically monitor network throughput, latency, and error rate during tests. ### Source excerpt Gremlin announces Failure Flags by proxy, a no-code application fault injection solution for serverless and managed applications. Learn more in our latest blog post. ## Why agentic AI development needs reliability guardrails DevFeed: [Why agentic AI development needs reliability guardrails]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2026-05-15T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [agentic-coding](), [AI-assisted coding](), [Resilience](), [Chaos Engineering](), [systems](), [Latency](), [Database]() Tags: [agentic](), [agentic-ai](), [agentic-coding](), [ai](), [ai-for-code](), [database](), [latency](), [resilience](), [systems](), [testing]() ### AI overview Agentic AI is accelerating code generation and deployment, but the resulting increase in code volume and reported issue rates raises reliability risks. The article argues for scalable reliability guardrails and fault-injection testing to verify resilience and reduce the risk of outage-causing failures. ### Source excerpt Companies are moving faster than ever with agentic AI, but that means more risks. Without reliability guardrails, they risk costly outages. ## The hidden reliability risks in your agentic AI workflows DevFeed: [The hidden reliability risks in your agentic AI workflows]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Artificial Intelligence](), [distributed-systems](), [Latency](), [Network](), [Large Language Model](), [Low Latency](), [Retrieval Augmented Generation (RAG)](), [systems](), [Orchestration](), [AWS Transform]() Tags: [agentic-ai](), [ai](), [complexity](), [dependency](), [llm](), [network](), [orchestration](), [outages](), [production](), [rag](), [systems](), [testing](), [workflows]() ### AI overview This article examines reliability risks in agentic AI workflows, focusing on unstable network interactions, non-deterministic behavior, and the complexity of third-party dependencies. It explains how latency, outages, retrieval-augmented generation systems, and multi-agent orchestration can create cascading failures, and advocates proactive reliability testing. ### Source excerpt Prevent AI outages before they impact production. Learn how to discover and mitigate reliability risks in agentic AI systems like network stability, non-deterministic behavior, and third-party dependencies. ## How Gremlin makes disaster recovery testing easier and faster DevFeed: [How Gremlin makes disaster recovery testing easier and faster]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2026-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Disaster Recovery](), [Resilience](), [Testing](), [Cloud]() Tags: [backup](), [cloud](), [disaster-recovery](), [failover](), [gremlin](), [resilience](), [testing](), [use-cases]() ### AI overview The article explains how Gremlin's Disaster Recovery Testing helps teams test disaster recovery plans by simulating failures such as zone evacuations, region failovers, and cloud-provider outages. It recommends establishing service baselines with test suites, running tests regularly, and repeating them to verify fixes. ### Source excerpt Gremlin's Disaster Recovery Testing makes it easy to run zone evacuations, region failovers, and more for a fraction of the lift of traditional disaster recovery testing. ## Announcing Disaster Recovery Testing DevFeed: [Announcing Disaster Recovery Testing]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-02-03T00:00:00Z Content type: release Language: en Sources: [Gremlin Blog]() Topics: [Disaster Recovery](), [Testing](), [Incident response](), [Resilience](), [Availability](), [Cloud](), [datacenter](), [Amazon Web Services](), [Azure]() Tags: [announcements](), [availability](), [aws](), [azure](), [disaster-recovery](), [failover](), [gremlin](), [health-checks](), [incident-response](), [infrastructure](), [metrics](), [resilience](), [systems](), [testing]() ### AI overview Gremlin announces Disaster Recovery Testing, a feature for running organization-wide zone, region, and datacenter-scale experiments. It helps teams validate failover, disaster recovery, and incident response processes, with health checks that can automatically halt tests when key metrics exceed defined SLA limits. ### Source excerpt Gremlin announces Disaster Recovery Testing for validating region failover processes, disaster recovery plans, incident response procedures, and more. ## Reliability Resolutions: How to build effective reliability programs that won't fade away DevFeed: [Reliability Resolutions: How to build effective reliability programs that won't fade away]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2026-01-21T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Chaos Engineering](), [Availability](), [systems](), [data]() Tags: [availability](), [chaos-engineering](), [data](), [engineering](), [reliability-management](), [systems](), [testing](), [uptime]() ### AI overview This article explains how to build reliability and Chaos Engineering programs that produce lasting results. It recommends aligning reliability work with company goals, assigning ownership, creating repeatable processes, identifying data gaps, and testing specific failure modes on critical systems. Progress can be demonstrated through evidence such as validated failover and achievement of uptime targets. ### Source excerpt We're already almost through January. How are your reliability resolutions faring? Check out these key questions to help you follow-through and build an effective reliability program. ## How to test application resiliency by simulating the Cloudflare December 2025 outage DevFeed: [How to test application resiliency by simulating the Cloudflare December 2025 outage]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-12-19T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Failure Flags](), [Resilience](), [incident](), [Chaos Engineering](), [SDKs](), [JavaScript](), [Node.js](), [Python](), [Kubernetes](), [AWS Lambda](), [Azure]() Tags: [2025](), [after-the-retrospective](), [applications](), [aws](), [aws-lambda](), [azure](), [c-sharp](), [cloud](), [cloudflare](), [code](), [failure-flags](), [gremlin](), [how-to](), [http](), [incident](), [internet-traffic](), [javascript](), [kubernetes](), [node-js](), [outage](), [python]() ### AI overview This tutorial explains how to use Gremlin Failure Flags to simulate HTTP 500 errors associated with the December 2025 Cloudflare outage. It describes application-layer fault injection, the distinction from network-layer experiments, and supported deployment environments and SDK languages. ### Source excerpt Use Gremlin Failure Flags to safely simulate 500 error codes and test resiliency to outages, like the December 5th Cloudflare incident. ## Gremlin Release Roundup 2025: Reliability across AI, on-prem, and applications DevFeed: [Gremlin Release Roundup 2025: Reliability across AI, on-prem, and applications]() Original publisher: [Read original article]() Author: Andre Newman Published: 2025-12-15T00:00:00Z Content type: release Language: en Sources: [Gremlin Blog]() Topics: [on-prem](), [Failure Flags](), [experiments](), [Artificial Intelligence](), [MCP Server](), [telemetry](), [SRE]() Tags: [2025](), [ai](), [analysis](), [experiments](), [failure-flags](), [features](), [gremlin](), [mcp](), [mcp-server](), [no-code](), [on-prem](), [outages](), [release](), [releases](), [sre](), [telemetry]() ### AI overview Gremlin's 2025 release roundup describes improvements aimed at preventing outages and making reliability testing easier. Highlights include Reliability Intelligence for analyzing failures and recommending remediations, a Gremlin MCP server for querying environments through an LLM, new experiments and Failure Flags capabilities, expanded platform support, streamlined onboarding, and web UI refinements. ### Source excerpt This year's release roundup covers our new on-prem offering, new Failure Flags features, intelligent analysis of failed experiments, and much more. ## How to use Gremlin's Reliability Report DevFeed: [How to use Gremlin's Reliability Report]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-12-12T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [dashboards](), [monitor](), [systems](), [Cloud](), [Kubernetes](), [configuration]() Tags: [blog](), [cloud](), [configuration](), [gremlin](), [how-to](), [kubernetes](), [leadership](), [monitor](), [organizational](), [reliability-management]() ### AI overview Gremlin's Reliability Report provides organization-wide visibility into system reliability through reliability scores, detected risks, test-run counts, and service-level impacts. The article explains the report's dashboard sections, including six-month reliability trends and automatically detected Kubernetes and cloud risks, and describes how leadership can use the information to monitor and improve reliability. ### Source excerpt Find out how our Reliability Report gives you visibility into your system's reliability--and how Gremlin uses it to improve reliability. ## Gremlin's unofficial reliability track for Gartner IOCS 2025 DevFeed: [Gremlin's unofficial reliability track for Gartner IOCS 2025]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-12-01T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [SRE](), [incident](), [Critical Infrastructure](), [AI Agent](), [genai]() Tags: [2025](), [agentic-ai](), [analysts](), [critical-infrastructure](), [gartner](), [incident](), [site-reliability](), [talks](), [team-topologies]() ### AI overview Gremlin presents an unofficial reliability-focused track for Gartner IOCS 2025, highlighting sessions on software-update risks, critical dependencies, SRE team structures, and the future of reliability in an AI agent world. ### Source excerpt Check out the Gremlin-curated unofficial track of reliability talks at Gartner IOCS 2025. ## Reliability lessons from the 2025 Cloudflare outage DevFeed: [Reliability lessons from the 2025 Cloudflare outage]() Original publisher: [Read original article]() Author: Andre Newman Published: 2025-11-20T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Cloudflare](), [Bot Management](), [configuration](), [Chaos Engineering](), [Post Mortem](), [Network](), [Workers]() Tags: [2025](), [after-the-retrospective](), [bot-management](), [chaos-engineering](), [cloudflare](), [configuration](), [engineering](), [http](), [internet](), [management](), [outage](), [outages](), [post-mortem](), [workers]() ### AI overview The article examines the November 2025 Cloudflare outage, explaining how an oversized Bot Management configuration caused HTTP 5XX errors and cascading failures across dependent services. It highlights configuration propagation, service dependencies, and chaos engineering as reliability considerations. ### Source excerpt In November 2025, a misconfigured Cloudflare service led to a partial outage. Learn what happened, and what you can do to reduce the impact of similar outages. ## Reliability lessons from the 2025 Microsoft Azure Front Door outage DevFeed: [Reliability lessons from the 2025 Microsoft Azure Front Door outage]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-11-17T00:00:00Z Content type: opinion Language: en Sources: [Gremlin Blog]() Topics: [Azure](), [Microsoft](), [Cloud](), [cloud-infrastructure]() Tags: [2025](), [after-the-retrospective](), [azure](), [backup](), [best-practices](), [cloud](), [infrastructure](), [microsoft](), [outage](), [outages](), [recovery](), [uptime](), [xbox]() ### AI overview This article examines reliability lessons from the October 2025 global outage affecting Microsoft Azure Front Door, Azure Content Delivery Network, and related Microsoft services. It emphasizes customer responsibility for uptime, redundancy, tested failover, and active-active infrastructure. ### Source excerpt In October 2025, Microsoft Azure Front Door and Content Delivery Network suffered a global outage. Find out what your team can do to minimize the impact of similar outages in the future. ## Gremlin's unofficial Microsoft Ignite 2025 reliability track DevFeed: [Gremlin's unofficial Microsoft Ignite 2025 reliability track]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-11-12T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Azure](), [Microsoft](), [Resilience](), [Cloud](), [configuration](), [autoscaling](), [Replication](), [Artificial Intelligence]() Tags: [2025](), [ai](), [autoscaling](), [azure](), [cloud](), [cloud-native](), [conference](), [configuration](), [gremlin](), [industry](), [microsoft](), [recovery](), [replication](), [resilience](), [secure-by-default](), [shared-responsibility](), [storage]() ### AI overview Gremlin's unofficial Microsoft Ignite 2025 reliability track curates conference sessions about building resilient systems with Microsoft and Azure tools. The sessions cover reliability assessment and configuration, autoscaling and replication, failure simulation, recovery orchestration, shared responsibility, and secure backup practices for cloud and AI-ready applications. ### Source excerpt Check out the Gremlin-curated unofficial track of reliability talks at Microsoft Ignite 2025. ## Improve Kubernetes reliability faster with Gremlin and Dynatrace DevFeed: [Improve Kubernetes reliability faster with Gremlin and Dynatrace]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-11-10T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Kubernetes](), [dynatrace](), [observability](), [Chaos Engineering](), [ai observability]() Tags: [ai](), [announcements](), [cloud-native](), [dynatrace](), [gremlin](), [integration](), [kubernetes](), [observability](), [testing]() ### AI overview The article presents a strategic integration between Gremlin and Dynatrace that automatically discovers Kubernetes services configured in Dynatrace, making fault-injection testing faster to set up. It explains how health checks use observability metrics such as error rates and latency to evaluate experiments, validate monitoring and alerting, and improve reliability across cloud-native architectures. ### Source excerpt It's easier than ever to start testing Kubernetes with Dynatrace and Gremlin. The new strategic integration automatically discovers objects to make testing set up simple and fast. ## Reliability lessons from the 2025 AWS DynamoDB outage DevFeed: [Reliability lessons from the 2025 AWS DynamoDB outage]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-11-07T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Amazon DynamoDB](), [Amazon Web Services](), [Complex Systems](), [systems](), [Cloud]() Tags: [2025](), [amazon-dynamodb](), [applications](), [aws](), [cloud](), [industry](), [outage](), [outages](), [systems]() ### AI overview The article examines reliability lessons from the October 2025 AWS DynamoDB outage in US-EAST-1, which began with a DNS issue and was followed by an Amazon EC2 outage. It recommends mapping service dependencies, testing how applications behave when dependencies are unavailable, and distinguishing critical from non-critical dependencies. ### Source excerpt In October 2025, Amazon DynamoDB had a massive outage that took down hundreds of systems. Find out what your team can do to minimize the impact of similar outages in the future. [Next page]()