System.Fabric.Chaos.DataStructures Namespace

Classes

ChaosDescription	Represents the status of Chaos.
ChaosEvent	This is the base class for all the different types of events that Chaos generates
ChaosEventsSegment	Represents the events of ChaosEvent caused by Chaos.
ChaosEventsSegmentFilter	Represents the filter to choose the ChaosEvent's to include in the ChaosEventsSegment
ChaosParameters	This class defines all the test parameters to configure the ChaosTestScenario.
ChaosReport	Represents the status of running Chaos, possibly within a time range, as returned by GetChaosReportAsync(ChaosReportFilter, TimeSpan, CancellationToken).
ChaosReportFilter	Represents the filter to choose the interesting ChaosEvent's to include in the ChaosReport
ChaosSchedule	Represents a schedule that automates rus of Chaos.
ChaosScheduleDescription	Represents a versioned ChaosSchedule. The version of a schedule is a number that gets updated when the schedule is updated.
ChaosScheduleJob	Represents a rule for when and how to run Chaos.
ChaosScheduleJobActiveDays	Represents which days of the week the ChaosScheduleJob is active for.
ChaosScheduleTimeRangeUtc	Represents a time range in a 24 hour day in UTC time.
ChaosScheduleTimeUtc	Represents a time of day in 24 hour time. Time is in UTC time.
ChaosTargetFilter	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.
ExecutingFaultsEvent	Represents the event that encapsulates the faults that are being executed by Chaos.
StartedEvent	Represents the event that is created when Chaos is started for the first time or following a stop.
StoppedEvent	Represents the Chaos event that is created when Chaos is stopped for some reason.
TestErrorEvent	Represents the Chaos event that is created when a failure happens in Chaos test execution.
ValidationFailedEvent	Represents the Chaos event that is created when validation fails and encapsulates information about why validation failed.
WaitingEvent	Represents the Chaos event that is created when Chaos is waiting for the cluster to be healthy again.

Enums

ChaosScheduleStatus	Represents the state of the Chaos schedule.
ChaosStatus	Represents the task that Chaos is presently executing.