linkerd2/proxy
Eliza Weisman c688cf6028
Add response classification to proxy metrics (#639)
This PR adds a `classification` label to proxy response metrics, as @olix0r described in https://github.com/runconduit/conduit/issues/634#issuecomment-376964083. The label is either "success" or "failure", depending on the following rules:
+ **if** the response had a gRPC status code, *then*
   - gRPC status code 0 is considered a success
   - all others are considered failures
+ **else if** the response had an HTTP status code, *then*
  - status codes < 500 are considered success,
  - status codes >= 500 are considered failures
+ **else if** the response stream failed **then**
  - the response is a failure.

I've also added end-to-end tests for the classification of HTTP responses (with some work towards classifying gRPC responses as well). Additionally, I've updated `doc/proxy_metrics.md` to reflect the added `classification` label.

Signed-off-by: Eliza Weisman <eliza@buoyant.io>
2018-03-28 14:49:00 -07:00
..
controller-grpc Turn off the `use_logging` default feature of quickcheck. (#465) 2018-02-26 16:04:58 -10:00
convert Prepare for the v0.3.0 release (#406) 2018-02-21 11:14:11 -08:00
futures-mpsc-lossy Prepare for the v0.3.0 release (#406) 2018-02-21 11:14:11 -08:00
router Proxy: Upgrade h2 and indexmap crates (#572) 2018-03-14 12:35:38 -07:00
src Add response classification to proxy metrics (#639) 2018-03-28 14:49:00 -07:00
tests Add response classification to proxy metrics (#639) 2018-03-28 14:49:00 -07:00
Cargo.toml proxy: add SIGTERM and SIGINT handlers (#581) 2018-03-16 18:53:20 -07:00
Dockerfile Actually skip flaky tests on CI and in Docker (#626) 2018-03-26 17:11:06 -07:00