--- title: Beyond pass or fail: The new era of chaos engineering description: Krkn, an open source chaos engineering tool, is moving beyond binary pass/fail outcomes toward detailed resilience telemetry. Its beta Resiliency Score gives a... canonical: https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Beyond pass or fail: The new era of chaos engineering | daily.dev og:description: Krkn, an open source chaos engineering tool, is moving beyond binary pass/fail outcomes toward detailed resilience telemetry. Its beta Resiliency Score gives a... og:url: https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb og:image: https://api.daily.dev/og/posts/wG3vDbBlb.png og:image:alt: Beyond pass or fail: The new era of chaos engineering og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Beyond pass or fail: The new era of chaos engineering **[Red Hat Developer](https://daily.dev/sources/rhdev)** · 7 min read · 0 upvotes · 0 comments ## Summary Krkn, an open source chaos engineering tool, is moving beyond binary pass/fail outcomes toward detailed resilience telemetry. Its beta Resiliency Score gives a weighted 0-100% health metric based on Prometheus SLOs, while HTTP Health Checks track exact endpoint downtime duration and status codes, and KubeVirt Checks monitor VM connectivity and reachability during chaos experiments. Together, these three telemetry layers let teams compare resilience scores across application versions in CI/CD pipelines to catch architectural regressions, such as a version drop from a 95% to 70% resiliency score with new VM outages. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the Krkn Resiliency Score and how is it calculated? The Resiliency Score is a beta macro-health metric in Krkn ranging from 0 to 100%, calculated by tracking live Prometheus data across a chaos test window against predefined SLOs. Standard warnings default to 1 point and critical outages to 3 points using a weighted scoring model, and engineers can assign custom weights to prioritize business-critical components like authentication or payment gateways. _Teams tuning chaos experiments can track tools like Krkn's scoring approach on daily.dev._ ### How do Krkn HTTP Health Checks track application downtime during chaos testing? Krkn's HTTP Health Checks are configured in config.yaml and probe application endpoints at user-defined intervals, down to the second, throughout a chaos run. Rather than a simple pass/fail, the telemetry records the exact start time, end time, and duration of downtime along with HTTP status codes, and supports bearer tokens or credential tuples for monitoring protected endpoints. _Engineers measuring recovery time in seconds can follow resilience-testing tooling updates on daily.dev._ ### How can chaos engineering telemetry detect resilience regressions between application versions? Running identical Krkn chaos scenarios against successive application versions creates a standardized telemetry baseline for comparison. For example, if version 2.0 maintains a 95% Resiliency Score with zero HTTP endpoint failure but version 2.1 drops to 70% with a 45-second VM outage, that gap is immediate, quantifiable proof of an architectural regression introduced by the newer version. _Teams guarding CI/CD pipelines against hidden regressions can track this kind of tooling on daily.dev._ ## Similar posts on daily.dev - [Kubernetes chaos engineering at scale: Krkn Operator Developer Preview in Red Hat Advanced Cluster Management](https://daily.dev/posts/kubernetes-chaos-engineering-at-scale-krkn-operator-developer-preview-in-red-hat-advanced-cluster-m-uaavrdrey) · Red Hat Developer · 0 upvotes · 0 comments - [Why killing pods is not enough: Testing operator reconciliation with operator-chaos](https://daily.dev/posts/why-killing-pods-is-not-enough-testing-operator-reconciliation-with-operator-chaos-wpoesrwhl) · Red Hat Developer · 1 upvotes · 0 comments - [A live Kubernetes cluster can still have an ownership gap](https://daily.dev/posts/a-live-kubernetes-cluster-can-still-have-an-ownership-gap-by8o4s5rz) · The New Stack · 1 upvotes · 0 comments - [The Shift from Chaos to Controlled Reliability Testing](https://daily.dev/posts/the-shift-from-chaos-to-controlled-reliability-testing-ille2dhie) · SD Times · 1 upvotes · 0 comments - [Unlocking Kubernetes Chaos: AI Anomaly Detection That Slays MTTR](https://daily.dev/posts/unlocking-kubernetes-chaos-ai-anomaly-detection-that-slays-mttr-jmc2gw7oj) · Container Journal · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#cicd](https://daily.dev/tags/cicd), [#observability](https://daily.dev/tags/observability) [View this post on daily.dev](https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Beyond pass or fail: The new era of chaos engineering","url":"https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb"},"datePublished":"2026-09-30T13:39:02.540Z","dateModified":"2026-09-30T13:39:29.102Z","description":"Krkn, an open source chaos engineering tool, is moving beyond binary pass/fail outcomes toward detailed resilience telemetry. Its beta Resiliency Score gives a...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"Red Hat Developer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Red Hat Developer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a8895f3216c4900bdc455585a4ad3e4","url":"https://daily.dev/sources/rhdev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,cicd,observability","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Red Hat Developer","item":"https://daily.dev/sources/rhdev"},{"@type":"ListItem","position":3,"name":"Beyond pass or fail: The new era of chaos engineering"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/beyond-pass-or-fail-the-new-era-of-chaos-engineering-wg3vdbblb#faq","mainEntity":[{"@type":"Question","name":"What is the Krkn Resiliency Score and how is it calculated?","acceptedAnswer":{"@type":"Answer","text":"The Resiliency Score is a beta macro-health metric in Krkn ranging from 0 to 100%, calculated by tracking live Prometheus data across a chaos test window against predefined SLOs. Standard warnings default to 1 point and critical outages to 3 points using a weighted scoring model, and engineers can assign custom weights to prioritize business-critical components like authentication or payment gateways. Teams tuning chaos experiments can track tools like Krkn's scoring approach on daily.dev."}},{"@type":"Question","name":"How do Krkn HTTP Health Checks track application downtime during chaos testing?","acceptedAnswer":{"@type":"Answer","text":"Krkn's HTTP Health Checks are configured in config.yaml and probe application endpoints at user-defined intervals, down to the second, throughout a chaos run. Rather than a simple pass/fail, the telemetry records the exact start time, end time, and duration of downtime along with HTTP status codes, and supports bearer tokens or credential tuples for monitoring protected endpoints. Engineers measuring recovery time in seconds can follow resilience-testing tooling updates on daily.dev."}},{"@type":"Question","name":"How can chaos engineering telemetry detect resilience regressions between application versions?","acceptedAnswer":{"@type":"Answer","text":"Running identical Krkn chaos scenarios against successive application versions creates a standardized telemetry baseline for comparison. For example, if version 2.0 maintains a 95% Resiliency Score with zero HTTP endpoint failure but version 2.1 drops to 70% with a 45-second VM outage, that gap is immediate, quantifiable proof of an architectural regression introduced by the newer version. Teams guarding CI/CD pipelines against hidden regressions can track this kind of tooling on daily.dev."}}]} ```