Service Health
Incident affecting Chronicle Security
Delay in normalization for Chronicle customers
Incident began at 2023-05-08 10:17 and ended at 2023-05-08 14:54 (all times are US/Pacific).
Previously affected location(s)
Multi-region: us
Date | Time | Description | |
---|---|---|---|
| 8 May 2023 | 14:54 PDT | The issue with Chronicle has been resolved for all affected users as of Monday, 2023-05-08 14:53 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 8 May 2023 | 12:14 PDT | Summary: Delay in normalization for Chronicle customers Description: Our engineering team is currently working on mitigation of the issue. We will provide an update by Monday, 2023-05-08 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers are unable to see the latest ingested logs on the Chronicle UI. Logs will be visible only after normalization and there is a current delay of approximately 3 hours for normalization. Rules run on normalized events to detect threats and these are also delayed. Customers will not be seeing latest alerts on their page. Workaround: None at this time. |
| 8 May 2023 | 10:45 PDT | Summary: Delay in normalization for Chronicle customers Description: We are experiencing an issue with Chronicle Security beginning at Monday, 2023-05-08 07:30 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2023-05-08 12:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers are unable to see the latest ingested logs on the Chronicle UI. Logs will be visible only after normalization and there is a current delay of approximately 3 hours for normalization. Rules run on normalized events to detect threats and these are also delayed. Customers will not be seeing latest alerts on their page. Workaround: None at this time. |
- All times are US/Pacific