As such, none of our Amazon ALB (Application Load Balancer) log aggregation contains Request-ID, Request-Source, or Calling-Service. But, Amazon doesn't know anything about these architectural decisions. Using HTTP headers for request tracing is great when you are logging information inside one of your own application / domain services. As such, not all services - especially older services - uphold these tracing requirements. Calling-Source - the previous hop in the request's network chain.ĬAVEAT: I say "supposed to" because this was an evolving architectural decision.Request-Source - the originator of the request.Request-ID - a unique ID for every request.I think this may really help us!Īs requests pass through the InVision infrastructure, they are supposed to include - and propagate - the following request tracing HTTP headers: Yesterday, however, David discovered that Amazon's load balancers will record (and modify) the HTTP header, X-Amzn-Trace-Id, within their request logs. And, even though we are using request tracing headers in our distributed system, we are struggling to connect the dots as those requests pass-through Amazon's load balancers. Part of what makes this issue so challenging to debug is that there are many services that touch requests coming out of this application. At InVision, David Bainbridge and I have been working hard to figure out why some users are getting randomly logged-out of one of our client-side applications.
0 kommentar(er)
