In Progress
Status Update
Comments
bl...@google.com <bl...@google.com>
st...@google.com <st...@google.com> #3
+1
er...@condenast.com <er...@condenast.com> #4
Is there still no update or ETA or progress you could relate on this?
ra...@google.com <ra...@google.com> #5
Hello,
The product team is still analyzing this, please consider that once they have new information they will post it here. However, there is no ETA for the release.
sa...@google.com <sa...@google.com> #6
Hi team do we have an update or timelines on this feature request?
st...@google.com <st...@google.com> #7
Hi team,
do we have any update? customer would like to observe the payload size.
thanks
do we have any update? customer would like to observe the payload size.
thanks
mi...@strive.ai <mi...@strive.ai> #8
+1 for this. I see random AppendRows failures but can't figure out what the root cause is given it's behind a BQ Subscription with pub/sub. Would like to see logs in addition to metrics if possible? Any advice on where to see logs for BQ Subscriptions?
ds...@google.com <ds...@google.com>
mb...@uma-health.com <mb...@uma-health.com> #9
Hello Team,
I am also looking forward to a solution to this feature request. Any news?
I am also looking forward to a solution to this feature request. Any news?
bw...@google.com <bw...@google.com>
ga...@google.com <ga...@google.com> #10
This ask is currently in our backlog, and we will consider this for 2024 plans.
an...@iheartmedia.com <an...@iheartmedia.com> #11
mega bump on this, really hard to debug issues without it
ga...@google.com <ga...@google.com>
ni...@google.com <ni...@google.com>
em...@google.com <em...@google.com> #12
Hello team
Any update on this please?
Thank you,
Emna
Any update on this please?
Thank you,
Emna
ni...@google.com <ni...@google.com> #13
Comment has been deleted.
ni...@google.com <ni...@google.com> #14
A Storage Read API specific BigQuery Information_Schema table is under development which should address these needs around spend reporting and error troubleshooting.
I will share an ETA when possible.
Description
Problem you have encountered:
We are unable to find a way to distinguish calls to BigQuery via Storage API and REST API in the logs. This distinction is required as the pricing model is very different.
we are aware we can see the usage of the BigQuery Storage API in the APIs & Services menu but having the logs in Satckdriver it much suitable
What you expected to happen:
being able to See log of the call made to the BigQuery Storage API same way we can see the log of the call made to to the REST API
Steps to reproduce:
1) Create a BigQuery table
2) Load data to the table
3) Use the quickstart[1] to query the table
4) Check the Stackdriver logs
[1]: ttps://
Other information (workarounds you have tried, documentation consulted, etc):