On 23/02/2021 11:22, Paolo Filippelli wrote:
I've managed to correctly activate istio-proxy logs, and that's what I
can see.
This is the log when I wget "inside" the Prometheus container, with
success
[2021-02-23T10:58:55.066Z] "GET /metrics HTTP/1.1" 200 - "-" 0 75771
51 50 "-" "Wget" "4dae0790-1a6a-4750-bc33-4617a6fbaf16"
"10.172.22.36:7070" "127.0.0.1:7070" inbound|7070|| 127.0.0.1:42380
10.172.22.36:7070 10.172.23.247:38210 - default
This is the log when Prometheus scraping fails
[2021-02-23T10:58:55.536Z] "GET /metrics HTTP/1.1" 503 UC "-" 0 95 53
- "-" "Prometheus/2.11.0" "2c97c597-6a32-44ed-a2fb-c1d37a2644b3"
"10.172.22.36:7070" "127.0.0.1:7070" inbound|7070|| 127.0.0.1:42646
10.172.22.36:7070 10.172.23.247:33758 - default
According to this:
https://blog.getambassador.io/understanding-envoy-proxy-and-ambassador-http-access-logs-fee7802a2ec5
The UC response flags indicate "Upstream connection termination", which
suggests something on the destination service. I would suggest looking
at the logs there - the request ID might be useful to try to find the
request?||
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/d8168442-0408-2c41-0507-7608743fe8bf%40Jahingo.com.
