Type Members

1.  class ReplayingEventsSequencerClientTransport extends SequencerClientTransport with NamedLogging

   Transport implementation for replaying messages from a file.

2.  class ReplayingSendsSequencerClientTransport extends SequencerClientTransport with NamedLogging with NoTracing with FlagCloseableAsync

   Replays previously recorded sends against the configured sequencer and using a real sequencer client transport.

   Replays previously recorded sends against the configured sequencer and using a real sequencer client transport. Records the latencies/rates to complete the send itself, and latencies/rates for an event that was caused by the send to be witnessed. These metrics are currently printed to stdout. Sequencers are able to drop sends so to know when all sends have likely been sequenced we simply wait for a period where no events are received for a configurable duration. This isn't perfect as technically a sequencer could stall, however the inflight gauge will report a number greater than 0 indicating that these sends have gone missing. Clients are responsible for interacting with the transport to initiate a replay and wait for observed events to be idle. A reference can be obtained to this transport component by waiting on the future provided in ReplayAction.SequencerSends. This testing transport is very stateful and the metrics will only make sense for a single replay, however currently multiple or even concurrent calls are not prevented (just don't).