Hi guys, I'm testing the bigquery ingestion, and f...
# troubleshoot
n
Hi guys, I'm testing the bigquery ingestion, and for metadata works fine but i don't get any lineage or usage info. the cli (version 0.8.26.3) says parsing 0 rows from logs. So i tried to execute the log filter on gcp console and when i filter with this condition:
protoPayload.serviceName="<http://bigquery.googleapis.com|bigquery.googleapis.com>"
i do get logs. but if i add the second condition taken from the connector, no logs are found:
protoPayload.methodName="jobservice.jobcompleted"
Instead in my logs the method name is formatted like this:
methodName: "google.cloud.bigquery.v2.JobService.InsertJob"
any advice on this one? thanks!
d
Let me look after this…
n
thanks!
d
I need to do some investigation what is the difference between the two and to understand if it can happen one returns with result while the other not.
n
ok, let me know if i can give you further info
d
hey, Could you check me please if these returns queries?
Copy code
protoPayload.serviceName="<http://bigquery.googleapis.com|bigquery.googleapis.com>" AND protoPayload.methodName="google.cloud.bigquery.v2.JobService.Query"
And this one?
Copy code
protoPayload.serviceName="<http://bigquery.googleapis.com|bigquery.googleapis.com>" AND protoPayload.methodName="jobservice.jobcompleted"
n
Hey, i actually get no results for both
d
Are you sure you ran some query in bigquery before? I would like to understand what is happening.
n
yes we have several airflow dags running. but i can see only logs with methodName = google.cloud.bigquery.v2.JobService.InsertJob. i agree that this sounds strange
d
thanks, I try to research further and will get back to you
Hey, I rewrote the query by the audit v2 format. Can you check this as well ->
Copy code
resource.type=("bigquery_project") AND protoPayload.methodName=("google.cloud.bigquery.v2.JobService.Query" OR "google.cloud.bigquery.v2.JobService.InsertJob") AND protoPayload.metadata.jobChange.job.jobStatus.jobState="DONE" AND NOT protoPayload.metadata.jobChange.job.jobStatus.errorResult:*
I tried it locally and for me it gives the same results as the v1 version but let’s see if it is the same on your side as well.
n
Hey, yes with this one i'm getting bigquery related logs!
d
Interesting but great to hear 🙂 For me both gives back the same results but based on the documentation v2 is the recommended way to use.
n
yes maybe it's due to some particular configuration in our environment, not sure about it. Thanks for taking the time!
d
Other users are facing this issue as well and this seems to be promising to solve it.
🚀 1
@numerous-application-54063 We cut a new python release yesterday and there there is an option to enable the v2 api. I wonder if you could give it a go and test if this helps. To enable it you should set in your bigquery source recipe:
use_v2_audit_metadata: True
n
i tested it and it was still not working, but now can also be a permission issue on my side, since the query seems to work in the cloud logging ui. i will try to have a more detailed look at this and get back to you 🙂
d
Thanks