Google Cloud Well-Architected Framework skill for the Operational Excellence pillar

Overview

Core principles

• Ensure operational readiness: Define and measure criteria for a workload to be considered ready for production, including staffing, processes, and governance. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/operational-readiness-and-performance-using-cloudops
• Manage incidents and problems: Establish structured processes for incident response, communication, and root cause analysis to minimize impact and prevent recurrence. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-incidents-and-problems
• Manage and optimize cloud resources: Monitor resource utilization and right-size environments to maintain performance while ensuring operational efficiency. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-and-optimize-cloud-resources
• Automate and manage change: Use Infrastructure as Code (IaC) and CI/CD pipelines to ensure consistent, repeatable, and low-risk deployments and configuration changes. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/automate-and-manage-change
• Continuously improve and innovate: Regularly review architectures, monitor industry trends, and adapt operations to meet evolving business needs. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/continuously-improve-and-innovate

Relevant Google Cloud products

• Observability and monitoring
  • Cloud Monitoring: Full-stack observability for Google Cloud and hybrid environments.
  • Cloud Logging: Real-time log management and analysis at scale.
  • Error Reporting: Aggregates and displays errors for running cloud services.
  • Service Monitoring: Tools for defining and tracking Service Level Objectives (SLOs).
• Automation and CI/CD
  • Cloud Build: Serverless platform for building, testing, and deploying software.
  • Cloud Deploy: Managed continuous delivery service for GKE, Cloud Run, and GCE.
  • Terraform / Infrastructure Manager: Managed service for Infrastructure as Code (IaC) automation.
  • Artifact Registry: Central repository for managing build artifacts and container images.
• Resource management and optimization
  • Recommender (Active Assist): Automatically identifies idle resources and right-sizing opportunities.
  • Resource Manager: Hierarchical management of resources across organizations, folders, and projects.
• Incident response
  • Incident response & management (IRM): Structured tools and processes for managing operational disruptions.

Workload assessment questions

• Operational readiness and performance
  • How do you define and measure operational readiness for your cloud workloads and what specific criteria or metrics do you use?
  • Describe your process for defining, tracking, and achieving SLOs for your critical workloads.
• Incident and problem management
  • Describe your incident management process, including roles, responsibilities, and communication channels.
  • How do you conduct post-incident reviews (PIRs) to identify root causes and implement preventive measures?
• Resource management and optimization
  • How do you ensure that your cloud resources are right-sized for your workloads, and what tools or techniques do you use?
• Change automation
  • Describe your change management process, including approval workflows, testing procedures, and deployment strategies.
  • How do you automate deployments, ensure their consistency and manage configuration?
• Continuous improvement
  • How do you ensure that your cloud operations are continuously adapting to meet evolving business needs and technological advancements?

Validation checklist

• Operational readiness
  • A formal framework or set of criteria exists to assess operational readiness before production deployment.
  • Service Level Objectives (SLOs) are explicitly defined and monitored using automated tools.
• Incident management
  • Incident response roles and communication channels are clearly defined and documented.
  • A structured, blameless post-mortem process is followed for all major incidents.
• Change automation
  • All infrastructure changes are performed using Infrastructure as Code (IaC) to ensure consistency.
  • CI/CD pipelines are integrated with automated testing for all deployment changes.
• Resource optimization
  • Resource utilization is regularly reviewed using recommendations from Active Assist or performance data.
• Culture of improvement
  • A documented strategy is in place for regularly reviewing and adapting cloud operations to industry advancements.