> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/chaos-engineering/troubleshooting-and-resources/faqs/index.md).

# Frequently Asked Questions

Find answers to the most common questions about Harness Chaos Engineering, from getting started to advanced implementation topics.

## Getting Started <a href="#getting-started" id="getting-started"></a>

### What is Chaos Engineering? <a href="#what-is-chaos-engineering" id="what-is-chaos-engineering"></a>

Chaos Engineering is the discipline of experimenting on a system to build confidence in the system's capability to withstand turbulent conditions in production. It involves intentionally introducing failures in a controlled manner to identify weaknesses before they cause outages.

### Why should I use Chaos Engineering? <a href="#why-should-i-use-chaos-engineering" id="why-should-i-use-chaos-engineering"></a>

Chaos Engineering helps you:

* **Identify weaknesses** before they cause production outages
* **Build confidence** in your system's resilience
* **Improve incident response** through practice and preparation
* **Reduce MTTR** (Mean Time To Recovery) during real incidents
* **Validate disaster recovery** procedures and assumptions

### Is Chaos Engineering safe? <a href="#is-chaos-engineering-safe" id="is-chaos-engineering-safe"></a>

Yes, when done properly. Chaos Engineering emphasizes:

* **Controlled experiments** with defined blast radius
* **Comprehensive monitoring** and automatic rollback
* **Starting small** and gradually increasing scope
* **Safety measures** and circuit breakers
* **Team coordination** and communication

### How is Harness Chaos Engineering different from other tools? <a href="#how-is-harness-chaos-engineering-different-from-other-tools" id="how-is-harness-chaos-engineering-different-from-other-tools"></a>

Harness Chaos Engineering offers:

* **Enterprise-grade platform** with advanced security and compliance
* **Comprehensive fault library** covering infrastructure, applications, and cloud services
* **Native CI/CD integration** for continuous resilience testing
* **Advanced automation** with intelligent rollback and remediation
* **Team collaboration features** including GameDays and shared experiments

## Implementation <a href="#implementation" id="implementation"></a>

### Where should I start with Chaos Engineering? <a href="#where-should-i-start-with-chaos-engineering" id="where-should-i-start-with-chaos-engineering"></a>

Follow this progression:

1. **Start in staging** environments, never production initially
2. **Begin with simple experiments** like pod restarts or CPU stress
3. **Use small blast radius** affecting only a few instances
4. **Set up comprehensive monitoring** before running experiments
5. **Gradually expand** scope and complexity as confidence grows

### What experiments should I run first? <a href="#what-experiments-should-i-run-first" id="what-experiments-should-i-run-first"></a>

Recommended first experiments:

* **Pod/Container deletion** - Test application restart resilience
* **CPU stress** - Validate auto-scaling and performance under load
* **Network latency** - Test timeout handling and user experience
* **Database connection failures** - Validate connection pooling and failover
* **Memory pressure** - Test memory management and garbage collection

### How do I choose what to test? <a href="#how-do-i-choose-what-to-test" id="how-do-i-choose-what-to-test"></a>

Consider these factors:

* **Business criticality** - Start with most important user journeys
* **Historical incidents** - Test scenarios based on past outages
* **System dependencies** - Focus on single points of failure
* **Recent changes** - Validate resilience of new features or infrastructure
* **Compliance requirements** - Test disaster recovery procedures

### How often should I run chaos experiments? <a href="#how-often-should-i-run-chaos-experiments" id="how-often-should-i-run-chaos-experiments"></a>

Frequency depends on your maturity:

* **Getting started**: Weekly experiments in staging
* **Intermediate**: Daily automated experiments, weekly production tests
* **Advanced**: Continuous chaos testing integrated into CI/CD
* **Mature**: Real-time chaos testing with intelligent automation

## Technical Questions <a href="#technical-questions" id="technical-questions"></a>

### What platforms does Harness Chaos Engineering support? <a href="#what-platforms-does-harness-chaos-engineering-support" id="what-platforms-does-harness-chaos-engineering-support"></a>

We support:

* **Kubernetes** (all major distributions: EKS, AKS, GKE, OpenShift)
* **Linux** (Ubuntu, RHEL, CentOS, Debian, Fedora)
* **Cloud platforms** (AWS, Azure, GCP)
* **Windows** (limited fault types)
* **VMware vSphere**
* **Container platforms** (Docker, containerd, CRI-O)

### Can I run chaos experiments in production? <a href="#can-i-run-chaos-experiments-in-production" id="can-i-run-chaos-experiments-in-production"></a>

Yes, but with proper precautions:

* **Start with staging** and build confidence first
* **Use small blast radius** (1-5% of instances initially)
* **Run during low-traffic periods** to minimize user impact
* **Have comprehensive monitoring** and automatic rollback
* **Coordinate with teams** and stakeholders
* **Follow change management** procedures

