Update "First chaos experiment" #9474
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67b823c845358729e8c1da96--harness-developer.netlify.app |
SmritiSatya
requested review from
deepanshuHarness,
jimin-harness,
guna-harness,
neelanjan00,
shovanmaity,
Jonsy13,
Saranya-jena,
Adarshkumar14,
ispeakc0de,
amityt,
uditgaurav,
S-ayanide,
vanshBhatia-A4k9,
ksatchit,
umamukkara,
SarthakJain26,
pratmit and
wei-harness
as code owners
ksatchit
reviewed
Feb 28, 2025
|
|
||
| 3. [Enabling a chaos infrastructure](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#enable-chaos): The required chaos infrastructure is enabled within a chaos environment. | ||
| 2. [Add an environment](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#create-environment) and [create an infrastructure](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#enable-chaos): A chaos experiment is performed within a chaos environment that houses the necessary infrastructure. The required chaos infrastructure is enabled within a chaos environment. |
There was a problem hiding this comment.
Suggested change
| 2. [Add an environment](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#create-environment) and [create an infrastructure](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#enable-chaos): A chaos experiment is performed within a chaos environment that houses the necessary infrastructure. The required chaos infrastructure is enabled within a chaos environment. | |
| 2. [Add an environment](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#create-environment) and [create an infrastructure](/docs/chaos-engineering/use-harness-ce/infrastructures/enable-disable#enable-chaos): A chaos experiment is performed within an environment that houses the chaos-enabled infrastructure. |
ksatchit
reviewed
Feb 28, 2025
| In the agent model, a chaos agent has to be deployed on the target resource and then the chaos agent runs the chaos experiments on the local resources. | ||
|
|
||
|  | ||
|
|
||
| Agent model is preferred to run chaos experiments on the Linux or Windows hosts. However, they can be used to run chaos experiments on all types of resources. The following table provides different agent types and corresponding target resources. | ||
| Agent model is preferred to run chaos experiments on the Linux or Windows hosts. However, they can be used to run chaos experiments on all types of resources. |
There was a problem hiding this comment.
Suggested change
| Agent model is preferred to run chaos experiments on the Linux or Windows hosts. However, they can be used to run chaos experiments on all types of resources. | |
| Agent model is preferred to run chaos experiments on the Linux or Windows hosts. |
ksatchit
reviewed
Feb 28, 2025
| @@ -87,7 +89,7 @@ Chaos governance is a critical feature of the Harness Chaos Engineering module, | |||
| 2. Guardrails around running chaos experiments. This is achieved through the [ChaosGuard](/docs/chaos-engineering/use-harness-ce/governance/governance-in-execution/). | |||
|
|
|||
| ### Construct Chaos Experiments | |||
| Chaos experiments are initially constructed using an easy-to-use UI based builder called **Chaos Studio**. Chaos Studio helps in building complex chaos experiments with ease and also provides a great execution view. Chaos experiments will have chaos faults and resilience probes. Chaos fault templates are taken from the Enterprise ChaosHub and then tuned to the needs of the experiment. Resilience probes are constructed either from scratch or using the templates, tuned and then attached to a fault or an experiment. | |||
| Chaos experiments are initially [constructed](/docs/chaos-engineering/use-harness-ce/experiments/create-experiments) using an easy-to-use UI based builder called **Chaos Studio**. Chaos Studio helps in building complex chaos experiments with ease and also provides a great execution view. Chaos experiments will have chaos faults and resilience probes. Chaos fault templates are taken from the Enterprise ChaosHub and then tuned to the needs of the experiment. Resilience probes are constructed either from scratch or using the templates, tuned and then attached to a fault or an experiment. | |||
There was a problem hiding this comment.
Suggested change
| Chaos experiments are initially [constructed](/docs/chaos-engineering/use-harness-ce/experiments/create-experiments) using an easy-to-use UI based builder called **Chaos Studio**. Chaos Studio helps in building complex chaos experiments with ease and also provides a great execution view. Chaos experiments will have chaos faults and resilience probes. Chaos fault templates are taken from the Enterprise ChaosHub and then tuned to the needs of the experiment. Resilience probes are constructed either from scratch or using the templates, tuned and then attached to a fault or an experiment. | |
| Chaos experiments are initially [constructed](/docs/chaos-engineering/use-harness-ce/experiments/create-experiments) using an easy-to-use UI based builder called **Chaos Studio**. Chaos Studio helps in building complex chaos experiments with ease and also provides a great execution view. Chaos experiments will have chaos faults and resilience probes. Chaos fault templates are taken from the Enterprise ChaosHub and then tuned to the needs of the experiment. Resilience probes are constructed in accordance with the validation needs and mapped to the desired faults. |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67c168475aa6e825de0870b6--harness-developer.netlify.app |
ksatchit
approved these changes
Feb 28, 2025
deepanshuHarness
approved these changes
Feb 28, 2025
wei-harness
approved these changes
Feb 28, 2025
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First experiment
Execute experiment using API
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: