Service Health
Incident affecting Operations
We are investigating an issue with a delay in Google Stackdriver Logging ingestion.
Incident began at 2019-04-19 09:27 and ended at 2019-04-19 13:11 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 19 Apr 2019 | 13:11 PDT | The issue with Google Stackdriver Logging ingestion has been resolved for all affected projects as of Friday, 2019-04-19 12:30 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
| 19 Apr 2019 | 11:55 PDT | The issue with delays in Google Stackdriver Logging ingestion should be resolved for some projects and we expect a full resolution in the near future. We will provide another status update by Friday, 2019-04-19 14:00 US/Pacific with current details. |
| 19 Apr 2019 | 11:17 PDT | We are investigating an issue with a delay in Google Stackdriver Logging ingestion. Logs ingested after Friday, 2019-04-19 09:27 US/Pacific may be not show up in queries to the Stackdriver logging service. The service is currently processing the backlog of messages, logs ingested since 09:27 US/Pacific will begin to appear in results. We will provide more information by Friday, 2019-04-19 12:00 US/Pacific. |
| 19 Apr 2019 | 10:23 PDT | We are investigating an issue with a delay in Google Stackdriver Logging ingestion. Logs ingested after Friday, 2019-04-19 09:27 US/Pacific are unable to be queried from the Stackdriver logging service. We currently working on a mitigation. We will provide more information by Friday, 2019-04-19 11:15 US/Pacific. A workaround to access more recent logs would be to leverage log exports. Log exports are not currently experiencing the same delay as the query service. |
| 19 Apr 2019 | 10:23 PDT | We are investigating an issue with a delay in Google Stackdriver Logging ingestion. |
- All times are US/Pacific