Assigned
Status Update
Comments
se...@google.com <se...@google.com>
se...@google.com <se...@google.com> #2
Hello,
Thank you for filing this Feature Reques!
If I may ask, what difference would this feature make on a business level if you can already get the result?
Regards.
ad...@ims-edu.org <ad...@ims-edu.org> #3
Thank you for your quick response.
This would be of tremendous impact to our org on a business level.
Our legal department requires regular updates on who is on legal hold every so often in order to be able to send out communications to those users updating their legal hold status. Being able to automate the retrieval of this list via a single API call rather than potentially hundreds of API calls that returns the same information lessens the impact on our daily API quota limits. Additionally, the fewer the API calls and iteration required decreases potentials for errors during execution of any automated process to retrieve this data. Additionally, it requires no manual intervention to get this report out on an automated schedule, instead of having to manually download the CSV from the Vault admin console and then creating a properly formatted email with this info. And finally, with the ability to quickly retrieve this information without concern for daily quota limits, we can sync this information with a dashboard application that our admins use for updated status information on all our users, ensuring that holds can be added/removed in a timely fashion if current status information is always readily available in near real-time.
Thank you, I hope this helps.
This would be of tremendous impact to our org on a business level.
Our legal department requires regular updates on who is on legal hold every so often in order to be able to send out communications to those users updating their legal hold status. Being able to automate the retrieval of this list via a single API call rather than potentially hundreds of API calls that returns the same information lessens the impact on our daily API quota limits. Additionally, the fewer the API calls and iteration required decreases potentials for errors during execution of any automated process to retrieve this data. Additionally, it requires no manual intervention to get this report out on an automated schedule, instead of having to manually download the CSV from the Vault admin console and then creating a properly formatted email with this info. And finally, with the ability to quickly retrieve this information without concern for daily quota limits, we can sync this information with a dashboard application that our admins use for updated status information on all our users, ensuring that holds can be added/removed in a timely fashion if current status information is always readily available in near real-time.
Thank you, I hope this helps.
se...@google.com <se...@google.com> #4
Hello,
Thank you for your answers!
I have filed your feature request internally.
Regards.
al...@sclhealth.org <al...@sclhealth.org> #5
Hello,
This feature would greatly help my organization as well.
Our provisioning system performs a periodic removal/deletion of archived Google accounts, and it needs to be able to determine what users are on legal hold to prevent the loss of the held data.
Iterating through the matters and holds often causes us to hit our limits for the Vault API, so that is not a viable solution.
Thank you,
Alex
This feature would greatly help my organization as well.
Our provisioning system performs a periodic removal/deletion of archived Google accounts, and it needs to be able to determine what users are on legal hold to prevent the loss of the held data.
Iterating through the matters and holds often causes us to hit our limits for the Vault API, so that is not a viable solution.
Thank you,
Alex
je...@uber.com <je...@uber.com> #6
+1 on this feature request
mc...@sc-core.net <mc...@sc-core.net> #7
+1
is...@google.com <is...@google.com>
bl...@google.com <bl...@google.com> #8
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for component 197903.
dk...@broadinstitute.org <dk...@broadinstitute.org> #9
+1
gi...@gmail.com <gi...@gmail.com> #10
+1
mc...@snapchat.com <mc...@snapchat.com> #11
+1
te...@go-4ig.com <te...@go-4ig.com> #12
is this feature added ?
mc...@snapchat.com <mc...@snapchat.com> #13
Bumping this issue as I am running into issues with API quotas when trying pull this data through Vault matters/holds/accounts endpoints. Please provide a better solution for this. The UI export is perfect but we need this is an API endpoint.
Error talking to Google API: <HttpError 429 when requestinghttps://vault.googleapis.com/v1/matters/AAABBBCCCDDD/holds/AAABBBCCCCDDD/accounts?alt=json returned "Quota exceeded for quota metric 'Matter Reads' and limit 'Matter Reads per minute' of service 'vault.googleapis.com ' for consumer 'project_number:AAABBBCCCCDDD'.". Details: "[{'@type': 'type.googleapis.com/google.rpc.ErrorInfo ', 'reason': 'RATE_LIMIT_EXCEEDED', 'domain': 'googleapis.com ', 'metadata': {'quota_limit_value': '120', 'service': 'vault.googleapis.com ', 'quota_limit': 'MatterReadsPerMinutePerProject', 'quota_location': 'global', 'quota_metric': 'vault.googleapis.com/matter_reads ', 'consumer': 'projects/AAABBBCCCCDDD'}}, {'@type': 'type.googleapis.com/google.rpc.Help ', 'links': [{'description': 'Request a higher quota limit.', 'url': 'https://cloud.google.com/docs/quota#requesting_higher_quota'}]} ]">
Error talking to Google API: <HttpError 429 when requesting
a_...@airbnb.com <a_...@airbnb.com> #14
+1
ma...@okta.com <ma...@okta.com> #15
+ 1 I am impacted by this as well at OKTA. It would be great to have this UI functionality which returns a list in 5 seconds, compared to the API queries which take roughly 40 mins.
Description
First, please search through existing issues to ensure that the feature request has not already been reported. You can start the search here:
If the feature has already been requested, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any context of how the feature would benefit you.
Also, please verify that the functionality you are requesting is not already present in the current API and tools.
If your feature has not been requested, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the request:
Need an API method added to the Vault API that lists all users with one or more holds just like in the Vault admin interface (see attached).
What is the purpose of this new feature?
The purpose of this makes it easier to identify which users in our domain or organization have holds placed against them in Google Vault without having to loop through all matters and then subsequently having to iterate through all users in each matter. This avoids potentially having to make an exponentially greater amount of API calls rather than a single call to obtain the same information, reducing impact on daily API request quotas and reducing the amount of increased traffic and load on Google API servers.
What existing APIs would this affect?
This would affect the Vault Reporting API.
What existing data does this use?
This leverages reporting data already available via the Vault/Reports/User Holds in the Vault admin console/UI.
Please provide any additional information below.