More data in logs #203
Description
It would simplify debuging kubernetes cluster problems / mittens configuration parameter errors when additional data regarding what is going on, at least where it's connecting to and url that is getting fetched / or has problems would be logged.
Current output log
2021/11/29 01:34:45 Wrote file: alive
2021/11/29 01:34:45 []
2021/11/29 01:34:45 Waiting for http target to be ready for a max of 60s
2021/11/29 01:34:46 HTTP target not ready yet...
2021/11/29 01:34:47 HTTP target not ready yet...
2021/11/29 01:34:48 HTTP target not ready yet...
Rational
It's hard to debug configuration (we were working on READY check) when you work with a black box
When log has more data, debugging the problems and finding a solution is much easier.
2021/11/29 01:34:45 Writing file: alive
2021/11/29 01:34:45 Wrote file: alive
2021/11/29 01:34:45 []
2021/11/29 01:34:45 creating httpclient to host: http://apidsp2.xyz.com:80
2021/11/29 01:34:45 Waiting for http target to be ready for a max of 60s
2021/11/29 01:34:46 creating request: http://apidsp2.xyz.com:80/health.aspx
2021/11/29 01:34:46 status code: 404
2021/11/29 01:34:46 HTTP target not ready yet...
2021/11/29 01:34:47 creating request: http://apidsp2.xyz.com:80/health.aspx
2021/11/29 01:34:47 status code: 404
2021/11/29 01:34:47 HTTP target not ready yet...
or output like from the warmup phase:
021/11/29 16:07:00 🔴 http response 89 ms 404 POST /process.aspx
2021/11/29 16:07:00 🔴 http response 300 ms 404 POST /process.aspx
2021/11/29 16:07:00 🔴 http response 279 ms 404 POST /process.aspx