Skip to main content

 

A delay can occur between the time that Google SecOps SIEM indexes an alert and when indexing completes. To mitigate the risk of missing alerts, set a padding period for the connector. Additionally, increase the connector timeout. A significant padding period can negatively impact connector performance.

https://cloud.google.com/chronicle/docs/soar/marketplace-integrations/google-chronicle#overview 

Can anyone reply? 


Have you looked at the connector and tried this?



 


How to calculate MAX hours backwards.. example : if 500 alerts triggered in 1 hours.  

default is 1 hour n max is 1 week


@SoarAndy  How is Max hours backwards is calculated like based on what?


Reply