Nozomi Logs getting ingested even though connection is successful in Nozomi Console

From my experience with similar API connection issues, I recommend checking the Regional Endpoints for your SecOps. You mentioned you’re using https://malachiteingestion-pa.googleapis.com. It’s possible that your SecOps instance is based in a different region. (You can verify this in the URL shown in the GUI.)
For example, if you’re located in London, you should use:
https://europe-west2-malachiteingestion-pa.googleapis.com
You can find the full list here:
https://docs.cloud.google.com/chronicle/docs/reference/ingestion-api#regional_endpoints

Hope this helps!

Hi,
Thank you for the response,

The connection was working with the endpoint “https://malachiteingestion-pa.googleapis.com” but it suddenly stopped for some reason and post that we downloaded the service account auth file from collection agents console and tried adding that in Nozomi. The connection is successful but not logs are being ingested. I am wondering if the SA, from collections agents, doesn’t have enough permissions for these integrations.

Hi ​@Aravind3 

Has the issue been resolved on your end? We are encountering the same problem in our environment. It would be helpful if you could share the steps or approach you followed to resolve it.

If anyone has faced a similar issue, please share your experience or the steps taken to fix it. Your support would be greatly appreciated.

Thanks in advance.