log scenario index and name, and transaction index and name #552
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #551 by including the following details in the request log:
scenario_index
scenario_name
transaction_index
(optional)transaction_name
(optional)Adding this information to the request log caused the GooseRequestMetric to grow statistically larger than the other members of the GooseMetric enum. Clippy recommended boxing it because of this:
Because
transaction_index
is optional it is represented as aString
in the log instead of as ausize
(whereas scenario_index is represented as a usize as it's always guaranteed to be set). If empty, it will show up as""
, whereas"0"
indicates the first transaction in the scenario.For example, a snippet from a CSV-formatted request log:
Or similarly, a snippet from a JSON-formatted request log:
A raw-formatted request log:
And finally, a pretty-formatted request log: