You migrated some of your applications to Google Cloud. You are using a legacy monitoring platform deployed on-premises for both on-premises and cloud- deployed applications. You discover that your no

Question

Options

• AReplace your monitoring platform with Cloud Monitoring.
• BInstall the Cloud Monitoring agent on your Compute Engine instances.
• CMigrate some traffic back to your old platform. Perform A/B testing on the two platforms
• DUse Cloud Logging and Cloud Monitoring to capture logs, monitor, and send alerts. Send them to

• A
  5% (1)
• B
  9% (2)
• C
  5% (1)
• D
  82% (18)

Explanation

The root cause is that a legacy on-premises monitoring system must route network traffic across the internet to observe cloud-hosted applications, introducing latency before alerts are triggered. The correct fix is to use cloud-native observability tools - Cloud Logging and Cloud Monitoring - to detect and alert on issues where the resources actually live, then push those alerts to the on-premises platform. This hybrid approach keeps critical alerting logic co-located with the cloud workloads for near-instant detection. Option A (replace entirely) is too disruptive and ignores on-premises apps. Option B (install the agent) only improves metric collection, not the alerting latency. Option C (A/B testing traffic migration) does not address the monitoring architecture at all.

No community discussion yet for this question.