Configuring and Viewing Cloud Audit Logs recensioni

15250 recensioni

Justince Y. · Recensione inserita circa 5 anni fa

Justince Y. · Recensione inserita circa 5 anni fa

Thomas M. · Recensione inserita circa 5 anni fa

Srinevasa N. · Recensione inserita circa 5 anni fa

Kamalika S. · Recensione inserita circa 5 anni fa

Kevin A. · Recensione inserita circa 5 anni fa

Latha R. · Recensione inserita circa 5 anni fa

Timo-Sven J. · Recensione inserita circa 5 anni fa

Derrick C. · Recensione inserita circa 5 anni fa

good

Vijay K. · Recensione inserita circa 5 anni fa

Charles M. · Recensione inserita circa 5 anni fa

Chong L. · Recensione inserita circa 5 anni fa

Lee W. · Recensione inserita circa 5 anni fa

Royston K. · Recensione inserita circa 5 anni fa

Adrian Y. · Recensione inserita circa 5 anni fa

Tan K. · Recensione inserita circa 5 anni fa

teeranai w. · Recensione inserita circa 5 anni fa

I'm updating my previous rating for this lab because I was finally able to complete it, after realizing there's a subtle typo in the instructions. In the Logs Explorer query, the lab indicates we should replace "PROJECT_ID" with the generated Quiklabs project ID. I did this, and it didn't work at all. It was only after coming back to this lab the next day that I realized it should read "[PROJECT_ID]" (with the brackets). It's a subtle difference, but makes the difference between passing & failing the lab, and it's an easy mistake to make late at night after the kids are in bed.

Jarod K. · Recensione inserita circa 5 anni fa

Yap T. · Recensione inserita circa 5 anni fa

I attempted five times to do this lab. I let it go for about a month . I could not figure it out. Finally, today on my sixth try, i decided to search online and found some ones tutorial explain this. For people who like know nothing of this things, it should be spelled out a bit. Few things : 1- On task one the " Policy Json" explanation does not say to hit "enter" to add "2". I was pasting right after the "{" 2- Task three for number #2 for pasting "logName " in query builder and replace project ID with our project ID. It does not show us that we do not have to keep the brackets. That it should look logName ("projects/myidhere/logs/cloudaudit.googleapis.com%2Factivity (this should be specified, all my lab attempts where with the brackets in it) there was no way i would have found this out on my own. 3- on Task 5 , when clicking on dataset name and expanding it , my lab did not show "cloudaudit_googleapis.com_a" under my data set, the only thing shown was a small, barely visible dash. It took it me a while to click on it cause i had no idea, thank Christ I did. 4- It would also be nice when it says to "delete query_editor" to let us know we can use "Compose NewQuery". I am sorry but some things were not explained to the full on this lab. I attempted five times to do this lab. I let it go for about a month . I could not figure it out. Finally, today on my sixth try, i decided to search online and found some ones tutorial explain this. For people who like know nothing of this things, it should be spelled out a bit. Few things : 1- On task one the " Policy Json" explanation does not say to hit "enter" to add "2". I was pasting right after the "{" 2- Task three for number #2 for pasting "logName " in query builder and replace project ID with our project ID. It does not show us that we do not have to keep the brackets. That it should look logName ("projects/myidhere/logs/cloudaudit.googleapis.com%2Factivity (this should be specified, all my lab attempts where with the brackets in it) there was no way i would have found this out on my own. 3- on Task 5 , when clicking on dataset name and expanding it , my lab did not show "cloudaudit_googleapis.com_a" under my data set, the only thing shown was a small, barely visible dash. It took it me a while to click on it cause i had no idea, thank Christ I did. 4- It would also be nice when it says to "delete query_editor" to let us know we can use "Compose NewQuery". I am sorry but some things were not explained to the full on this lab. This the longest time i have been stuck on a lab since i started doing this back in Dec, 2020. Had I not seen this good human tutorial none of your explanations when i emailed would have worked but none of them did. Thank You

Marilyn M. · Recensione inserita circa 5 anni fa

can not do this

Marilyn M. · Recensione inserita circa 5 anni fa

sneha M. · Recensione inserita circa 5 anni fa

I had to end the lab without completing it because I was unable to enable access to audit logs. No data is being generated, and attempting to re-run the steps in Task 1 generates an error. I'm going to attempt to restart the lab in case this is something related to this specific project ID.

Jarod K. · Recensione inserita circa 5 anni fa

esther G. · Recensione inserita circa 5 anni fa

Ken M. · Recensione inserita circa 5 anni fa

Non garantiamo che le recensioni pubblicate provengano da consumatori che hanno acquistato o utilizzato i prodotti. Le recensioni non sono verificate da Google.