Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix spacing
Make markdownlint happy.
  • Loading branch information
martincostello authored Feb 7, 2025
commit a9e5e10b87cb76be96e4feb19a7ecc40a966a36d
1 change: 1 addition & 0 deletions docs/chaos/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,11 +47,12 @@
.AddChaosBehavior(behaviorInjectionRate, cancellationToken => RestartRedisAsync(cancellationToken)); // Inject a chaos behavior to executions
```
<!-- endSnippet -->

> [!NOTE]
> It is usual to place the chaos strategy as the last strategy in the resilience pipeline.
> By placing the chaos strategies as last, they subvert the usual outbound call at the last minute, substituting their fault or adding extra latency, etc.
> The existing resilience strategies - further out in the `ResiliencePipeline` - still apply, so you can test how the Polly resilience strategies you have configured handle the chaos/faults injected by Simmy.

Check failure on line 55 in docs/chaos/index.md

View workflow job for this annotation

GitHub Actions / build-docs

Blank line inside blockquote

docs/chaos/index.md:55 MD028/no-blanks-blockquote Blank line inside blockquote https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md028.md
> [!NOTE]
> The `AddChaosFault` `AddChaosLatency` `AddChaosOutcome` `AddChaosBehavior` will take effect sequentially if you combine them together.
> In the above example, we use **fault first then latency strategy**, it can save fault waiting time. If you put `AddChaosLatency` before `AddChaosFault`, you will get different behavior.
Expand Down
Loading