Having issue with Lab Analyze Findings with Security Command Center

Screenshot 2025-01-30 at 9.17.32 PM.pngHas anyone else experienced the same issue? How did you resolve it? I’ve also reached out to support, and they’re testing it, but I haven’t received any updates on a fix yet. I guess that's the only way to resolve it for now, or should I try fixing it in findings.jsonl?

Solved Solved
1 4 251
3 ACCEPTED SOLUTIONS

No problem with this lab. Please follow steps as per Lab. wait for below output (as per below image) before exporting to cloud storage. and when exporting to BigQuery always select format as "JSONL".

repeat below command till you get o/p. it takes 10 to 15 mins. to display. This is very important step in this lab. I hope this information will help you to solve problem. All the best.

--------------------------------------------------------------------------------------------------------------------------

bq query --apilog=/dev/null --use_legacy_sql=false \
"SELECT finding_id,event_time,finding.category FROM continuous_export_dataset.findings"

-------------------------------------------------------------------------------------------------------------------------

 

RAOKS_0-1738386130128.png

 

View solution in original post

Hi, @aiblair20.

I didn’t encounter any issues when I tried this. Let’s go through the steps carefully again. If you still get the error, please use the 'Chat Support' option in the top-right corner. They should be able to help identify the issue if it persists.
mokit_0-1736861672449.png


Regards,
Mokit

View solution in original post

Thanks, everyone. The issue has been resolved. I mistakenly chose the JSON instead of the JSONL.

View solution in original post

4 REPLIES 4

Answer pls what they finally said

For me they always have only answer "Everything is working"

Its a hi-tech google method to earn money. Did they return you credits for broken lab?

No problem with this lab. Please follow steps as per Lab. wait for below output (as per below image) before exporting to cloud storage. and when exporting to BigQuery always select format as "JSONL".

repeat below command till you get o/p. it takes 10 to 15 mins. to display. This is very important step in this lab. I hope this information will help you to solve problem. All the best.

--------------------------------------------------------------------------------------------------------------------------

bq query --apilog=/dev/null --use_legacy_sql=false \
"SELECT finding_id,event_time,finding.category FROM continuous_export_dataset.findings"

-------------------------------------------------------------------------------------------------------------------------

 

RAOKS_0-1738386130128.png

 

Hi, @aiblair20.

I didn’t encounter any issues when I tried this. Let’s go through the steps carefully again. If you still get the error, please use the 'Chat Support' option in the top-right corner. They should be able to help identify the issue if it persists.
mokit_0-1736861672449.png


Regards,
Mokit

Thanks, everyone. The issue has been resolved. I mistakenly chose the JSON instead of the JSONL.

Top Labels in this Space