GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.
TBD
TBD
Full Changelog: https://github.com/buger/goreplay/compare/v1.3.2...1.3.3
--input-raw-realip-header https://github.com/buger/goreplay/pull/996
Thanks @DimaGolomozy!
Added official Windows support https://github.com/buger/goreplay/wiki/Running-on-Windows
Traffic capture engine fully re-constructed to be more scalable, efficient and bulletproof. You should see way lower packet loss, capture quality, and CPU/Memory usage.
Deprecated own HTTP client in favour of native Go HTTP library https://github.com/buger/goreplay/pull/833
Increased stability, and numerous bug fixes.
--input-raw :80,8080,3000 https://github.com/buger/goreplay/pull/935
--output-tcp-skip-verify flag to skip TCP output TLS verification https://github.com/buger/goreplay/pull/814 @tomerf--output-tcp-workers to configure number of TCP output connections https://github.com/buger/goreplay/pull/819
--http-pprof enabled: /debug/vars%i file name variable to inject unique instance ID to file name. Can be useful if you have logs from multiple machines and you need unique names.--input-file-dry-run option to previewing how long it will take and how many requests in given file input https://github.com/buger/goreplay/commit/8e76559b492402ef1d2aee99e0106d085db7f935
--input-raw-max-wait option (in seconds), which allows to skip long pauses in recorded files https://github.com/buger/goreplay/commit/19ad90aa4bb0320c8ba623d5509a0690e8c3ec25
--input-file-read-depth option to pre-read and buffer requests (and sort them). By default, is 100 https://github.com/buger/goreplay/commit/625ed54f1ebcc006e7d04a27544807fbaff08508
--input-raw-timestamp-type go to enable application level timestamps, when network timestamps unreliable https://github.com/buger/goreplay/commit/8edb74e57276c712444ccfb89ed40dd0ca5c39d6
Thank you, @urbanishimwe, @slimus, @arijitAD for jumping with me to this adventure!
Huge kudos to all GoReplay community, especially to our contributors @DimaGolomozy @tomerf @swills @davidFR @two @jl2005 @rmasclef @othererik @ankitdobhal @eko @code4wt @wangfeng22 @lins05 @betty1126 @YuriYin @StanleyP
--input-raw-bpf-filter https://github.com/buger/goreplay/commit/2b993eda49b2a9e9d54ae6cbd616dbb6f6f28388
--http-pprof enabled: /debug/vars--input-file-dry-run option to previewing how long it will take and how many requests in given file input https://github.com/buger/goreplay/commit/8e76559b492402ef1d2aee99e0106d085db7f935
--input-raw-max-wait option (in seconds), which allows to skip long pauses in recorded files https://github.com/buger/goreplay/commit/19ad90aa4bb0320c8ba623d5509a0690e8c3ec25
--input-file-read-depth option to pre-read and buffer requests (and sort them). By default, is 100 https://github.com/buger/goreplay/commit/625ed54f1ebcc006e7d04a27544807fbaff08508
--input-raw-timestamp-type go to enable application level timestamps, when network timestamps unreliable https://github.com/buger/goreplay/commit/8edb74e57276c712444ccfb89ed40dd0ca5c39d6
af_packet packet capture engine for Linux https://github.com/buger/goreplay/pull/950
--input-raw :80,8080,3000 #935--input-raw localhost:80), now it properly binds to loopback interface #943