Hi @AfvanJaffer you can onboard another GCP organization by obtaining another one-time code from us. Simply open a support case and mention you need another one-time code to link another GCP org to Chronicle.

@Rene_Figueroa 

Hey, thanks for the prompt reply.

here the situation is, we don't want to interrupt transfer of logs from the existing organization.

we want to collect logs from both the organizations simultaneously into the same chronicle instance.

Hi @AfvanJaffer there should be no interruption to the existing connected org. When you get a new one-time code, you will set that connection in the new GCP organization. We have multiple customers who send data from multiple GCP orgs without any interruption. 

Understood!

so I believe we can follow the steps outlined in this documentation on the new organization:

Ingest GCP Logs

Could you please confirm if these are the exact steps we need to follow for the new organization?

@Rene_Figueroa .

A new capability was just released that allows you to now configure this on your own without a one-time code from Google! 
Note, I haven't tested this  yet, but here are the latest released documents: 
https://cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs#enable-direct-ingestion
Based on: https://cloud.google.com/chronicle/docs/release-notes#August_01_2024

@AfvanJaffer please see above.