Skip to content

Commit 3455bd0

Browse files
Update website/docs/user-guides/create-resilience-probe.md
Co-authored-by: Neelanjan Manna <[email protected]>
1 parent badd5b4 commit 3455bd0

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

website/docs/user-guides/create-resilience-probe.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@ You can learn about the concept of resilience probes [here](../concepts/probes.m
1111
Here are some characterstics of resilience probes.
1212
- **Unique Identifier**: Each Resilience Probe is identified by a unique name, serving as its identifier. Probe names cannot be reused for a given fault.
1313
- **Deletion Behavior**: Deleting a Resilience Probe will disable it from further use but does not delete it from the system. This ensures that the probe's history and configuration remain intact for reference and analysis.
14-
14+
:::note
15+
Starting from v3.0, it is required to add at least one Resilience Probe per chaos fault. This allows for a stricter chaos hypothesis validation which is independent of only the chaos fault's successful execution.
16+
:::
1517
For this user guide, we will use a HTTP probe.
1618

1719
## 1. Go to the Resilience Probes section

0 commit comments

Comments
 (0)