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.
Currently we use Nginx ngx_mirror_module to implements mirroring of original HTTPS request and pass to other local port like 8081. So that Goreplay can capture this traffic in port 8081.
But we have a concern that the mirroring in Nginx may have an impact on system performance while pressure testing, because lots of requests might cause the mirroring also take many system resource.
So, is there any solution for GoReplay to capture the HTTPS traffic without modification on reverse-proxy nodes?
Thanks!
crylg
commented
3 weeks ago
Currently we use Nginx ngx_mirror_module to implements mirroring of original HTTPS request and pass to other local port like 8081. So that Goreplay can capture this traffic in port 8081. But we have a concern that the mirroring in Nginx may have an impact on system performance while pressure testing, because lots of requests might cause the mirroring also take many system resource. So, is there any solution for GoReplay to capture the HTTPS traffic without modification on reverse-proxy nodes? Thanks!