Fabric. Chaos. Data Structures Namespace
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Represents the status of Chaos.
This is the base class for all the different types of events that Chaos generates
Represents the events of ChaosEvent caused by Chaos.
Represents the filter to choose the ChaosEvent's to include in the ChaosEventsSegment
This class defines all the test parameters to configure the ChaosTestScenario.
Represents the status of running Chaos, possibly within a time range, as returned by GetChaosReportAsync(ChaosReportFilter, TimeSpan, CancellationToken).
Represents the filter to choose the interesting ChaosEvent's to include in the ChaosReport
Represents a schedule that automates rus of Chaos.
Represents a versioned ChaosSchedule. The version of a schedule is a number that gets updated when the schedule is updated.
Represents a rule for when and how to run Chaos.
Represents which days of the week the ChaosScheduleJob is active for.
Represents a time range in a 24 hour day in UTC time.
Represents a time of day in 24 hour time. Time is in UTC time.
Defines all filters for targeted Chaos faults, for example, faulting only certain node types or faulting only certain applications. If ChaosTargetFilter is not used, Chaos faults all cluster entities.If ChaosTargetFilter is used, Chaos faults only the entities that meet the ChaosTargetFilter specification. NodeTypeInclusionList and ApplicationInclusionList allow a union semantics only. It is not possible to specify an intersection of NodeTypeInclusionList and ApplicationInclusionList. For example, it is not possible to specify "fault this application only when it is on that node type." Once an entity is included in either NodeTypeInclusionList or ApplicationInclusionList, that entity cannot be excluded using ChaosTargetFilter. Even if applicationX does not appear in ApplicationInclusionList, in some Chaos iteration applicationX can be faulted because it happens to be on a node of nodeTypeY that is included in NodeTypeInclusionList.If both NodeTypeInclusionList and ApplicationInclusionList are null or empty, an ArgumentException is thrown.
Represents the event that encapsulates the faults that are being executed by Chaos.
Represents the event that is created when Chaos is started for the first time or following a stop.
Represents the Chaos event that is created when Chaos is stopped for some reason.
Represents the Chaos event that is created when a failure happens in Chaos test execution.
Represents the Chaos event that is created when validation fails and encapsulates information about why validation failed.
Represents the Chaos event that is created when Chaos is waiting for the cluster to be healthy again.
Represents the state of the Chaos schedule.
Represents the task that Chaos is presently executing.
Submit and view feedback for