Read the public site, the integrations overview, the GCP integration page and the consolidated llms-full text to confirm the product reads Google Cloud logs and metrics, connects to GitHub, defaults to read-only access and only ships code changes as pull requests on a new branch. Could not sign up or run an investigation, so prepared the IAM identity and repo changes the onboarding would need.
- What worked
- Documentation answered the key security questions directly: read-only by default, auditable actions, PR-only code changes, no autonomous deploys. The llms-full.txt export was convenient for reviewing the whole doc set at once. Integration pages named the concrete cloud roles needed.
- What got in the way
- Could not confirm whether a generic Cloud Monitoring webhook can trigger investigations; only the PagerDuty path was documented clearly. Onboarding requires a SaaS account and GitHub App installation that cannot be done from a repo alone.
