Narasimha Karumanchi
Narasimha Karumanchi
*Title*: Wrong response flag *Description*: The access log is showing the wrong response flag for all logs. Following is the sample. It has "-" for log messages. {"path":null,"authority":null,"downstream_remote_address":"49.37.131.33:64345","duration":5303,"upstream_local_address":"0.0.0.0:49171","bytes_sent":8453,"x_forwarded_for":null,"downstream _local_address":"172.17.160.240:443","upstream_transport_failure_reason":null,"request_id":null,"user_id":null,"response_code":0,"req_method":null,"req_path":null,"**response_flags**":"-","rou te_name":null,"upstream_cluster":"hosted_proxy","method":null,"req_body":null,"upstream_service_time":null,"upstream_host":"10.0.0.5:8443","start_time":"2022-09-10T14:27:14.956Z","requeste...
Increasing access log on Windows *Description*: On Windows, we have tried to use the envoyproxy with access_log enabled. Over time, I think there is no default way to rotate the...
Event Tracing for Windows (ETW) support for Windows *Description*: I see the logs which are being generated by either access_logs or containers are not compatible with windows ETW.
Did anyone test the rate limit with Windows? Even though it is platform-independent, I could not see any tests on Windows.