Eliza Weisman 9e49054963 Classify non-gRPC status codes for HTTP telemetry (#200) ... Currently, all "success"/"failure" classifications in the telemetry API are made based on the `grpc-status` trailer. If the trailer is not present, then a request is assumed to have failed. As we start proxying non-gRPC traffic, the controller needs to also be aware of HTTP status codes, so that non-gRPC requests are not assumed to always fail. I've modified the telemetry API server to classify requests based on their HTTP status codes when the `grpc-status` trailer is not present. I've also modified the `simulate-proxy` script to generate fake HTTP/2 traffic without the `grpc-status` trailer. Closes #196 Signed-off-by: Eliza Weisman <eliza@buoyant.io>		2018-01-24 10:57:23 -08:00
..
destination-client	Upgrade k8s.io/client-go to v6.0.0 (#122)	2018-01-11 10:22:37 -08:00
simulate-proxy	Classify non-gRPC status codes for HTTP telemetry (#200)	2018-01-24 10:57:23 -08:00