Traffic Player
- Ben Clark
Overview
Allows our users to record traffic and then replay the traffic through a rule test rules on know repeatable data.
Traffic can be replayed at the same rate it was gathered or much faster to speed up test cycles.
Traffic Player will playback a previously created recording. These recordings should be started and stopped using the Journey Orchestration API. The API is called recording.
Example:
Our user records a hours worth of live website traffic that would have gone through a carousel banner on the homepage. This traffic is played back through theBanner Carousel rule in the test target with an “immediate” replay mode. This compresses the hours worth of events pushing them through very quickly. The results of the tests on the banner are reviewed, changes made and the same data pushed through again to validate the changes have worked.
How recordings work
Create your recording using the Journey Orchestration API. The recording should contain the events you wish to replay
Select the recording that you want to use in Template Builder or local Spoon. If working in Local spoon download the recording.
This will create several files on your local disk
A file containing the raw traffic data from this recording
A KTR file that reads and processes the file containing the raw traffic data file
View the data sent in the “preview data” pane for the “Replay rule invoke traffic” step and compare it against the original recorded traffic
Don’t forget that the values in the recording can be altered as desired to
Plugin Configuration
General
Fields
Tokens
Allows the user to see the field values in the JSON provided. These can then be adjusted in this screen to allow the user to see how the results differ.
The following settings can be configured:
Setting | Description |
|---|---|
Step Name | Allows the Step to be given a unique descriptive name. |
Replay Mode | Allows you to change the delay between the events created. Walltime will play the events back with the same delays that were present when created. A recording taken over an hour will therefore take an hour to playback. Immediate will replay the events as fast as possible, ignoring any delays between events. This should allow you to speed up your test processes. |
API Key mode | Requires an key to use the step and the linked recording. Don’t forget the recording may contain sensitive information if you recorded from production. Default is “none “where no key is required. |
Replay Status Column | Allows you to name the column that provides out the status of the running of the events |
Replay Response Column | Allows you to name the column that provides out the result of the running of the events |
Trace | Allows you to provide greater granularity in your logging when the recording is replayed.  None - standard logging Tile - Provides logging at a Tile level Step - Provides logging at a step level |