Cherry-pick #21215 to 7.x: Handle multiple upstreams in ingress-controller#21373
Cherry-pick #21215 to 7.x: Handle multiple upstreams in ingress-controller#21373ChrsMark merged 1 commit intoelastic:7.xfrom
Conversation
(cherry picked from commit b65b123)
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Cherry-pick of PR #21215 to 7.x branch. Original message:
What does this PR do?
This PR tunes
ingress-controller's pipeline so as to handle multiple upstreams. We put the multiple lengths, times and status_codes inupstream.response.length_list,upstream.response.time_listandupstream.response.status_code_listfields while we sum time under single fieldupstream.response.timeand we only store last response length inupstream.response.length(with this we also preserve the existing dashboardsbeats/filebeat/module/nginx/_meta/kibana/7/dashboard/Filebeat-nginx-ingress-overview.json
Line 1007 in 54ea284
In addition, we preserve the multiple upstreams at
upstream_ip_listand we only store the lastupstream.ipandupstream.portas well as the laststatus_code.Sample log:
192.168.64.14 - - [07/Feb/2020:12:02:42 +0000] "GET /v2/some HTTP/1.1" 200 61 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0" 348 0.001 [default-web2-8080] [] 172.17.0.6:8080, 172.17.0.7:8080 61, 100 0.100, 0.004 200, 203 835136ae24486dbb4156dcbe21f5d402Sample event:
Why is it important?
So as to handle cases where nginx-ingress retries multiple upstreams.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues