az sf chaos
Manage the Service Fabric Chaos service, designed to simulate real failures.
|az sf chaos start||If Chaos is not already running in the cluster, starts running Chaos with the specified in Chaos parameters.|
az sf chaos start
If Chaos is not already running in the cluster, starts running Chaos with the specified in Chaos parameters.
az sf chaos start [--app-type-health-policy-map]
JSON encoded list with max percentage unhealthy applications for specific application types. Each entry specifies as a key the application type name and as a value an integer that represents the MaxPercentUnhealthyApplications percentage used to evaluate the applications of the specified application type.
Disables the move primary and move secondary faults.
The maximum amount of time to wait for all cluster entities to become stable and healthy.
The maximum number of concurrent faults induced per iteration.
When evaluating cluster health during Chaos, the maximum allowed percentage of unhealthy applications before reporting an error.
When evaluating cluster health during Chaos, the maximum allowed percentage of unhealthy nodes before reporting an error.
Total time (in seconds) for which Chaos will run before automatically stopping. The maximum allowed value is 4,294,967,295 (System.UInt32.MaxValue).
The server timeout for performing the operation, specified in seconds. This is the maximum time a client can wait.
Wait time (in seconds) between consecutive faults within a single iteration.
Time-separation (in seconds) between two consecutive iterations of Chaos.
When evaluating cluster health during Chaos, treat warnings with the same severity as errors.
Increase logging verbosity to show all debug logs.
Show this help message and exit.
JMESPath query string. See http://jmespath.org/ for more information and examples.
Increase logging verbosity. Use --debug for full debug logs.