Cloud Transformation

Managed Operations on Google Cloud

Workloads watched, patched, backed up and kept within budget: Google's operations tools with an NGT team and an ITSM process around them.

How NGT runs Google Cloud workloads as a managed service. Cloud Monitoring, Cloud Logging, Cloud Trace and Managed Service for Prometheus feed dashboards and alerts; VM Manager patches servers; Backup and DR and cross-region replicas keep a recovery region ready; budgets, Active Assist and committed use discounts keep cost in line. Alerts become tickets in the customer's ITSM process.

telemetrysnapshotsrestorereplicametricsalertsticketsGoogle CloudRegion · primaryRegion · recoveryObserve, patch and optimiseNGT operationsCompute EngineGKECloud SQLBackup and DRbackup vaultCompute Enginerestored from snapshotsCloud SQLcross-region replicaCloud MonitoringCloud LoggingCloud TraceManaged Service forPrometheusVM ManagerActive AssistrightsizingCloud BillingbudgetsCommitted usediscountsCloud BillingDashboardsGrafana or Cloud MonitoringNGT operations teammonitoring and incidentsITSMincident, problem, change

Point at a component to light its links; select it for what it does here and the practice that makes it right on Google Cloud. A Google Cloud product without an icon of its own shows its category's icon, as Google's icon set does.

When to use it

  • Workloads on Google Cloud that need a team to run them after go-live
  • A disaster-recovery requirement with a second region
  • Cloud spend growing faster than usage

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation