This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
API Gateway based on ESPv2/2.41.0 doesn't log trace context so it is hard to pair request from API GW with backend logs.

What you expected to happen:
Having trace ID logged that corresponding log lines are connected across services
Header seems to be propagated but it is not logged

Steps to reproduce:
In our serverless setup we have Global LB -> API GW -> Cloud Run

Trace context is not logged

Other information (workarounds you have tried, documentation consulted, etc):
Followed setup https://cloud.google.com/api-gateway/docs/gateway-load-balancing
Global LB would add Trace context according https://cloud.google.com/load-balancing/docs/https#target-proxies

Issue 267332446

Links (3)

Issue metadata