You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2019. It is now read-only.
It is possible in envoy to configure the health check endpoint, and then it will be ignored by tracing. For example, I updated the jaeger tracing example front-envoy-jaeger.yaml to include the health check filter:
I then called the app using curl -v http://localhost:8000/trace/1 and saw a trace as expected in the Jaeger UI. Then I issued a request on the health endpoint:
$ curl -v http://localhost:8000/health
* Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8000 (#0)
> GET /health HTTP/1.1
> Host: localhost:8000
> User-Agent: curl/7.59.0
> Accept: */*
>
< HTTP/1.1 200 OK
< x-envoy-upstream-healthchecked-cluster: front-proxy
< date: Wed, 30 May 2018 09:43:40 GMT
< server: envoy
< content-length: 0
<
* Connection #0 to host localhost left intact
which did not result in a trace instance.
The issue is I currently don't know how this v2 config can be passed from Istio to the Envoy proxy. Hopefully someone with knowledge of the v2 api can answer that.
Is there anyway to filter out K8 health check probes from Tracing ?
I have been looking at few old posts about this question but none of give any solution. Everything is pointing to adding this as a feature to Envoy.
The text was updated successfully, but these errors were encountered: