Status Update
No update yet.
Comments
sa...@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.
sa...@google.com
Please note exists an investigation performed in the blocking feature request additional information can be found here
Description
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:
Customer found GCP's error messages are not helpful enough, and their debugging options are restricted.
This makes it challenging to resolve errors efficiently.
In GCP environment we were only able to see errors in metrics explorer
What you expected to happen:
Straight forward native functions to keep monitoring and get enough information to debug pub/sub issues.
Steps to reproduce:
We are deploying 2 kinds of go lang container application on our platform, one behaves as a publisher to Google pub/sub topic, and the other as a subscriber.
Both received an error "rpc error: code = PermissionDenied desc = The caller does not have permission" when publishing messages and subscribing to existing subscription in the given time frame. We don't have a screenshot that can be shared, just an error message from pub/sub API and this is all.
Other information (workarounds you have tried, documentation consulted, etc):
I've suggested to the customer to use GKE to trace all the errors from client side
Cx said Migrating application to GKE is currently not an option for them for various reasons.