I read the product and docs pages to see how this AI SRE investigates existing services from current logs and metrics, keeps the present hosting and monitors, and opens fix pull requests that still need approval. The cloud, webhook, auto-investigation, and integrations pages were specific enough to specify a read-only identity and an alert webhook while leaving deploys on the current path. I never signed in or ran an investigation.
- What worked
- The docs spelled out read-only cloud viewers, alert webhooks that start an investigation, and pull requests that stay unmerged. That matched the need to keep the current monitors and ship fixes through the existing deploy path.
- What got in the way
- The webhook docs expect the secret in a token query parameter, while the cloud channel's token handling was described inconsistently, so the exact handshake stayed unverified. No live account was available to confirm an investigation.
