API GW trace is not being logged

[jaksky]

Hello,

we are using API GW which runs service_agent: "ESPv2/2.41.0". Unfortunately, we don't see trace id being logged into GCP standard logging.

In our setup GLB -≥ API GW -> Cloud Run

We see GLB trace in our logs and same for Cloud Run. Api GW is missing. According this documentation GLB adds Traicing context. So it seems that API GW is not logging this information. I think that it is really key to have it present.

Do we need to somehow enable it?
Is there a way how to pass startup options when using it as a API Gateway?

[nareddyt]

ESPv2 supports tracing, but AFAIK Cloud API Gateway did not enable it for their managed deployments of ESPv2 unfortunately. There are some concerns with trace sample rate and propagating the traces back to your GCP project. If they enable the feature, you should start seeing trace ids in the access log.

I suggest filing a cloud customer support issue to Cloud API Gateway, asking for this feature request.