Status Update
No update yet.
Comments
su...@google.com
su...@google.com
Hello,
Thank you for reaching out to us!
I tried to reproduce this issue at my end. However, I am getting the intended behavior.
Please check the
Please let me know if that helped you with your use case and if there is anything else you would need assistance with.
Thank you
st...@gmail.com
> Scheme
> JavaScript origins must use the HTTPS scheme, not plain HTTP. Localhost URIs (including localhost IP address URIs) are exempt from this rule.
Subdomains of localhost (ie. foo.localhost) *are* "Localhost URIs" but are not currently exempt from the rule, contrary to the documentation.
su...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
st...@gmail.com
Thanks for the reply. Though Traicing is not supported by API GW, I understood it in the context of the ability to start and initiate trace context. Inability to configure sampling period etc. This I understood more on the side of logging support (structured logging).
Nonetheless, If API Gateway doesn't log an existing trace context or offer a way to customize logging fields, it is near to impossible to have reasonable supportability using this component. As far as I understand, ESP V2 does offer tracing support already.
Logging existing trace context could be a great improvement with the relatively low effort needed with big value delivered supporting very common scenario for serverless deployment
Description
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
Global LB would add Trace context according