### How do I measure the success of chaos experiments? <a href="#how-do-i-measure-the-success-of-chaos-experiments" id="how-do-i-measure-the-success-of-chaos-experiments"></a>

Key metrics include:

* **Resilience score** - Overall system resilience rating
* **Recovery time** - How quickly systems return to normal
* **Error rates** - Impact on user-facing errors
* **Performance metrics** - Response time and throughput impact
* **Business metrics** - Revenue, user experience, SLA compliance

### What happens if an experiment goes wrong? <a href="#what-happens-if-an-experiment-goes-wrong" id="what-happens-if-an-experiment-goes-wrong"></a>

Harness Chaos Engineering includes multiple safety mechanisms:

* **Automatic rollback** when thresholds are breached
* **Manual stop** capability at any time
* **Blast radius limits** to contain impact
* **Comprehensive monitoring** to detect issues quickly
* **Team notifications** for immediate response

## Security and Compliance <a href="#security-and-compliance" id="security-and-compliance"></a>

### Is Harness Chaos Engineering secure? <a href="#is-harness-chaos-engineering-secure" id="is-harness-chaos-engineering-secure"></a>

Yes, we implement enterprise-grade security:

* **SOC 2 Type II** certified
* **ISO 27001** compliant
* **End-to-end encryption** for data in transit and at rest
* **RBAC** (Role-Based Access Control) for fine-grained permissions
* **Audit logging** for all activities and changes
* **SAML/SSO integration** with enterprise identity providers

### Can I use Chaos Engineering in regulated industries? <a href="#can-i-use-chaos-engineering-in-regulated-industries" id="can-i-use-chaos-engineering-in-regulated-industries"></a>

Absolutely. Many regulated industries use chaos engineering:

* **Financial services** - Test trading systems and payment processing
* **Healthcare** - Validate patient data systems and medical devices
* **Government** - Test critical infrastructure and citizen services
* **Aerospace** - Validate flight systems and ground operations

Key considerations:

* **Compliance documentation** - Maintain detailed experiment records
* **Change management** - Follow established change control procedures
* **Risk assessment** - Evaluate and document potential impacts
* **Stakeholder approval** - Get necessary approvals before testing

### How do you handle data privacy? <a href="#how-do-you-handle-data-privacy" id="how-do-you-handle-data-privacy"></a>

We protect data privacy through:

* **Data minimization** - Collect only necessary experiment data
* **Encryption** - All data encrypted in transit and at rest
* **Access controls** - Strict access controls and audit trails
* **Data retention** - Configurable retention policies
* **Regional compliance** - Support for GDPR, CCPA, and other regulations

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

### My experiment won't start. What should I check? <a href="#my-experiment-wont-start-what-should-i-check" id="my-experiment-wont-start-what-should-i-check"></a>

Common issues and solutions:

1. **Permissions** - Verify RBAC permissions for target resources
2. **Connectivity** - Check network connectivity to target systems
3. **Resource availability** - Ensure target resources exist and are healthy
4. **Configuration** - Validate experiment configuration and parameters
5. **Dependencies** - Check if required services or tools are running

### Experiments are failing unexpectedly. How do I debug? <a href="#experiments-are-failing-unexpectedly-how-do-i-debug" id="experiments-are-failing-unexpectedly-how-do-i-debug"></a>

Debugging steps:

1. **Check experiment logs** for error messages and details
2. **Verify target system health** before and during experiments
3. **Review monitoring data** for system behavior patterns
4. **Validate success criteria** and thresholds
5. **Test in isolation** to identify specific failure points

### How do I handle false positives in monitoring? <a href="#how-do-i-handle-false-positives-in-monitoring" id="how-do-i-handle-false-positives-in-monitoring"></a>

Strategies for reducing false positives:

* **Tune thresholds** based on historical data and normal variation
* **Use multiple metrics** to validate actual impact
* **Implement grace periods** to account for temporary fluctuations
* **Regular threshold review** and adjustment based on system changes
* **Composite health checks** combining multiple indicators

### My team is resistant to Chaos Engineering. How do I get buy-in? <a href="#my-team-is-resistant-to-chaos-engineering-how-do-i-get-buy-in" id="my-team-is-resistant-to-chaos-engineering-how-do-i-get-buy-in"></a>

Building team support:

* **Start with education** about chaos engineering benefits
* **Share success stories** from other organizations
* **Begin with low-risk experiments** to build confidence
* **Involve skeptics** in experiment design and execution
* **Demonstrate value** through improved incident response
* **Address concerns** about safety and potential impact

## Advanced Topics <a href="#advanced-topics" id="advanced-topics"></a>

### Can I create custom faults? <a href="#can-i-create-custom-faults" id="can-i-create-custom-faults"></a>

Yes, through several methods:

