Sign in to confirm you’re not a bot
This helps protect our community. Learn more

Azure Incident Retrospective: MySQL/MariaDB in West US, Databricks, Apr 2024 (Tracking ID: QS3K-BPZ)

Microsoft Reactor
125K subscribers
271 views 1 year ago
On 19 April 2024, an Azure MySQL incident (Tracking ID: QS3K-BPZ) impacted MySQL and MariaDB resources in the West US region - and impacted Azure Databricks resources in the West US, West US 2, and South Central US regions. After publishing the Post Incident Review (PIR) we invited impacted customers and partners to join this Teams Live Event to be part of a discussion with our engineering leaders and experts – to learn more about the incident, how we responded, and what we learned. Customers who participated in the live event also had an opportunity to get any questions about the incident answered, through a Live Q&A moderated by our engineering subject matter experts. Stay informed during issues – configure Service Health alerts for notifications and invites: https://www.aka.ms/ASH-docs Learn from previous events – Health history in Azure Service Health shows impact to your services: https://www.aka.ms/ASH-portal Prepare for the unexpected – learn more about steps you can take to prepare for cloud incidents: https://www.aka.ms/IncidentReadiness [eventID:22706] ...more
...more
Azure Incident Retrospective: MySQL/MariaDB in West US, Databricks, Apr 2024 (Tracking ID: QS3K-BPZ)
4Likes
271Views
2024May 29
On 19 April 2024, an Azure MySQL incident (Tracking ID: QS3K-BPZ) impacted MySQL and MariaDB resources in the West US region - and impacted Azure Databricks resources in the West US, West US 2, and South Central US regions. After publishing the Post Incident Review (PIR) we invited impacted customers and partners to join this Teams Live Event to be part of a discussion with our engineering leaders and experts – to learn more about the incident, how we responded, and what we learned. Customers who participated in the live event also had an opportunity to get any questions about the incident answered, through a Live Q&A moderated by our engineering subject matter experts. Stay informed during issues – configure Service Health alerts for notifications and invites: https://www.aka.ms/ASH-docs Learn from previous events – Health history in Azure Service Health shows impact to your services: https://www.aka.ms/ASH-portal Prepare for the unexpected – learn more about steps you can take to prepare for cloud incidents: https://www.aka.ms/IncidentReadiness [eventID:22706]
How this content was made
Auto-dubbed
Audio tracks for some languages were automatically generated. Learn more

Follow along using the transcript.

Microsoft Reactor

125K subscribers