Reliability
Checking connection limits before an application launch
Calculate database connections across app instances and test pool waits, errors and query latency before launch.
Section
Reliability
Reliability
Choosing alerts that require a clear operator action
Decide which cloud signals deserve an alert by defining impact, owner, urgency and the operator's next step.
Reliability
Choosing cloud requirements from reliability and data needs
Define checkable cloud requirements from business availability, recovery targets, data sensitivity and handling needs.
Reliability
Cloud monitoring with golden signals, SLOs and alerts
Build cloud monitoring around user outcomes, diagnostic signals and alerts that lead to a clear response.
Reliability
Cloud reliability
Define cloud reliability for business workloads, choose controls for likely failures, and check whether recovery meets agreed targets.
Reliability
Comparing redundancy with recoverability
Compare what redundancy and recovery each protect, where their limits differ, and how to combine them against business targets.
Reliability
Defining availability requirements for a business workload
Define availability around a business journey, choose a useful measure, and record recovery targets alongside the objective.
Reliability
Managing operating system updates for cloud servers: 4 steps
Plan cloud server patch priorities and deployment waves, then verify application health and track skipped or failed machines.
Reliability
Monitoring application latency alongside server resources
Read request latency with traffic, errors, dependencies and server resources to investigate slow application actions.
Reliability
Planning database backup and restore tests
Set a database restore test pass condition, isolate the restored copy and measure data and application recovery.
Reliability
Planning for a regional service disruption
Prepare a regional disruption plan with clear failover criteria, independent dependencies, data decisions and a tested return path.
Reliability
Recording logs useful for incident investigation
Choose application log events, fields, identifiers and safeguards that help operators reconstruct an incident.
Reliability
Reviewing alert noise after an incident
Use an incident timeline to find duplicate, mistimed and unactionable alerts while preserving useful detection.
Reliability
Reviewing backup and recovery evidence regularly
Review backup coverage, job history and restore exercises against each workload's recovery requirements, then assign gaps.
Reliability
Reviewing configuration changes that expose services
Trace a cloud access change to its affected service, assess reachability and record the correction and checks.
Reliability
Rolling back an application release safely
Decide how to respond to a faulty application release by checking version, traffic and data compatibility before verifying live service.
Reliability
Separating development, test and production environments
Set boundaries for cloud development, test and production while keeping test results relevant to a live release.
Reliability
Testing a deployment before changing live services
Choose release checks around changed components, important user actions and explicit pass conditions before changing live services.
Reliability
Testing a recovery procedure rather than assuming it works
Test the full recovery path, measure actual RTO and RPO, inspect recovered data, and record the limits of each exercise.
Reliability
Testing cloud backups against recovery requirements
Plan an isolated cloud-backup restore, measure usable recovery against RTO and RPO, and record what the test actually proves.
Reliability
Troubleshooting connectivity between cloud services
When one cloud service cannot reach another, locate the failing layer before changing rules.