GKE app shows performance issues; logs are in Cloud Logging and metrics are collected via Prometheus sidecar. You need to correlate logs and metrics, send real-time alerts, and minimize cost. What should you do?

The correct approach is to export Prometheus metrics to Cloud Monitoring as external metrics and create log-based metrics from Cloud Logging. Cloud Monitoring is designed for correlating different metric types, including external metrics (from Prometheus) and log-based metrics (from Cloud Logging). This allows for unified dashboards, alerting, and analysis, directly addressing the need for correlation and real-time alerts. This method leverages existing Cloud Monitoring capabilities, minimizing setup and operational cost. Incorrect options: Importing custom metrics into Prometheus from Cloud Logging is inefficient and complex; Prometheus is primarily a time-series database, not a log analysis tool. Exporting to Cloud Bigtable or BigQuery for joins is overly complex and costly for real-time correlation and alerting. These are better suited for large-scale, historical analysis rather than immediate operational insights.