[Feature]: Specify which faults to induce when using Start-ServiceFabricChaos

[jonathanpv]

Is your feature request related to a problem? Please describe your workload details. Start-ServiceFabricChaos cmdlet allows developers to invoke faults. However it seems these faults are hard-coded. As a developer attempting to test resiliency of clusters it would be beneficial to be able to have fine-grained control over the faults Start-ServiceFabricChaos induces.

I also have a requirement: My code should induce faults to services (applications?) located in another cluster, and also ones located in the same cluster.

A shared multi-tenant environment. Restarting a node will bring down multiple services, not one. Sure, it may test resiliency of cluster but we want to simulate faults at an application / service level. And there's no way Start-ServiceFabricChaos can be configured to not restart a node.

Describe the solution you'd like A parameter of list where Start-ServiceFabricChaos --faults [restartNode, movePartition, etc] so developer can fine tune what control to use.

Describe alternatives you've considered Currently we could implement the functionality ourselves, but we would lose out on Get-ServiceFabricChaosReport.

Area/Component: Reliable Services. I'm unsure if I labelled this correctly, I'm new to service fabric.

Expected behavior Not relevant.

Additional context Please let me know if you require more context.

Service Fabric Runtime Version: 9.0.1672.9590

Environment:

• Local
• OS: Windows 11 Enterprise

---

Assignees: /cc @microsoft/service-fabric-triage