Finding the source of failed http requests #45997
Unanswered
KevinDW-Fluxys
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm having some issues with investigating the source of some failed requests, and I was wondering if i can do more from within Istio to find out where they are coming from.
The use case:
I noticed a pod in our cluster was having a high amount of 4xx errors. By enabling access logging for that component, i could see the following entries every second:
[2023-07-13T10:17:14.489Z] "GET /api HTTP/1.1" 403 - via_upstream - "-" 0 591 1 1 "10.138.0.15" "Go-http-client/1.1" "6e9735cf-bfbc-4f18-8e15-8a59390332d3" "pipelines.man.dev.azure.fluxys.net" "172.16.4.193:8080" inbound|8080|| 127.0.0.6:44523 172.16.4.193:8080 10.138.0.15:0 - default
[2023-07-13T10:17:14.903Z] "GET / HTTP/1.1" 403 - via_upstream - "-" 0 585 1 0 "10.138.0.9" "Go-http-client/1.1" "024beaf4-6846-451c-8e68-aa67b1f35504" "pipelines.man.dev.azure.fluxys.net" "172.16.4.193:8080" inbound|8080|| 127.0.0.6:44523 172.16.4.193:8080 10.138.0.9:0 - default
This shows me that something is constantly trying and failing to connect to this pod. I have no idea where it is coming from, as i can only see the ip from our nodes as source ip. I can also see this in kiali, but the source of the traffic is always istio-ingressgateway.
Is there a way to figure out the source of this?
Beta Was this translation helpful? Give feedback.
All reactions