* **BYOC (Bring Your Own Chaos)** - Upload custom fault scripts
* **API integration** - Use REST APIs to trigger custom failures
* **Custom probes** - Create application-specific health checks
* **Script execution** - Run custom scripts during experiments

### How do I integrate with my existing monitoring tools? <a href="#how-do-i-integrate-with-my-existing-monitoring-tools" id="how-do-i-integrate-with-my-existing-monitoring-tools"></a>

Harness integrates with popular tools:

* **Prometheus/Grafana** - Native metrics integration
* **Datadog** - Real-time monitoring and alerting
* **New Relic** - APM and infrastructure monitoring
* **Splunk** - Log analysis and correlation
* **PagerDuty** - Incident management and escalation

### Can I automate chaos experiments in CI/CD pipelines? <a href="#can-i-automate-chaos-experiments-in-cicd-pipelines" id="can-i-automate-chaos-experiments-in-cicd-pipelines"></a>

Yes, we provide:

* **GitHub Actions** integration
* **Jenkins plugins** and pipeline steps
* **GitLab CI** integration
* **Azure DevOps** extensions
* **Native Harness CI/CD** integration
* **REST API** for custom integrations

### How do I scale chaos engineering across multiple teams? <a href="#how-do-i-scale-chaos-engineering-across-multiple-teams" id="how-do-i-scale-chaos-engineering-across-multiple-teams"></a>

Scaling strategies:

* **Standardized templates** for common experiment types
* **Shared experiment library** for reusable scenarios
* **Team-specific permissions** and resource isolation
* **Centralized reporting** and analytics
* **Training programs** and best practice sharing
* **Center of Excellence** for chaos engineering governance

## Pricing and Licensing <a href="#pricing-and-licensing" id="pricing-and-licensing"></a>

### How is Harness Chaos Engineering priced? <a href="#how-is-harness-chaos-engineering-priced" id="how-is-harness-chaos-engineering-priced"></a>

Pricing is based on:

* **Infrastructure targets** - Number of nodes/instances under test
* **Experiment executions** - Number of experiments run per month
* **Advanced features** - Enterprise features and support levels
* **Deployment model** - SaaS vs. Self-Managed pricing

Contact [sales](https://harness.io/contact-sales) for detailed pricing information.

### Is there a free tier available? <a href="#is-there-a-free-tier-available" id="is-there-a-free-tier-available"></a>

Yes, we offer:

* **Free tier** with limited experiments and targets
* **Trial period** for full feature evaluation
* **Developer accounts** for learning and experimentation
* **Open source** components for basic chaos testing

### What support options are available? <a href="#what-support-options-are-available" id="what-support-options-are-available"></a>

Support tiers include:

* **Community support** - Forums and documentation
* **Standard support** - Business hours email support
* **Premium support** - 24/7 support with SLA guarantees
* **Enterprise support** - Dedicated customer success manager

## Getting Help <a href="#getting-help" id="getting-help"></a>

### Where can I find more information? <a href="#where-can-i-find-more-information" id="where-can-i-find-more-information"></a>

Resources available:

* [**Documentation**](/resilience-testing/chaos-engineering/new-to-chaos-engineering/overview.md) - Comprehensive guides and tutorials
* [**Community Forum**](https://community.harness.io) - Ask questions and share experiences
* [**Slack Community**](https://harnesscommunity.slack.com) - Real-time chat with users and experts
* [**FAQs**](/resilience-testing/chaos-engineering/troubleshooting-and-resources/faqs.md) - Frequently asked questions and solutions
* [**Training Programs**](https://university.harness.io) - Structured learning paths

### How do I contact support? <a href="#how-do-i-contact-support" id="how-do-i-contact-support"></a>

Support channels:

* **In-app support** - Submit tickets directly from the platform
* **Email support** - <support@harness.io>
* **Phone support** - Available for premium customers
* **Emergency support** - 24/7 for critical issues (enterprise customers)

### Can I request new features? <a href="#can-i-request-new-features" id="can-i-request-new-features"></a>

Yes, we welcome feedback:

* **Feature requests** through in-app feedback
* **Community voting** on proposed features
* **Direct feedback** to customer success managers
* **Beta programs** for early access to new features

***

## Still have questions? <a href="#still-have-questions" id="still-have-questions"></a>

If you can't find the answer you're looking for:

1. **Check our** [**detailed FAQs**](/resilience-testing/chaos-engineering/troubleshooting-and-resources/faqs.md) for technical questions
2. **Join our** [**Community Forum**](https://community.harness.io) to ask questions
3. **Contact** [**Support**](mailto:support@harness.io) for technical assistance
4. **Schedule a** [**demo**](https://harness.io/demo) to speak with our experts

{% hint style="info" %}
**QUICK HELP**

For immediate assistance, use the in-app help chat or check our [Resources](/resilience-testing/chaos-engineering/troubleshooting-and-resources/troubleshooting.md) section for common issues and solutions.
{% endhint %}