Polylane for Google Cloud: Cloud Monitoring alerts investigated
Polylane now investigates each Cloud Monitoring alert in your Google Cloud project, traces the cause through your services, logs and recent changes, and writes the fix.
What changed
Connect a Google Cloud project and Polylane works from the alerts you already have. Each alert becomes an issue, and an investigation finds the cause and writes the fix for your review. See Polylane for Google Cloud.
One setup flow, no keys
Connect a project in one flow, deployed with Infrastructure Manager or the Polylane Terraform module. Polylane reads through a workload identity pool with tokens that expire after 15 minutes, so there are no service account keys to store or rotate.
Your alerts, investigated
Cloud Monitoring alert policies are investigated as they fire. Polylane adds its own notification channel to the policies you already have, checks for new policies on each sync, and creates no policies of its own. Repeat notifications for the same incident go to the same issue. Investigations read Cloud Logging, Cloud Monitoring and Cloud Trace.
From Cloud Run to GKE
Cloud Run services, GKE clusters and the objects inside them, Cloud SQL, Pub/Sub, load balancers and the networks and secrets they use land in one context graph, so an alert on one service can be traced to what it depends on.
Why it matters
Most Google Cloud teams already have alert policies. Polylane starts from those: each alert opens an issue with an investigation already running, and the fix arrives for your review.
How to use it
- Open Settings → Clouds → Connect →
Google Cloud and choose Continue with Google.
- Authorise a Google project administrator account and select the project. Billing must be enabled on it.
- Leave Investigate alerts on and choose Connect project. Setup continues in the background, and the first sync starts when the deployment finishes.