Cloud asset export missing fields on Bigquery [212719457]

Assigned

Feature Request

Status Update

No update yet.

Description

lu...@google.com

created issue #1

Dec 30, 2021 08:03PM

Issue summary: The customer is trying to get the billing sync table information from the resulting table of a cloud asset inventory export.

The customer is using the table id of the billing sync table on bigquery

But when the customer retrieves the information from the cloud asset export in bigquery, the query returns information related to the billing sync table, but a lot of columns returned a null value and the customer needs information about the size of the table, number of rows of the table etc.

The related attributes are null:

"numBytes": null, "numPhysicalBytes": null, "numLongTermBytes": null, "numRows": null,

1.- Why that attributes are coming all as "null"?

2.- Isn't the Cloud Asset export supposed to fill those fields?.

Reproduction Steps: 

gcloud \

asset export \

--content-type 'resource' \

--asset-types="assets_types" \

--organization "org ID" \

--bigquery-table "projects/"projectID"/datasets/"dataset"/tables/"table" " \

--output-bigquery-force \

--per-asset-type

Comments

ch...@google.com <ch...@google.com> #2Dec 30, 2021 08:15PM

Any news on this issue?

ch...@google.com <ch...@google.com> Feb 24, 2022 10:27PM

Reassigned to yu...@google.com.

sa...@google.com <sa...@google.com> #3Oct 18, 2022 04:10PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build
Which Android build are you using? (e.g. OPP1.170223.012)

Device used
Which device did you use to reproduce this issue?

Steps to reproduce
What steps are needed to reproduce this issue?

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

de...@americanas.io <de...@americanas.io> #4Oct 18, 2022 09:23PM

Please share the details requested in

comment #3

, to proceed further with the bug.

yu...@google.com <yu...@google.com> Oct 20, 2022 11:11PM

Reassigned to yi...@google.com.

yi...@google.com <yi...@google.com> #5Nov 2, 2022 05:58PM

Android build:
Happened on every Android version I tested this, i.e. API 21 to API 29

Device used:
Pixel 2 XL as well as several emulated devices in Android Studio

Steps to reproduce:
See original post

Frequency:
Always, i.e. 100%

Android bug report:
N.A.

Screen capture of the issue
N.A.

[Deleted User] <[Deleted User]> #6Apr 6, 2023 09:02AM

Facing the same problem. UsageStatsManager.queryUsageStats seems to return unpredictable results. I will post more details later.

o....@plarium.com <o....@plarium.com> #7Apr 7, 2023 07:21PM

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

[Deleted User] <[Deleted User]> #8Apr 11, 2023 02:46PM

Please share the apk requested in

comment #7

, to proceed further with the bug.

di...@google.com <di...@google.com> Apr 12, 2023 01:41AM

Reassigned to di...@google.com.

di...@google.com <di...@google.com> #9May 9, 2023 03:12AM

I created this issue more than a year ago. Back then I did solve this by some workaround / own method. Of course I am now working on something else and cannot develop and provide an extra app for you.

Also please note that this is in fact not anything app-specific but rather a general problem with the Android API (e.g. you might have a look at the multiple threads regardings this on

stackoverflow.com).

Message last modified on May 9, 2023 03:13AM

yu...@google.com <yu...@google.com> #10May 10, 2023 12:30AM

@ <be...@googlemail.com> in

comment #9

Are you using **UsageStatsManager.queryEvents** instead of **queryUsageStats** in your workaround / own method?
**queryEvents** is more precise, however, I have to filter the query result and do lots of computation to get the app usage information.
It's some workaround but not a user-friendly solution.

[Deleted User] <[Deleted User]> #11May 10, 2023 01:44AM

We have passed this to the development team and will update this issue with more information as it becomes available.

di...@google.com <di...@google.com> #12May 10, 2023 04:25PM

This is nonsense, it says that i have used viber for 50 minutes today, and i didn't open it even once. When i use queryAndAggregateUsageStats() method it says that 50 minutes are spent on viber which is incorrect, and for the other apps it surprisingly is quite correct. If i use queryEvents, it says that viber is used 0 minutes which is correct, but it says that instagram is used 23 hours, and for the other apps it is correct. And if i use queryUsageStats() all the data is let's say random... I don't understand how app usage stats apps on playstore work that good.

ad...@capitalone.com <ad...@capitalone.com> #13Aug 30, 2023 04:36PM

Hi Team,

Even I’m facing same issue. I tried many methods, tried to run on different android versions but same result. There is some issue UsageStats manager API itself.

rp...@ford.com <rp...@ford.com> #14Nov 29, 2023 09:30PM

Hi
I use the usageStatManager and queryAndAggregateUsageStats in two different devices and try to get the usageStats in several periods. The results are wrong. It gave some usage stats that not exist in the given period.

https://drive.google.com/file/d/1wIDMTEXZFjrrHLgHY-SBsoddzUKg0pQ0/view?usp=drive_web (Screenshot_20200702-202506.jpg)

do...@google.com <do...@google.com> #15Nov 29, 2023 11:09PM

Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete.
If this issue currently still exists, we request that you log a new issue along with the bug report here

https://goo.gl/TbMiIO and reference this bug for context.

pa...@sabre.com <pa...@sabre.com> #16Jul 17, 2024 05:10AM

This API is really weird and hard to use. Can someone please help?